Skip to main content
ClaudeWave

US government open-data tools for AI agents, as one MCP server - EPA, FEMA, USGS, NOAA, FAA, USACE, FDIC, HUD and more. Runs locally: npx gov-data-mcp

MCP ServersRegistry oficial0 estrellas0 forksJavaScriptMITActualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 9/20/2026
Install in Claude Code / Claude Desktop
Method: NPX · gov-data-mcp
Claude Code CLI
claude mcp add gov-data-mcp -- npx -y gov-data-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "gov-data-mcp": {
      "command": "npx",
      "args": ["-y", "gov-data-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# 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`

```bash
npx gov-data-mcp
```

## Install

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

### Claude Desktop / Claude Code / Cursor

```json
{
  "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:

| Tool | Answers |
|---|---|
| `site-due-diligence-bundle` | 20-layer go / caution / no-go verdict for one coordinate |
| `epa-contaminated-site-screener` | Phase I ESA database search at ASTM E1527-21 distances |
| `faa-drone-airspace-checker` | Part 107 LAANC and airspace verdicts, batched |
| `hifld-grid-proximity-screener` | Nearest transmission line, substation, serving utility, ISO/RTO |
| `interconnection-queue-tracker` | Generator interconnection queues across 7 ISOs |
| `fdic-ncua-health-rollup` | Bank and credit-union health with real peer cohorts |
| `fema-nri-county-risk-profile` | County and census-tract natural-hazard risk |
| `fws-wetlands-proximity-screener` | NWI wetlands within a radius, with decode columns |
| `nhd-surface-water-404-screener` | Clean Water Act §404 surface-water screen |
| `epa-drinking-water-quality-screener` | SDWA violations, lead, PFAS occurrence |
| `parcel-owner-lookup` | Assessor-roll owner of record for an address |
| `license-verifier` | 19 professional licensing boards across 9 states + OIG exclusions |

**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](https://apify.com/malonestar) 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](https://docs.apify.com/integrations/x402): an agent with a funded [Coinbase Agentic Wallet](https://docs.cdp.coinbase.com/agentic-wallet/welcome) (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](https://apify.com/apify.it/x402-awal):

```bash
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:START -->
## 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](https://apify.com/malonestar/epa-airtoxscreen-cancer-risk-screener) · [epa-contaminated-site-screener](https://apify.com/malonestar/epa-contaminated-site-screener) · [epa-drinking-water-quality-screener](https://apify.com/malonestar/epa-drinking-water-quality-screener) · [epa-ghgrp-emitter-screener](https://apify.com/malonestar/epa-ghgrp-emitter-screener) · [epa-impaired-waters-303d-screener](https://apify.com/malonestar/epa-impaired-waters-303d-screener) · [epa-nonattainment-air-permit-screener](https://apify.com/malonestar/epa-nonattainment-air-permit-screener) · [epa-rcra-corrective-action-cleanup-monitor](https://apify.com/malonestar/epa-rcra-corrective-action-cleanup-monitor) · [epa-rcra-hazwaste-generator-rollup](https://apify.com/malonestar/epa-rcra-hazwaste-generator-rollup) · [epa-repowering-brownfield-to-solar-site-finder](https://apify.com/malonestar/epa-repowering-brownfield-to-solar-site-finder) · [epa-sole-source-aquifer-screener](https://apify.com/malonestar/epa-sole-source-aquifer-screener) · [epa-tri-facility-release-rollup](https://apify.com/malonestar/epa-tri-facility-release-rollup) · [epa-tsca-cdr-chemical-site-screener](https://apify.com/malonestar/epa-tsca-cdr-chemical-site-screener) · [erns-nrc-release-incident-screener](https://apify.com/malonestar/erns-nrc-release-incident-screener) · [fuds-defense-site-screener](https://apify.com/malonestar/fuds-defense-site-screener) · [historic-land-use-sic-contaminant-screener](https://apify.com/malonestar/historic-land-use-sic-contaminant-screener) · [site-due-diligence-bundle](https://apify.com/malonestar/site-due-diligence-bundle) · [state-tank-spill-registry-screener](https://apify.com/malonestar/state-tank-spill-registry-screener) · [usgs-historical-topo-records-review](https://apify.com/malonestar/usgs-historical-topo-records-review)

**Flood, fire, quake & ground hazard** (13)

[calfire-fhsz-screener](https://apify.com/malonestar/calfire-fhsz-screener) · [cbrs-coastal-barrier-screener](https://apify.com/malonestar/cbrs-coastal-barrier-screener) · [fema-nri-county-risk-profile](https://apify.com/malonestar/fema-nri-county-risk-profile) · [fema-repetitive-loss-flood-market-screener](https://apify.com/malonestar/fema-repetitive-loss-flood-market-screener) · [karst-sinkhole-risk-screener](https://apify.com/malonestar/karst-sinkhole-risk-screener) · [nfip-flood-loss-risk-screener](https://apify.com/malonestar/nfip-flood-loss-risk-screener) · [noaa-slr-inundation-threshold-screener](https://apify.com/malonestar/noaa-slr-inundation-threshold-screener) · [noaa-storm-events-peril-climatology](https://apify.com/malonestar/noaa-storm-events-peril-climatology) · [usace-levee-flood-risk-screener](https://apify.com/malonestar/usace-levee-flood-risk-screener) · [usgs-bedrock-geology-lithology-screener](https://apify.com/malonestar/usgs-bedrock-geology-lithology-screener) · [usgs-landslide-proximity-screener](https://apify.com/malonestar/usgs-landslide-proximity-screener) · [usgs-seismic-design-screener](https://apify.com/malonestar/usgs-seismic-design-screener) · [wildfire-asset-exposure-screener](https://apify.com/malonestar/wildfire-asset-exposure-screener)

**Habitat, wetlands, protected & historic land** (9)

[blm-sage-grouse-siting-screener](https://apify.com/malonestar/blm-sage-grouse-siting-screener) · [fws-critic
ai-agentsapifydue-diligenceenvironmental-dataepafemagovernment-datamcpmcp-servermodel-context-protocolopen-datausgs

Lo que la gente pregunta sobre gov-data-mcp

¿Qué es malonestar/gov-data-mcp?

+

malonestar/gov-data-mcp es mcp servers para el ecosistema de Claude AI. US government open-data tools for AI agents, as one MCP server - EPA, FEMA, USGS, NOAA, FAA, USACE, FDIC, HUD and more. Runs locally: npx gov-data-mcp Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-09-19.

¿Cómo se instala gov-data-mcp?

+

Puedes instalar gov-data-mcp clonando el repositorio (https://github.com/malonestar/gov-data-mcp) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar malonestar/gov-data-mcp?

+

Nuestro agente de seguridad ha analizado malonestar/gov-data-mcp y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene malonestar/gov-data-mcp?

+

malonestar/gov-data-mcp es mantenido por malonestar. La última actividad registrada en GitHub es del 2026-09-19, con 0 issues abiertos.

¿Hay alternativas a gov-data-mcp?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega gov-data-mcp en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: malonestar/gov-data-mcp
[![Featured on ClaudeWave](https://claudewave.com/api/badge/malonestar-gov-data-mcp)](https://claudewave.com/repo/malonestar-gov-data-mcp)
<a href="https://claudewave.com/repo/malonestar-gov-data-mcp"><img src="https://claudewave.com/api/badge/malonestar-gov-data-mcp" alt="Featured on ClaudeWave: malonestar/gov-data-mcp" width="320" height="64" /></a>

Más MCP Servers

Alternativas a gov-data-mcp