GSA Per Diem
PYPI · GSA-PERDIEM-MCP · SCANNED SEP 20
GSA Per Diem access readiness, lodging, and meals and incidental expense rates. 7 tools.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 34 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 986 tokens (~140/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the GSA Per Diem MCP server?
GSA Per Diem runs locally as a PyPI package, launched with uvx gsa-perdiem-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · gsa-perdiem-mcp
claude mcp add com-1102tools-gsa-perdiem-mcp -- uvx gsa-perdiem-mcp
{
"mcpServers": {
"com-1102tools-gsa-perdiem-mcp": {
"command": "uvx",
"args": [
"gsa-perdiem-mcp"
]
}
}
} {
"servers": {
"com-1102tools-gsa-perdiem-mcp": {
"command": "uvx",
"args": [
"gsa-perdiem-mcp"
]
}
}
} codex mcp add com-1102tools-gsa-perdiem-mcp -- uvx gsa-perdiem-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-1102tools-gsa-perdiem-mcp": {
"type": "local",
"command": [
"uvx",
"gsa-perdiem-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-1102tools-gsa-perdiem-mcp --command uvx --arg gsa-perdiem-mcp
mcp_servers:
com-1102tools-gsa-perdiem-mcp:
command: "uvx"
args: ["gsa-perdiem-mcp"] {
"McpServers": {
"com-1102tools-gsa-perdiem-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"gsa-perdiem-mcp"
]
}
}
} assistant mcp add com-1102tools-gsa-perdiem-mcp -t stdio -c uvx -a gsa-perdiem-mcp
{
"mcpServers": {
"com-1102tools-gsa-perdiem-mcp": {
"command": "uvx",
"args": [
"gsa-perdiem-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 1.0.9 → 1.0.10 functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/gsa-perdiem-mcp@1.0.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 34 packages
| Packages resolved | 34 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_locations ~90
Compare per diem rates across multiple locations. locations: list of {"city": "...", "state": "XX"} dicts, max 25 entries (DEMO_KEY limits you to ~10 req/hr so this is generous). Returns rates sorted by max daily total (highest first). Useful for travel IGCE development when comparing destination costs.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year | – | – | – |
| locations | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
estimate_travel_cost ~211
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.101. travel_month: 3-letter abbreviation (Jan, Feb, ..., Dec). If omitted, uses the max monthly lodging rate (conservative estimate for IGCE). Does NOT include airfare or ground transportation. Add those separately. 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. A single trip longer than a year is unlikely to be covered by per diem.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| fiscal_year | – | – | – |
| num_nights | integer | yes | – |
| state | string | yes | – |
| travel_month | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_access_status ~22
Check Per Diem credential presence without returning or validating its value.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_mie_breakdown ~100
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. Use this to show the meal component breakdown when presenting per diem estimates. M&IE does NOT vary seasonally (unlike lodging). The tier is set per location and applies year-round.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_city_perdiem ~313
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. The city endpoint resolves cities to their county's rate area server-side, so the matched NSA name can legitimately differ from the query (Washington -> 'District of Columbia', Penasco -> 'Taos'). Selection order: 1. Exact city name match 2. Composite NSA name containing the city (e.g., 'Boston' matches 'Boston / Cambridge') 3. API-resolved rate area (no Standard Rate row in the response) 4. Standard Rate fallback (query fell through to the state default) Apostrophes, hyphens, and slashes in city names are auto-replaced with spaces (GSA API quirk). Keep periods for 'St.' prefix cities (St. Louis). For DC: query city='Washington', state='DC'. CONUS only: AK, HI, and territories return a pointer to DoD/State rates.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| fiscal_year | – | – | – |
| state | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_state_rates ~113
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. Useful for comparing rates across cities within a state or for building a travel IGCE with multiple destinations. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year | – | – | – |
| state | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_zip_perdiem ~101
Look up federal per diem rates by ZIP code. May return multiple entries (NSA + standard rate). This tool auto-selects the NSA rate over the standard rate. Useful when the exact city name is uncertain but the ZIP is known. Accepts 5-digit ZIPs or ZIP+4 (e.g., '02101' or '02101-1234').
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year | – | – | – |
| zip_code | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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 PyPI package (gsa-perdiem-mcp).
Is the GSA Per Diem MCP server safe to use?
GSA Per Diem scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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_access_status, lookup_city_perdiem, lookup_zip_perdiem, lookup_state_rates, get_mie_breakdown, and 2 more. Their descriptions and schemas cost roughly 950 tokens of context every time the server is loaded.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the GSA Per Diem MCP server under?
GSA Per Diem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.