US Government Data MCP server

gov-data-mcp

120 US government open-data tools, as one MCP server.

EPA, FEMA, USGS, NOAA, FAA, USACE, FDIC, HUD, NRCS, HRSA, CMS, county assessor rolls and state licensing boards — all reachable as agent-callable tools, all reading directly from official government APIs and bulk files. No scraping, no HTML parsing, no rate-limit roulette.

mcp-name: io.github.malonestar/gov-data-mcp

npx gov-data-mcp

Install

You need a free Apify API token from console.apify.com/settings/integrations. Apify's free tier includes monthly platform credit that covers evaluating every tool here.

Claude Desktop / Claude Code / Cursor

{
  "mcpServers": {
    "gov-data": {
      "command": "npx",
      "args": ["-y", "gov-data-mcp"],
      "env": { "APIFY_TOKEN": "apify_api_..." }
    }
  }
}

Claude Desktop reads claudedesktopconfig.json; Claude Code reads .mcp.json in your project; Cursor reads .cursor/mcp.json. The block is identical in all three.

What you get

12 dedicated tools for the highest-traffic questions, callable directly:

Plus three tools that reach the other 108:

• search-gov-data-tools — find a tool by keyword, agency or topic
• describe-gov-data-tool — full input schema for any tool in the catalog
• run-gov-data-tool — run any tool in the catalog

The catalog is bundled, so discovery costs nothing. Ask your agent "what government data tools do you have for flood risk?" and it will search all 120.

Example prompts

Screen 1200 Broadway, Denver CO for environmental risk under ASTM E1527-21 and tell me which findings fall inside the standard's search distance.

I'm siting a 40 MW solar project at 41.88, -93.10. Check grid proximity, prime farmland, wetlands, critical habitat and the interconnection queue, then tell me what would kill the project.

Can I fly a Part 107 mission at these six coordinates, and which ones need a DroneZone authorization rather than LAANC?

Which Texas banks show the 2006 CRE-concentration guidance flagged on both prongs?

How it works

Each tool is a published Apify Actor that this server invokes through the Apify API. The server starts the run, waits for a terminal state, and returns the rows.

Billing is to your own Apify account at each actor's published pay-per-result rate, listed on its Store page. Free-tier credit covers evaluation. A run that fails bills nothing beyond a fractional actor-start charge.

Every result carries the run_id and a console.apify.com URL, so any claim an agent makes from this server can be traced back to the exact run that produced it.

No Apify account? Agents can pay per run with x402

Shortened. The full README is on GitHub.