# Epa Echo (npm · @pipeworx/mcp-epa-echo)

EPA ECHO MCP — wraps EPA ECHO Web Services (free, no auth)

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-epa-echo/epa-echo-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-epa-echo/epa-echo-mcp)
- npm · `@pipeworx/mcp-epa-echo`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-epa-echo/pipeworx-mcp-epa-echo.md), [page](https://verifymcp.io/servers/pipeworx-io-epa-echo/pipeworx-mcp-epa-echo)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-epa-echo`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-epa-echo).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add pipeworx-io-epa-echo -- npx -y @pipeworx/mcp-epa-echo
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-epa-echo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epa-echo"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-epa-echo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epa-echo"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-epa-echo -- npx -y @pipeworx/mcp-epa-echo
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-epa-echo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-epa-echo"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-epa-echo --command npx --arg -y --arg @pipeworx/mcp-epa-echo
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-epa-echo:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-epa-echo"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-epa-echo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-epa-echo"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-epa-echo -t stdio -c npx -a -y @pipeworx/mcp-epa-echo
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-epa-echo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-epa-echo"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +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.

### 2026-11-01 (score 82, +1)

- [security regression] 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.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.1 → 0.2.2

### 2026-10-31 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 81)

First indexed and scored.

## MCP tools (5)

### `echo_facility_search` (~309 tokens)

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.

Input parameters:

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

### `echo_compliance_history` (~54 tokens)

Check a facility's compliance record and enforcement timeline. Returns violation status, inspection dates, quarters in violation, and enforcement actions taken.

Input parameters:

- `registry_id` (string, required): EPA Registry ID (from echo_facility_search results).

### `echo_violations` (~93 tokens)

Get violation details for a facility, filterable by program (water, air, waste). Returns violation dates, types, and current status.

Input parameters:

- `program` (string): Environmental program filter: "CWA" (water), "CAA" (air), or "RCRA" (waste). Defaults to CWA.
- `registry_id` (string, required): EPA Registry ID (from echo_facility_search results).

### `echo_enforcement_actions` (~48 tokens)

Retrieve enforcement cases against a facility. Returns action type, penalty amounts, dates, and settlement details.

Input parameters:

- `registry_id` (string, required): EPA Registry ID (from echo_facility_search results).

### `echo_search_by_violation` (~160 tokens)

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.

Input parameters:

- `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").

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-epa-echo/pipeworx-mcp-epa-echo#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-epa-echo
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-epa-echo
- Repository: https://github.com/pipeworx-io/mcp-epa-echo
- Website: https://pipeworx.io/packs/epa-echo
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-epa-echo/pipeworx-mcp-epa-echo.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-epa-echo/pipeworx-mcp-epa-echo.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-epa-echo/pipeworx-mcp-epa-echo