mcpdirectory.dev
9,129 servers · updated 23 Sept

Usaspending Gov MCP server

community Active last commit 10 d
{
  "mcpServers": {
    "ecfr": {
      "command": "uvx",
      "args": [
        "usaspending-gov-mcp",
        "--refresh-package",
        "ecfr-mcp",
        "--from",
        "ecfr-mcp"
      ],
      "env": {
        "SAM_API_KEY": "<sam_api_key>",
        "DEMO_KEY": "<demo_key>"
      }
    }
  }
}
file .mcp.json (in your project root)install uvx usaspending-gov-mcpversion 0.3.2

What it does

This server exposes federal contracting data from USASpending.gov and eight other federal sources including SAM.gov, GSA CALC+, BLS OEWS, eCFR, Federal Register, Regulations.gov, and Acquisition.gov. It is for developers building assistants that need to query real federal APIs deterministically rather than relying on model recall.

  • Look up federal contract awards, subawards, and recipient information from USASpending.gov.
  • Query wage and employment data from Bureau of Labor Statistics OEWS for government cost estimates.
  • Search federal regulations, rules, and acquisition policies across eCFR, Federal Register, and Regulations.gov.

Tools this server exposes

ToolDoes
get_access_statusCheck whether required API credentials are configured locally for each server.

This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.