Epa Envirofacts

What Epa Envirofacts does

Epa Envirofacts exposes selected US EPA Facility Registry Service (FRS) data through the Model Context Protocol. It focuses on EPA-regulated facilities and identifies the regulatory programs associated with each site. A facility appears once in list results, with its applicable programs grouped together rather than repeated for each program.

The integration is independent and unofficial. It is provided through Pipeworx and reaches the same gateway used by other Pipeworx data-source connections.

How it works

The hosted MCP endpoint is available at https://gateway.pipeworx.io/epa-envirofacts/mcp. An MCP client can connect to that URL directly and discover the Epa Envirofacts tools. The endpoint also exposes shared Pipeworx meta-tools, including ask_pipeworx, discover_tools, search_within, and memory-related tools. These shared tools are part of the gateway connection and may make the discovered tool set larger than the three EPA-specific tools.

Pipeworx also provides a full gateway endpoint at https://gateway.pipeworx.io/mcp. Either endpoint can reach the broader Pipeworx catalog through ask_pipeworx; the scoped endpoint lists the Epa Envirofacts tools directly.

For clients that use local processes, the @pipeworx/mcp-epa-envirofacts npm package acts as a stdio bridge. It forwards requests to the hosted gateway, so the local process still needs network access and has no offline mode. The tools can also be called over HTTP through the gateway's tool API.

Setup and configuration

Add the hosted endpoint to an MCP client configuration:

{
  "mcpServers": {
    "epa-envirofacts": {
      "url": "https://gateway.pipeworx.io/epa-envirofacts/mcp"
    }
  }
}

For a local stdio connection, configure npx to run the package:

{
  "mcpServers": {
    "epa-envirofacts": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-epa-envirofacts"]
    }
  }
}

Anonymous use is available with a daily limit of 50 calls. Setting PIPEWORX_API_KEY adds an account key; a free account raises the limit to 200 calls per day. Set PIPEWORX_META_TOOLS=1 with the npm bridge to include the shared Pipeworx meta-tools in its listed tools. The package requires network access. When operating behind an HTTPS proxy, Node's fetch may require NODE_USE_ENV_PROXY=1.

Tools and capabilities

• facilities_by_zip finds EPA-regulated facilities in a US ZIP code.
• facilities_by_state searches by US state and can optionally filter by city.
• get_facility retrieves one facility using its FRS Registry ID.
• Facility results include the EPA programs associated with the site, including RCRAINFO, NPDES, AIRS, and TRI when applicable.
• The tools are keyless when used anonymously.

Limitations and notes

The service covers EPA-regulated facilities represented in the Facility Registry Service, not arbitrary places or organizations. Location searches require a US ZIP code or state, while direct retrieval requires an FRS Registry ID. Anonymous calls are capped at 50 per day, and authenticated free-account usage is capped at 200 per day. The npm bridge is a network client rather than an offline data package. This is an unofficial integration and is not affiliated with, endorsed by, or published by the EPA.