USASpending.gov MCP server
online · 100% uptimeUSAspending.gov contracts, grants, loans, subawards, recipients, agencies, and federal accounts.
not scanned yet
24 stars619 downloads/wk
Reviews
Write oneNobody has reviewed USASpending.gov yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
USASpending.gov tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How USASpending.gov compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 958 ms
- faster than 12% of 30,031 servers
- GitHub stars
- 24
- more than 91% of 28,688 servers
- Downloads a week
- 619
- more than 91% of 12,191 servers with a package
Release history: 7 versions in the registry since 2026-09-13, latest 2026-11-03, typically one every 6 days.
Install USASpending.gov in Claude Code, Cursor or VS Code
claude mcp add --transport http usaspending-gov-mcp https://usaspending.1102tools.com/mcp
What the publisher says
From the USASpending.gov repository's README, as published. We do not edit it. Read it on GitHub
Federal contracting MCPs
Read-only source tools for federal contracting research: opportunities, awards, company records, labor pricing, travel rates, regulations, and rulemaking.
Explore 1102tools · Find a matching prompt · Download the MCP prompt guide
Available in ChatGPT
USAspending, GSA CALC+, and eCFR are also available as published plugins in the ChatGPT directory. Open a listing below to install and connect it in ChatGPT. These hosted plugins require no user API key or local Python setup.
After connecting, choose a matching prompt and replace the bracketed details. If a prompt lists multiple MCPs, connect every one it requires. For other sources or compatible MCP clients, use the server setup instructions below.
Server catalog
Choose the sources your work needs. Each server directory contains its own README, code, configuration, tests, and release notes.
Install
- For the three published ChatGPT plugins, use the directory links above. For other sources or MCP clients, open the selected server's README and follow its installation and configuration instructions.
- Configure any required API keys outside chat. The server README identifies the exact environment variables and access limits.
- Restart or reconnect the client as needed, and confirm the server's tools are visible. Where provided, getaccessstatus reports local credential readiness; it does not validate the key with the upstream provider.
- Choose a prompt, connect every MCP named beneath it, and replace the bracketed details.
A prompt does not install a server. Local command configuration and remote endpoint configuration differ; use the supported setup documented for the selected server. The ChatGPT directory links above identify the three published plugins; other servers use their documented setup instructions.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
USASpending.gov: common questions
- Is USASpending.gov MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the USASpending.gov safety report
- How do I install USASpending.gov?
- It runs remotely at usaspending.1102tools.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does USASpending.gov need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is USASpending.gov maintained?
- The last commit was 32 days ago (2026-10-03). The latest release is v1.0.29.
- Is USASpending.gov up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does USASpending.gov compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 958 ms (faster than 12% of 30,031 servers). Full comparison.