Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Epa Emissions

NPM · @PIPEWORX/MCP-EPA-EMISSIONS · 2 COMPONENTS

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

+3 this week 91 Trust /100

Last scanned (7 hours ago)

Scores higher than 88% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

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

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Nov 26 +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.

  • 20 Nov 26 +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.

  • 18 Nov 26 +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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 11 Nov 26 +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.

  • 9 Nov 26 +1
    • Security disclosure: unverified → fail ▼ functional
  • 8 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Analysed npm/@pipeworx/mcp-epa-emissions@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-epa-emissions
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-epa-emissions/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3635925239
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:fd208305dc956684512183a1833ce209e3ee63adf23e22ff04df49f224ca636f677ee718ef198d524dba0fc32af69b1ac0fcf68fa7af99be0cffbcc05

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~750 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ghg_emissions_by_sector ~204

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.

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

No output schema declared.

No examples provided.

ghg_facility_emissions ~191

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.

NameTypeReqDescription
facility_namestring–Optional — filter to facilities whose name contains this text.
limitnumber–Max facilities to return, ranked by emissions (default 20, max 200).
statestringyesUS state — 2-letter code ("TX", "CA") or full name ("Texas"). Required (this is state-scoped, not national).
yearnumber–Reporting year (default: latest available, ~2023).

No output schema declared.

No examples provided.

tri_chemical_releases ~101

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

NameTypeReqDescription
chemicalstringyesChemical name (e.g., "LEAD", "MERCURY", "BENZENE", "TOLUENE").
limitnumber–Max results (default 20, max 100).
statestring–Two-letter state abbreviation to filter by (optional).

No output schema declared.

No examples provided.

tri_facility_releases ~148

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.

NameTypeReqDescription
countystring–County name WITHOUT the word "County" — "Harris", not "Harris County". Matched exactly, case-insensitive.
facility_namestring–Facility name to search for (partial match).
limitnumber–Max results (default 20, max 100).
statestringyesTwo-letter state abbreviation (e.g., "TX", "CA").

No output schema declared.

No examples provided.

tri_trends ~106

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

NameTypeReqDescription
chemicalstring–Chemical name (e.g., "LEAD").
end_yearnumber–End year for the trend range (default: most recent available).
start_yearnumber–Start year for the trend range (default: 5 years ago).
statestring–Two-letter state abbreviation (e.g., "OH").

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-epa-emissions

# add to Claude Code
claude mcp add pipeworx-io-epa-emissions -- npx -y @pipeworx/mcp-epa-emissions
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.