USASpending.gov
PYPI · USASPENDING-GOV-MCP · 2 COMPONENTS
USAspending.gov contracts, grants, loans, subawards, recipients, agencies, and federal accounts.
Available components
Last scanned (8 hours ago)
Scores higher than 72% of PyPI servers
Category Finance and Payments
Recent critical change
GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 33 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to 1102tools-dev/federal-contracting-mcps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 9508 tokens (~172/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 1.0.28 → 1.0.29 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 0
- Package version: 1.0.27 → 1.0.28 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
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 5 Nov 2026 · Analysed pypi/usaspending-gov-mcp@1.0.29
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | 1102tools-dev/federal-contracting-mcps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/1102tools-dev/federal-contracting-mcps/.github/workflows/publish-pypi.yml@refs/tags/usaspending/v1.0.29 |
| Rekor log index | 3662739707 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:71749cf179ec57ef1a5e8a34348f1e4fe5d28170035b0a23f261237f705d62bb |
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 33 packages
| Packages resolved | 33 |
|---|---|
| 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 ~509
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. date_type controls the transaction date window. Omitted (the default) or 'action_date', it selects transaction actions inside the window. 'date_signed' selects the associated award's first signing date; 'last_modified_date' selects transaction update dates. 'new_awards_only' retains in-window actions associated with awards first signed in the window. These are transaction obligation totals, not new-award counts: use new_awards_over_time for counts. Award search/count tools use a different default interval-overlap rule. date_type needs time_period_start and/or time_period_end. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | – | – | – |
| awarding_agency | – | – | – |
| awarding_subagency | – | – | – |
| category | string | yes | – |
| contract_pricing_type_codes | – | – | – |
| date_type | – | – | – |
| def_codes | – | – | – |
| extent_competed_type_codes | – | – | – |
| funding_agency | – | – | – |
| keywords | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| page | integer | – | – |
| program_numbers | – | – | – |
| psc_codes | – | – | – |
| recipient_name | – | – | – |
| set_aside_type_codes | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
spending_by_geography ~218
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. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | string | – | – |
| awarding_agency | – | – | – |
| def_codes | – | – | – |
| funding_agency | – | – | – |
| geo_layer | string | – | – |
| naics_codes | – | – | – |
| program_numbers | – | – | – |
| 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 ~392
Find matching prime awards and their cumulative FFATA report totals. Filters select prime records, but subaward_count and subaward_obligation cover all reported subawards under each prime, not just subaward actions within time_period_start/end. This ranking is not a fiscal-period subaward ranking. For dated reports, pass a returned award_generated_internal_id to search_subawards(award_id=...), read every page, and retain action_date values inside the desired period. 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. page_metadata.hasNext is worked out here: the endpoint itself always says false, even with more pages. Rows include primes with no subawards (subaward_count 0). subaward_obligation sums FFATA reports, which can repeat cumulative amounts, so a subaward_to_award_ratio above 1 is a reporting artefact, not more subcontracting than the prime. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program name.
| Name | Type | Req | Description |
|---|---|---|---|
| award_type_codes | – | – | – |
| awarding_agency | – | – | – |
| def_codes | – | – | – |
| funding_agency | – | – | – |
| limit | integer | – | – |
| naics_codes | – | – | – |
| order | string | – | – |
| page | integer | – | – |
| program_numbers | – | – | – |
| 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 ~301
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. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfda() finds numbers by program 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 | – | – |
| program_numbers | – | – | – |
| 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 ~575
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. quarter and month are FISCAL periods (month 1 = October, quarter 1 = October-December). Buckets are clipped to the window, so a calendar-2025 window returns a partial fiscal_year '2025' (January- September only) and a partial '2026' (October-December); neither is that whole fiscal year. DoD contract actions are published 90 days late, so when the window reaches into the last 90 days and DoD is in scope the answer carries a data_note: those months are understated, so don't read them as a drop. 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. date_type controls the transaction date window. Omitted (the default) or 'action_date', it selects transaction actions inside the window. 'date_signed' selects the associated award's first signing date; 'last_modified_date' selects transaction update dates. 'new_awards_only' retains in-window actions associated with awards first signed in the window. These are transaction obligation totals, not new-award counts: use new_awards_over_time for counts. Award search/count tools use a different default interval-overlap rule. date_type needs time_period_start and/or time_period_end. program_numbers filters assistance awards by assistance listing (CFDA) number, e.g. ['93.778'] for Medicaid; use it with award_type='grants', 'loans', 'direct_payments', or 'other'. autocomplete_cfd…
| Name | Type | Req | Description |
|---|---|---|---|
| award_type | – | – | – |
| awarding_agency | – | – | – |
| awarding_subagency | – | – | – |
| contract_pricing_type_codes | – | – | – |
| date_type | – | – | – |
| def_codes | – | – | – |
| extent_competed_type_codes | – | – | – |
| funding_agency | – | – | – |
| group | string | – | – |
| keywords | – | – | – |
| naics_codes | – | – | – |
| program_numbers | – | – | – |
| psc_codes | – | – | – |
| recipient_name | – | – | – |
| time_period_end | – | – | – |
| time_period_start | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
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
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 contracts, grants, loans, subawards, recipients, agencies, and federal accounts. This page covers its PyPI package (usaspending-gov-mcp).
Is the USASpending.gov MCP server safe to use?
USASpending.gov scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 9,508 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 5 November 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.