Koskamo

Epa Echo MCP MCP server

The Epa Echo MCP server provides access to EPA ECHO Web Services, allowing agents to search for regulated facilities, retrieve compliance history, view violation records, and access enforcement actions for CWA, CAA, and RCRA programs. It offers five tools for querying facility data, compliance status, and enforcement cases without requiring authentication.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Pipeworx
MCP endpoint (Streamable HTTP)
https://gateway.pipeworx.io/epa-echo/mcp
Vendor documentation

What you can do with it

  • Search EPA-regulated facilities by name, state, or NAICS code
  • Retrieve compliance and enforcement history for specific facilities
  • Get detailed violation records filtered by environmental program
  • Find facilities currently in significant non-compliance
Tools advertised by the last live check:
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • search_within
  • deep_research
  • discover_tools
  • resolve_entity
  • compare_entities
  • subscribe
  • unsubscribe
  • list_subscriptions
  • recent_alerts
  • entity_profile
  • recent_changes
  • validate_claim
  • company_facts
  • scan_dependency
  • bet_research
  • polymarket_arbitrage
  • polymarket_edges
  • polymarket_kalshi_spread
  • polymarket_fill_risk
  • polymarket_edge_tracker
  • kalshi_weather_edge
  • resolution_audit
  • resolution_diff
  • release_calendar_markets
  • pipeworx_trending
  • suggest_questions
  • generate_llms_txt
  • ai_visibility_check
  • scan_competitor_ai_presence
  • pipeworx_feedback
  • remember
  • recall
  • forget
  • echo_facility_search
  • echo_compliance_history
  • echo_violations
  • echo_enforcement_actions
  • echo_search_by_violation

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http epa-echo-mcp https://gateway.pipeworx.io/epa-echo/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add epa-echo-mcp --url https://gateway.pipeworx.io/epa-echo/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable epa-echo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "epa-echo-mcp": {
      "url": "https://gateway.pipeworx.io/epa-echo/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "epa-echo-mcp": {
      "type": "streamableHttp",
      "url": "https://gateway.pipeworx.io/epa-echo/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start epa-echo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "epa-echo-mcp": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/epa-echo/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http epa-echo-mcp https://gateway.pipeworx.io/epa-echo/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "epa-echo-mcp": {
      "url": "https://gateway.pipeworx.io/epa-echo/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "epa-echo-mcp": {
      "serverUrl": "https://gateway.pipeworx.io/epa-echo/mcp"
    }
  }
}

Do you run Epa Echo MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing