USASpending.gov
PYPI · USASPENDING-GOV-MCP · SCANNED SEP 20
USASpending.gov awards, subawards, recipients, agencies, and federal accounts. 55 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 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 6850 tokens (~124/item across 55 items; 55 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 55 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 55 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 USASpending.gov MCP server?
USASpending.gov runs locally as a PyPI package, launched with uvx usaspending-gov-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 · usaspending-gov-mcp
claude mcp add com-1102tools-usaspending-gov-mcp -- uvx usaspending-gov-mcp
{
"mcpServers": {
"com-1102tools-usaspending-gov-mcp": {
"command": "uvx",
"args": [
"usaspending-gov-mcp"
]
}
}
} {
"servers": {
"com-1102tools-usaspending-gov-mcp": {
"command": "uvx",
"args": [
"usaspending-gov-mcp"
]
}
}
} codex mcp add com-1102tools-usaspending-gov-mcp -- uvx usaspending-gov-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-1102tools-usaspending-gov-mcp": {
"type": "local",
"command": [
"uvx",
"usaspending-gov-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-1102tools-usaspending-gov-mcp --command uvx --arg usaspending-gov-mcp
mcp_servers:
com-1102tools-usaspending-gov-mcp:
command: "uvx"
args: ["usaspending-gov-mcp"] {
"McpServers": {
"com-1102tools-usaspending-gov-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"usaspending-gov-mcp"
]
}
}
} assistant mcp add com-1102tools-usaspending-gov-mcp -t stdio -c uvx -a usaspending-gov-mcp
{
"mcpServers": {
"com-1102tools-usaspending-gov-mcp": {
"command": "uvx",
"args": [
"usaspending-gov-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.
- 18 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
- Package version: 1.0.5 → 1.0.9 functional
- Package version: 1.0.5 → 1.0.8 functional
- Package version: 1.0.5 → 1.0.7 functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +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.
- 6 Sept 26 +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.
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/usaspending-gov-mcp@1.0.9
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 →
spending_by_category ~290
Aggregate spending by a dimension (top vendors, top agencies, top NAICS, etc.). The 'category' parameter controls the grouping dimension. Common uses: - category='recipient': top vendors for a filter set (vendor landscape analysis) - category='awarding_subagency': which contracting offices within an agency - category='naics': which work categories got the most spending - category='psc': which product/service codes got the most spending - category='state_territory': geographic distribution - category='cfda': grant assistance listings Note: recipient category returns vendor names in ALL CAPS and may contain duplicates (subsidiaries, rebrands, re-registrations). For precise market share, apply name normalization to the returned 'name' field. At least one filter is required. An unfiltered call would silently aggregate the entire USASpending database (all years, all agencies), which is never what a caller wants.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | – | – | – |
| awarding_agency | – | – | – |
| awarding_subagency | – | – | – |
| category | string | yes | – |
| def_codes | – | – | – |
| keywords | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| page | integer | – | – |
| psc_codes | – | – | – |
| set_aside_type_codes | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_by_geography ~154
Geographic breakdown of spending. scope: 'recipient_location' (where the recipient is) or 'place_of_performance' (where the work happens). geo_layer: 'state', 'county', or 'district'. At least one filter is required. The API returns HTTP 500 on an empty filter set, so the requirement is enforced here with a clear error.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | string | – | – |
| awarding_agency | – | – | – |
| def_codes | – | – | – |
| funding_agency | – | – | – |
| geo_layer | string | – | – |
| naics_codes | – | – | – |
| psc_codes | – | – | – |
| scope | string | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_by_subaward_grouped ~222
Search subawards using the standard filters object (grouped result set). Unlike search_subawards which is scoped to a single prime, this returns subawards grouped under their primes given a filter set similar to search_awards. Useful for FFATA-wide analysis ("show me all DoD subcontracts on cyber awards in FY2026"). sort accepts: award_id, subaward_count, award_generated_internal_id, subaward_obligation. (These differ from search_subawards, which sorts by amount/action_date/etc.) Anything else returns HTTP 400 from the API.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type_codes | – | – | – |
| awarding_agency | – | – | – |
| def_codes | – | – | – |
| funding_agency | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| order | string | – | – |
| page | integer | – | – |
| psc_codes | – | – | – |
| set_aside_type_codes | – | – | – |
| sort | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_by_transaction ~237
Search at the transaction (modification) level. Unlike search_awards which returns one row per award, this returns one row per transaction (initial action plus every modification). Useful for tracking obligation events over time, ceiling adjustments, deobligations, and admin mods. recipient_uei is matched through the API's recipient text search (which covers name, UEI, and DUNS), so pass the plain 12-character UEI. Returns standard transaction fields: Action Date, Mod, Award ID, Action Type, Awarding Agency, Recipient Name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_amount_max | – | – | – |
| award_amount_min | – | – | – |
| award_type | string | – | – |
| awarding_agency | – | – | – |
| funding_agency | – | – | – |
| keywords | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| order | string | – | – |
| page | integer | – | – |
| psc_codes | – | – | – |
| recipient_uei | – | – | – |
| set_aside_type_codes | – | – | – |
| sort | string | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_over_time ~237
Aggregate spending amounts over time, grouped by fiscal year, quarter, or month. Use this to visualize spending trends, identify fiscal-year-end spikes, or compare spending patterns across years. Note: The API returns fiscal_year as a STRING. Cast to int for numeric comparisons. awarding_agency must be a TOPTIER agency name ('Department of Defense'). Military departments are subtiers: pass awarding_subagency='Department of the Navy'. A non-toptier name in awarding_agency (or a subagency that does not belong to the given toptier) silently returns all-zero aggregates. At least one filter is required (the API rejects empty filter sets with HTTP 400). Typical usage: pass time_period_start + time_period_end.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | – | – | – |
| awarding_agency | – | – | – |
| awarding_subagency | – | – | – |
| def_codes | – | – | – |
| group | string | – | – |
| keywords | – | – | – |
| naics_codes | – | – | – |
| psc_codes | – | – | – |
| recipient_name | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the USASpending.gov MCP server?
USASpending.gov is an MCP server listed in the public MCP registry as com.1102tools/usaspending-gov-mcp. USASpending.gov awards, subawards, recipients, agencies, and federal accounts. 55 tools. This page covers its PyPI package (usaspending-gov-mcp).
Is the USASpending.gov MCP server safe to use?
USASpending.gov scores 79 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 USASpending.gov MCP server expose?
USASpending.gov exposes 55 tools: search_awards, get_award_count, spending_over_time, spending_by_category, get_award_detail, and 50 more. Their descriptions and schemas cost roughly 6,850 tokens of context every time the server is loaded.
Is the USASpending.gov MCP server still maintained?
USASpending.gov 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 USASpending.gov MCP server under?
USASpending.gov declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.