{
  "markdown": "# EPA ECHO — Enforcement and Compliance History\n\nThe U.S. Environmental Protection Agency's Enforcement and Compliance History Online (ECHO). Facility-level compliance status, inspection history, formal and informal enforcement actions, permit data (Clean Air Act, Clean Water Act, RCRA, etc.). The authoritative source for \"is this facility in trouble with EPA?\" Free, no auth.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Why this matters for AI agents\n\nFor environmental risk assessment, regulatory due diligence, and ESG analysis, EPA ECHO is the primary source for what's actually happening with EPA enforcement. Self-reported emissions data is one thing; ECHO tells you when the EPA actually showed up and took action.\n\nCommon flows:\n\n- **Facility lookup.** \"Find facilities for company X.\" → `echo_facility_search({name: \"X\"})` → matching facilities with their EPA Registry IDs, compliance status, recent enforcement.\n- **Facility detail.** Once you have a facility ID, follow-up tools surface inspection history, permits, violations, formal actions.\n- **Geographic search.** Find all facilities in a ZIP code, county, or state with active enforcement.\n\nUsed by the `environmental_risk` recipe alongside GHG emissions and TRI data.\n\n## Auth\n\nNone. ECHO is fully public and free. Pipeworx forwards a polite User-Agent.\n\n## What EPA tracks via ECHO\n\n| Program | What it covers |\n|---|---|\n| **CAA** (Clean Air Act) | Major emitters, NSPS standards, NESHAP toxic air pollutants |\n| **CWA / NPDES** | Water discharge permits, effluent limits, biosolids |\n| **RCRA** | Hazardous waste generators, transporters, treatment/storage/disposal facilities |\n| **SDWA** | Public water systems |\n| **TRI** | Toxic Release Inventory reporters (separate `tri_facility_releases` tool) |\n\nA single facility can be regulated under multiple programs; ECHO surfaces all.\n\n## Compliance status decoded\n\n| Status | Meaning |\n|---|---|\n| In compliance | No active violations |\n| Significant Violator | Major program-level violation |\n| High Priority Violator (HPV) | Air-program-specific severe non-compliance |\n| Formal action issued | EPA or state has filed a legal action |\n| Informal action | Warning letter, notice of violation |\n| Active enforcement | An enforcement case is open |\n\nFor risk-tier assessment, \"Significant Violator\" + \"Active enforcement\" is High; clean record + closed historical violations is Low.\n\n## Common pitfalls\n\n- **Multi-facility companies.** Big companies have many EPA-regulated facilities; the company-name search returns all matches. Cluster by parent company in your output, not by facility.\n- **State-delegated programs.** Most EPA programs are administered by state environmental agencies. ECHO has the data but enforcement-action attribution can name the state, not EPA.\n- **Permit ≠ enforcement.** A facility holding a Clean Air Act Title V permit isn't \"in trouble\" — most major emitters need them. Distinguish permits (operating authorization) from enforcement (regulatory action).\n- **Lag.** ECHO updates monthly; settlements and recent inspections may not appear for 30–60 days.\n- **Self-reported data.** Compliance status often derives from self-reported monitoring data. The most damning enforcement signal is usually formal action, not raw violation counts.\n- **Closed facilities.** Decommissioned facilities still appear in ECHO with historical records. Filter to \"Active\" facility status for current operations only.\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"epa-echo\": {\n      \"url\": \"https://gateway.pipeworx.io/epa-echo/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/epa-echo/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Epa Echo data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 5549,
  "sha": "18d12a125e85c722b1d9cfd9aababfb6698cb4cf76e72eacf7f2ad4359fa854e",
  "repo_slug": "pipeworx-io/mcp-epa-echo",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_epa_echo_f91fdfdc/readme"
}