Epa Echo
NPM · @PIPEWORX/MCP-EPA-ECHO · 2 COMPONENTS
EPA ECHO MCP — wraps EPA ECHO Web Services (free, no auth)
Available components
Last scanned (3 hours ago)
Scores higher than 76% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-epa-echo). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 720 tokens (~144/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.2 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-epa-echo@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-epa-echo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-epa-echo/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635925121 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:01446f31715cbb25eaa67a68f9ca6175b73807d9e86da3a4d4a1a81add83b6c978b77d83a12f8b20b78164225bb184106a6f9e30b3227105b5fdc8867 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
echo_compliance_history ~54
Check a facility's compliance record and enforcement timeline. Returns violation status, inspection dates, quarters in violation, and enforcement actions taken.
| Name | Type | Req | Description |
|---|---|---|---|
| registry_id | string | yes | EPA Registry ID (from echo_facility_search results). |
No output schema declared.
No examples provided.
echo_enforcement_actions ~48
Retrieve enforcement cases against a facility. Returns action type, penalty amounts, dates, and settlement details.
| Name | Type | Req | Description |
|---|---|---|---|
| registry_id | string | yes | EPA Registry ID (from echo_facility_search results). |
No output schema declared.
No examples provided.
echo_facility_search ~309
Search EPA-regulated facilities by name, state, ZIP code, city, or industry code. facility_name uses a case-insensitive starts-with match; prepend % for a contains search (e.g., "%Exxon%" finds any facility with "Exxon" in its name). Combine at least two filters — a bare state is rejected upstream for large states ({state: "TX"} alone matches ~344,000 facilities and errors). Good queries: {facility_name: "%Exxon%", state: "TX"}, {city: "Baytown", state: "TX"}, {zip: "94025"}, {naics: "3251", state: "TX"}. Returns facility IDs, addresses, lat/long, compliance status, inspection/enforcement counts, and total penalties.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name (e.g., "Baytown"). |
| facility_name | string | – | Facility name — starts-with match by default; use % wildcard for contains search, e.g., "%Exxon%" or "%Baytown%". |
| limit | number | – | Max results to return (default 20, max 100). |
| naics | string | – | NAICS industry code, 2-6 digits — prefix match (e.g., "3251" = basic chemical manufacturing). Pair with state; alone it matches too many facilities. |
| state | string | – | Two-letter state abbreviation (e.g., "TX"). |
| zip | string | – | ZIP code. |
No output schema declared.
No examples provided.
echo_search_by_violation ~160
Find EPA-regulated facilities currently flagged with an identified violation, filterable by state and environmental program (CWA/CAA/RCRA/ALL). EPA ECHO has no server-side violation filter, so this scans up to 1,000 facilities for the state and returns the ones in violation — it is a sample, not an exhaustive statewide count. Returns facility IDs, names, addresses, and compliance status per program.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return (default 20, max 100). |
| program | string | – | Program filter: "CWA", "CAA", "RCRA", or "ALL" (default "ALL"). |
| state | string | – | Two-letter state abbreviation (e.g., "TX"). |
No output schema declared.
No examples provided.
echo_violations ~93
Get violation details for a facility, filterable by program (water, air, waste). Returns violation dates, types, and current status.
| Name | Type | Req | Description |
|---|---|---|---|
| program | string | – | Environmental program filter: "CWA" (water), "CAA" (air), or "RCRA" (waste). Defaults to CWA. |
| registry_id | string | yes | EPA Registry ID (from echo_facility_search results). |
No output schema declared.
No examples provided.
How do I install the Epa Echo MCP server?
Epa Echo runs locally as an npm package, launched with npx -y @pipeworx/mcp-epa-echo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-epa-echo
claude mcp add pipeworx-io-epa-echo -- npx -y @pipeworx/mcp-epa-echo
What is the Epa Echo MCP server?
Epa Echo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/epa-echo. EPA ECHO MCP, wraps EPA ECHO Web Services (free, no auth). This page covers its npm package (@pipeworx/mcp-epa-echo).
Is the Epa Echo MCP server safe to use?
Epa Echo scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Epa Echo MCP server expose?
Epa Echo exposes 5 tools: echo_facility_search, echo_compliance_history, echo_violations, echo_enforcement_actions, echo_search_by_violation. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.
Is the Epa Echo MCP server still maintained?
Epa Echo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Epa Echo MCP server under?
Epa Echo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.