# GSA Per Diem (remote · gsa-perdiem.1102tools.com)

GSA Per Diem access readiness, lodging, and meals and incidental expense rates. 7 tools.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gsa-perdiem.1102tools.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem.md), [page](https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem)
- pypi · `gsa-perdiem-mcp`: 76/100, [markdown](https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem-mcp.md), [page](https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem-mcp)

## Channel facts

- Endpoint: `https://gsa-perdiem.1102tools.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.8`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1413 tokens (~201/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the GSA Per Diem MCP server?

GSA Per Diem is a hosted endpoint at https://gsa-perdiem.1102tools.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-1102tools-gsa-perdiem-mcp 'https://gsa-perdiem.1102tools.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-1102tools-gsa-perdiem-mcp": {
      "url": "https://gsa-perdiem.1102tools.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-1102tools-gsa-perdiem-mcp": {
      "type": "http",
      "url": "https://gsa-perdiem.1102tools.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-1102tools-gsa-perdiem-mcp]
url = "https://gsa-perdiem.1102tools.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-1102tools-gsa-perdiem-mcp": {
      "type": "remote",
      "url": "https://gsa-perdiem.1102tools.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-1102tools-gsa-perdiem-mcp --url 'https://gsa-perdiem.1102tools.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-1102tools-gsa-perdiem-mcp:
    url: "https://gsa-perdiem.1102tools.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-1102tools-gsa-perdiem-mcp": {
      "Transport": "http",
      "Url": "https://gsa-perdiem.1102tools.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-1102tools-gsa-perdiem-mcp -t streamable-http -u 'https://gsa-perdiem.1102tools.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-1102tools-gsa-perdiem-mcp": {
      "type": "http",
      "url": "https://gsa-perdiem.1102tools.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 64, 0)

- [functional] Server version: 1.2.7 → 1.2.8

### 2026-10-25 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `get_data_status` (~121 tokens)

Report which fiscal years are bundled, their GSA source files, and which tools call the GSA API.

    ZIP, state, and M&IE lookups for bundled fiscal years are answered
    from GSA's published files with no network call. City requests with a
    supplied county for a bundled year also need no key or network call.
    City-name requests without a county, and unbundled years, use the live
    GSA Per Diem API. Credential
    presence is reported without revealing or validating any value.

### `lookup_city_perdiem` (~333 tokens)

Look up federal per diem rates for a city and state.

    Returns lodging rates (monthly breakdown for seasonal locations) and
    M&IE (meals and incidental expenses) for the specified fiscal year.

    state: 2-letter USPS code (e.g., 'DC', 'VA', 'MD', 'CA').
    fiscal_year: defaults to current FY. FY runs Oct 1 - Sep 30, so
    FY2026 = 2025-10-01 through 2026-09-30.
    county: optional county or independent city (e.g., 'Fairfax',
    'Hampden', 'Richmond city'). When given for a bundled fiscal year the
    rate is determined from GSA's county definitions without an API call.

    Without county, the GSA Per Diem API resolves the city name to rate
    areas. The result's status is:
    - resolved: one rate applies (exact name, composite name such as
      'Boston / Cambridge', GSA's own city-to-county resolution, or a
      Census county tie-break among GSA's candidates)
    - ambiguous: GSA lists several rate areas for the city; candidates are
      returned and no single rate is chosen
    - unresolved: GSA did not recognize the city; no rate is asserted

    CONUS only: AK, HI, and territories return a pointer to DoD/State rates.

Input parameters:

- `city` (string, required)
- `county`
- `fiscal_year`
- `state` (string, required)

### `lookup_zip_perdiem` (~180 tokens)

Look up federal per diem rates by ZIP code.

    Accepts 5-digit ZIPs or ZIP+4 (e.g., '02101' or '02101-1234').
    Bundled fiscal years are answered from GSA's published ZIP file with
    no API call; other years use the GSA Per Diem API.

    GSA sets rates by county or locality, and about 1,800 ZIPs span more
    than one rate area. The result's status is 'resolved' when every rate
    area GSA lists for the ZIP has the same rate, otherwise 'ambiguous'
    with all candidates and no single rate chosen. county (optional)
    selects the candidate for that county.

Input parameters:

- `county`
- `fiscal_year`
- `zip_code` (string, required)

### `lookup_state_rates` (~164 tokens)

Get all Non-Standard Area (NSA) per diem rates for a state.

    Returns every city/county with rates above the standard rate in that
    state, plus the state's standard rate. Seasonal areas include their
    lodging rate for each month (lodging_by_month). Useful for comparing rates
    across cities within a state or for building a travel IGCE with
    multiple destinations. Bundled fiscal years are answered from GSA's
    published files with no API call.

    CONUS only: AK, HI, and territories return a pointer to DoD/State rates
    instead of an empty list that would falsely imply the standard CONUS
    rate applies there.

Input parameters:

- `fiscal_year`
- `state` (string, required)

### `get_mie_breakdown` (~123 tokens)

Get the M&IE (meals and incidental expenses) tier breakdown table.

    Returns all M&IE tiers with breakfast, lunch, dinner, incidental, and
    first/last day (75%) amounts, for showing the meal component of a
    per diem estimate. Bundled fiscal years come from GSA's published
    M&IE breakdown with no API call.

    M&IE does NOT vary seasonally (unlike lodging). The tier is set per
    location and applies year-round.

Input parameters:

- `fiscal_year`

### `estimate_travel_cost` (~384 tokens)

Estimate total per diem cost for a trip.

    Calculates lodging + M&IE for the specified number of nights.
    First and last travel days use 75% M&IE per 41 CFR 301-11.20.

    travel_month: 3-letter abbreviation (Jan, Feb, ..., Dec). Every night is
    priced at that month's rate; for a trip that crosses into another month
    or fiscal year, add only each month's lodging_total at the applicable
    fiscal year rate. Calculate M&IE once across the actual trip days,
    using 75% only on the actual departure and return days. Do not add
    separate monthly mie_total or grand_total values: each estimate
    assumes a new trip.
    If omitted, uses the max monthly lodging rate (conservative estimate
    for IGCE).
    fiscal_year: if omitted, the FY of the next occurrence of travel_month
    (or the current FY when no month is given). Pass it for a trip that
    already happened.
    county: optional; selects the rate area when the city spans more than
    one (see lookup_city_perdiem).

    No estimate is produced when the city is ambiguous or unresolved; the
    candidate rate areas are returned instead.

    Does NOT include airfare or ground transportation.

    Formula:
    - Lodging = nightly_rate * num_nights
    - M&IE = full_day_rate * (travel_days - 2) + first/last_day_rate * 2
    - Travel days = num_nights + 1

    num_nights bounded 1-365.

Input parameters:

- `city` (string, required)
- `county`
- `fiscal_year`
- `num_nights` (integer, required)
- `state` (string, required)
- `travel_month`

### `compare_locations` (~108 tokens)

Compare per diem rates across multiple locations.

    locations: list of {"city": "...", "state": "XX"} dicts (optionally
    with "county"), max 25 entries. Returns rates sorted by max daily
    total (highest first). Ambiguous or unresolved cities are listed with
    their status and candidate rate areas instead of a rate.

    Useful for travel IGCE development when comparing destination costs.

Input parameters:

- `fiscal_year`
- `locations` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 67
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 66
- 2026-10-29: 65
- 2026-10-28: 65
- 2026-10-27: 64
- 2026-10-26: 64
- 2026-10-25: 64
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62

## Common questions

### What is the GSA Per Diem MCP server?

GSA Per Diem is an MCP server listed in the public MCP registry as com.1102tools/gsa-perdiem-mcp. GSA Per Diem access readiness, lodging, and meals and incidental expense rates. 7 tools. This page covers its hosted endpoint (https://gsa-perdiem.1102tools.com/mcp).

### Is the GSA Per Diem MCP server safe to use?

GSA Per Diem scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the GSA Per Diem MCP server expose?

GSA Per Diem exposes 7 tools: get_data_status, lookup_city_perdiem, lookup_zip_perdiem, lookup_state_rates, get_mie_breakdown, and 2 more. Their descriptions and schemas cost roughly 1,413 tokens of context every time the server is loaded.

### Does the GSA Per Diem MCP server require authentication?

No. We connected to GSA Per Diem without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GSA Per Diem MCP server still maintained?

GSA Per Diem is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://gsa-perdiem.1102tools.com/mcp
- Repository: https://github.com/1102tools-dev/federal-contracting-mcps
- Website: https://1102tools.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem.json
- HTML version of this page: https://verifymcp.io/servers/com-1102tools-gsa-perdiem-mcp/gsa-perdiem