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 claude_desktop_config.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

Every tool in this catalog is eligible for Apify's agentic payments: an agent with a funded Coinbase Agentic Wallet (USDC on Base, $1 minimum) buys a prepaid Apify token over the x402 protocol and uses it as APIFY_TOKEN — no account, no billing setup, no API key. The ready-made skill is apify.it/x402-awal:

npx -y awal auth login <email>            # one-time wallet auth
npx awal x402 pay 'https://agi.apify.com/protocols/x402/prepaid-tokens?amount=5&currency=usd' --max-amount 5000000 --json
# → returns a bearer token; export it as APIFY_TOKEN and start this server as usual

The prepaid balance is an absolute spending cap and expires after 14 days. Every tool here charges only per result — none pass platform usage through, none require full permissions, and none run in Standby mode, which are the three things that make an Actor ineligible. Prices are in the catalog (usdPer1000Results on every search hit), so an agent can see the cost before spending.

On honest answers

These actors are built around one rule: a failure must never be presentable as "nothing was found." That distinction matters most in exactly the cases people use this for — telling a buyer a property is clear of contamination, telling a pilot an airspace is uncontrolled, telling a lender a borrower is unlicensed.

So this server:

• reports run_status on every call, and never attaches a rows key to a run that did not succeed
• distinguishes "the run SUCCEEDED and the source genuinely matched nothing" from "the run failed" in the response text, explicitly
• retries transient Apify 429/5xx, then fails loudly saying the platform failed and no conclusion should be drawn about the government source
• treats an unknown tool name as a catalog miss, never as an empty result

The underlying actors carry the same discipline: per-source status on every row, null meaning not checked rather than checked and negative, live drift assertions that fail the run when an upstream silently truncates, and pagination guards on sources that answer HTTP 200 with a partial payload. Each actor's Store page documents the specific traps it defends against.

Coverage

120 tools, every one reading an official US government API or bulk file. The MCP server exposes 15 of them directly — twelve named tools plus search-gov-data-tools, describe-gov-data-tool and run-gov-data-tool, which reach the rest — because agents choose badly when handed more than about twenty tools.

Each entry links to its full input/output schema, pricing and worked examples.

Contamination & environmental due diligence (18)

epa-airtoxscreen-cancer-risk-screener · epa-contaminated-site-screener · epa-drinking-water-quality-screener · epa-ghgrp-emitter-screener · epa-impaired-waters-303d-screener · epa-nonattainment-air-permit-screener · epa-rcra-corrective-action-cleanup-monitor · epa-rcra-hazwaste-generator-rollup · epa-repowering-brownfield-to-solar-site-finder · epa-sole-source-aquifer-screener · epa-tri-facility-release-rollup · epa-tsca-cdr-chemical-site-screener · erns-nrc-release-incident-screener · fuds-defense-site-screener · historic-land-use-sic-contaminant-screener · site-due-diligence-bundle · state-tank-spill-registry-screener · usgs-historical-topo-records-review

Flood, fire, quake & ground hazard (13)

calfire-fhsz-screener · cbrs-coastal-barrier-screener · fema-nri-county-risk-profile · fema-repetitive-loss-flood-market-screener · karst-sinkhole-risk-screener · nfip-flood-loss-risk-screener · noaa-slr-inundation-threshold-screener · noaa-storm-events-peril-climatology · usace-levee-flood-risk-screener · usgs-bedrock-geology-lithology-screener · usgs-landslide-proximity-screener · usgs-seismic-design-screener · wildfire-asset-exposure-screener

Habitat, wetlands, protected & historic land (9)