epa-mcp-server MCP Server

Search EPA compliance, TRI, Superfund, drinking-water, EJScreen, and AirNow data.

Publisher claimed. No tool list reported, and Pod has not connected to this server.

Status

Pod has not dialled epa-mcp-server yet, so everything on this page is what its publisher reported rather than what we observed. Registries describe servers; they do not connect to them. Until a check runs, treat the tool list below as a claim.

Connect

Published as @cyanheads/epa-mcp-server on npm. Runs locally.

Known issues

22 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded — those are release checklists and internal refactors, not things that will go wrong for you. Showing 12.

Most discussed

feat(ejscreen): add EJSCREEN environmental justice scores

The server covers facility compliance (ECHO), TRI releases, Superfund sites, drinking water systems, and AirNow AQI — all facility or media-specific endpoints. EPA's EJSCREEN environmental justice screening tool is completely absent. EJSCREEN is now the primary lens for environmental justice analysis in regulatory, legal, and community contexts, and is actively used in EPA permitting decisions and Title VI complaints.

Proposal

Add an epa_get_ejscreen tool w

Read the thread · 2026-05-26 · closed · 2 comments

bug(epa_search_violations): always returns 0 cases — ECHO case_rest_services.get_case_info does not include a Cases array

Server version

0.1.2

mcp-ts-core version

^0.9.9

Runtime

Bun

Runtime version

1.3.11

Transport

HTTP (Streamable)

Description

epa_search_violations always returns { cases: [], totalCount: 0 } regardless of inputs. The ECHO case_rest_services.get_case_info endpoint does not return a Cases array in its response — it returns cluster/summary data only. The service reads data.Results?.Cases ?? [], which always falls back to [].

Steps to reproduce

1. C

Read the thread · 2026-05-26 · closed · 2 comments

bug(epa_get_facility): always fails — ECHO get_facility_info does not accept FRS Registry IDs via p_id

Server version

0.1.2

mcp-ts-core version

^0.9.9

Runtime

Bun

Runtime version

1.3.11

Transport

HTTP (Streamable)

Description

epa_get_facility fails for every Registry ID with ECHO returned no facility for Registry ID "...". Check the ID and try again. The ECHO get_facility_info endpoint's p_id parameter accepts program-specific facility IDs (e.g. RCRA handler ID WAD988470605), not FRS Registry IDs (e.g. 110005351555). Step 1 of getFacility() fetches

Read the thread · 2026-05-26 · closed · 2 comments

bug(epa_get_air_quality): AirNow cache key fix incomplete — colons in kind argument still crash every call

Server version

0.1.2

mcp-ts-core version

^0.9.9

Runtime

Bun

Runtime version

1.3.11

Transport

HTTP (Streamable)

Description

epa_get_air_quality crashes on every call with -32007 Key contains invalid characters. The fix in v0.1.1 (commit 592df81) addressed = and & in the params segment of the cache key but left colons in the kind argument untouched. The storage key validator prohibits colons; the resulting keys still contain three colons and are rejecte

Read the thread · 2026-05-26 · closed · 2 comments

ux(epa_get_facility): description leaks implementation detail — mentions 'ECHO DFR endpoints in parallel'

Server version

0.1.0

mcp-ts-core version

0.9.9

Runtime

Node.js

Runtime version

Node 24.x

Transport

HTTP (Streamable HTTP)

OS

macOS 15.x

Description

The epa_get_facility tool description includes the phrase "from multiple ECHO DFR endpoints in parallel" — this is an implementation detail (specific API endpoint names and execution strategy) that shouldn't appear in the tool description. Descriptions should describe what the tool does, not *how it's impl

Read the thread · 2026-05-26 · closed · 2 comments

Most recent

feat(config): default MCP_SESSION_MODE to stateless across env, Docker, and src

Dockerfile sets ENV MCP_SESSION_MODE="stateless", but .env.example carries a commented # MCP_SESSION_MODE=stateful, whose comment documents the value set as stateful | stateless (default: stateful). The container and the same code run via bunx, npm start, or from source therefore resolve to different session modes — stateless in Docker, stateful everywhere else, since the framework schema defaults to auto and auto resolves to stateful.

Related: cyanheads/mcp-ts-core#376

Read the thread · 2026-08-22 · open · 0 comments

bug(epa_get_tri_releases): facility_id handoff points at epa_search_facilities, which returns FRS registry IDs

epa_get_tri_releases requires a facility_id that its own description sources from the wrong tool:

Obtain facility_id (TRI facility ID) from epa_search_facilities.

epa_search_facilities is the ECHO compliance tool. Its facility records are keyed by registryId — the FRS registry identifier — and it carries TRI data only as an aggregate quantity field (triReleasesTransfersInLbs), not as a TRI facility identifier.

The tool that does surface the right identifier is `epa_search_tri_re

Read the thread · 2026-08-11 · open · 1 comment

refactor(naming): adopt program-grouped tool naming — epa_