Usaspending Gov MCP Server

usaspending-gov-mcp PyPI v1.0.5

Published by 1102tools-dev — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for USASpending.gov federal contract and award data

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

low Shell/command execution in packaging/dev tooling (tests/test_tool_profiles.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_tool_profiles.py:19`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: "] = profile return subprocess.run( [ sys.executable, "-c", (

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_tool_profiles.py

Tools 55

Each tool and what it can reach — statically extracted from the published source.

  • get_award_detailingests untrusted input
  • autocomplete_awarding_agencyno sensitive capability
  • autocomplete_cfdano sensitive capability
  • autocomplete_funding_agencyno sensitive capability
  • autocomplete_glossaryno sensitive capability
  • autocomplete_naicsno sensitive capability
  • autocomplete_pscno sensitive capability
  • autocomplete_recipientno sensitive capability
  • awards_last_updatedno sensitive capability
  • get_agency_awardsno sensitive capability
Show 45 more tools ↓
  • get_agency_budgetary_resourcesno sensitive capability
  • get_agency_federal_accountsno sensitive capability
  • get_agency_object_classesno sensitive capability
  • get_agency_obligations_by_award_categoryno sensitive capability
  • get_agency_overviewno sensitive capability
  • get_agency_program_activitiesno sensitive capability
  • get_agency_sub_agenciesno sensitive capability
  • get_award_countno sensitive capability
  • get_award_federal_account_countno sensitive capability
  • get_award_fundingno sensitive capability
  • get_award_funding_rollupno sensitive capability
  • get_award_subaward_countno sensitive capability
  • get_award_transaction_countno sensitive capability
  • get_award_types_referenceno sensitive capability
  • get_def_codes_referenceno sensitive capability
  • get_federal_account_detailno sensitive capability
  • get_federal_account_fy_snapshotno sensitive capability
  • get_federal_account_object_classesno sensitive capability
  • get_federal_account_program_activitiesno sensitive capability
  • get_glossaryno sensitive capability
  • get_idv_activityno sensitive capability
  • get_idv_amountsno sensitive capability
  • get_idv_childrenno sensitive capability
  • get_idv_fundingno sensitive capability
  • get_idv_funding_rollupno sensitive capability
  • get_naics_detailsno sensitive capability
  • get_psc_filter_treeno sensitive capability
  • get_recipient_childrenno sensitive capability
  • get_recipient_profileno sensitive capability
  • get_state_profileno sensitive capability
  • get_submission_periodsno sensitive capability
  • get_transactionsno sensitive capability
  • list_federal_accountsno sensitive capability
  • list_statesno sensitive capability
  • list_toptier_agenciesno sensitive capability
  • lookup_piidno sensitive capability
  • new_awards_over_timeno sensitive capability
  • search_awardsno sensitive capability
  • search_recipientsno sensitive capability
  • search_subawardsno sensitive capability
  • spending_by_categoryno sensitive capability
  • spending_by_geographyno sensitive capability
  • spending_by_subaward_groupedno sensitive capability
  • spending_by_transactionno sensitive capability
  • spending_over_timeno sensitive capability

What this scan could not see

Versions 6

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.5 latest A 96/100 1 1.13.0 2026-08-25
v1.0.4 A 96/100 1 1.12.1 2026-08-23
v1.0.3 A 96/100 0 1.12.1 2026-08-22
v1.0.2 A 96/100 0 1.12.1 2026-08-18
v1.0.0 A 96/100 0 1.12.1 2026-08-16
Show 1 more version ↓
v0.3.2 A 96/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/usaspending-gov-mcp/badge.svg)](https://mcptrustchecker.com/registry/usaspending-gov-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/usaspending-gov-mcp"><img src="https://mcptrustchecker.com/registry/usaspending-gov-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/usaspending-gov-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan usaspending-gov-mcp --online --registry pypi

Use the free API → How scoring works

More in Other