# Epa Emissions (npm · @pipeworx/mcp-epa-emissions)

EPA Emissions MCP — wraps EPA Envirofacts REST API (free, no auth)

- Trust score: 91/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-epa-emissions`
- Version: `0.2.1`
- 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-22.

- **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-emissions).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 806 tokens (~161/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**: 80/100
  - Stability observed for 24 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 Emissions MCP server?

Epa Emissions runs locally as an npm package, launched with npx -y @pipeworx/mcp-epa-emissions. 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-emissions -- npx -y @pipeworx/mcp-epa-emissions
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-22 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 85, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-08 (score 84, 0)

- [functional regression] Security disclosure: fail → unverified

## MCP tools (5)

### `ghg_facility_emissions` (~191 tokens)

The biggest greenhouse-gas-emitting facilities in a US state (EPA GHGRP), ranked by total CO2-equivalent emissions. Returns each facility's name, location, industry sector(s), and total metric tons CO2e. State-scoped (pass a state). Data lags ~1.5 years — latest full year is auto-selected (currently 2023) unless a `year` is given.

Input parameters:

- `facility_name` (string): Optional — filter to facilities whose name contains this text.
- `limit` (number): Max facilities to return, ranked by emissions (default 20, max 200).
- `state` (string, required): US state — 2-letter code ("TX", "CA") or full name ("Texas"). Required (this is state-scoped, not national).
- `year` (number): Reporting year (default: latest available, ~2023).

### `ghg_emissions_by_sector` (~204 tokens)

Total greenhouse-gas emissions by INDUSTRY SECTOR within a US state (EPA GHGRP) — answers 'which sectors emit the most in <state>'. Sectors: Power Plants, Refineries, Chemicals, Metals, Minerals, Pulp and Paper, Petroleum and Natural Gas Systems, Waste, etc. Returns each sector's total metric tons CO2e and facility count, ranked. State-scoped (pass a state); data lags ~1.5y so the latest full year (~2023) is auto-selected unless `year` is given.

Input parameters:

- `sector` (string): Optional — filter to one sector by name (e.g. "Power Plants", "Refineries", "Chemicals").
- `state` (string, required): US state — 2-letter code ("TX") or full name ("Texas"). Required (state-scoped, not national).
- `year` (number): Reporting year (default: latest available, ~2023).

### `tri_facility_releases` (~148 tokens)

Search EPA TRI toxic chemical release facilities by state, and optionally by COUNTY — "what toxic releases are reported in Harris County, Texas" is the shape these questions usually take. Returns facility location, county, type, and chemicals released with quantities in pounds.

Input parameters:

- `county` (string): County name WITHOUT the word "County" — "Harris", not "Harris County". Matched exactly, case-insensitive.
- `facility_name` (string): Facility name to search for (partial match).
- `limit` (number): Max results (default 20, max 100).
- `state` (string, required): Two-letter state abbreviation (e.g., "TX", "CA").

### `tri_chemical_releases` (~101 tokens)

Track toxic chemical releases by chemical name and state. Returns quantities released to air, water, and land broken down by year.

Input parameters:

- `chemical` (string, required): Chemical name (e.g., "LEAD", "MERCURY", "BENZENE", "TOLUENE").
- `limit` (number): Max results (default 20, max 100).
- `state` (string): Two-letter state abbreviation to filter by (optional).

### `tri_trends` (~106 tokens)

Analyze toxic release trends over time by state or chemical. Returns historical release data across years to identify patterns and changes.

Input parameters:

- `chemical` (string): Chemical name (e.g., "LEAD").
- `end_year` (number): End year for the trend range (default: most recent available).
- `start_year` (number): Start year for the trend range (default: 5 years ago).
- `state` (string): Two-letter state abbreviation (e.g., "OH").

## Diagnostics

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

## Score history

- 2026-11-22: 91
- 2026-11-21: 90
- 2026-11-20: 90
- 2026-11-19: 89
- 2026-11-18: 89
- 2026-11-17: 88
- 2026-11-16: 88
- 2026-11-15: 88
- 2026-11-14: 87
- 2026-11-13: 87
- 2026-11-12: 86
- 2026-11-11: 86
- 2026-11-10: 85
- 2026-11-09: 85
- 2026-11-08: 84
- 2026-11-07: 84
- 2026-11-06: 83
- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Epa Emissions MCP server?

Epa Emissions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/epa-emissions. EPA Emissions MCP, wraps EPA Envirofacts REST API (free, no auth). This page covers its npm package (@pipeworx/mcp-epa-emissions).

### Is the Epa Emissions MCP server safe to use?

Epa Emissions scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Emissions MCP server expose?

Epa Emissions exposes 5 tools: ghg_facility_emissions, ghg_emissions_by_sector, tri_facility_releases, tri_chemical_releases, tri_trends. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.

### Is the Epa Emissions MCP server still maintained?

Epa Emissions is still listed as active in the MCP registry. We last reached this channel on 22 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 Emissions MCP server under?

Epa Emissions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Epa Emissions MCP server?

VerifyMCP ran 16 checks on Epa Emissions, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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