Epa Aqs
NPM · @PIPEWORX/MCP-EPA-AQS · 2 COMPONENTS
EPA AQS MCP — the Air Quality System, EPA's regulatory-grade air monitoring archive
Available components
Last scanned (1 day ago)
Scores higher than 65% of npm servers
Category Health and Science
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-aqs). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1442 tokens (~360/item across 4 items; 4 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 Management20
- Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 77
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-epa-aqs@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-aqs |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-epa-aqs/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635924984 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d627d5ba5daaaf7dcd6fb6c6c7058324dc5d099f8c781da84ad66d196b3348cbbe6e69c76eb2dc132838928bed2e6bfa1428f590bd59b3ce8b49803a6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
aqs_annual_summary ~327
EPA AQS annual summary statistics for a pollutant and area — arithmetic mean, maximum, 98th/99th percentile, exceedance counts, observation completeness and the certification status behind each. This is what attainment and trend statements are built on. Sourced from the EPA Air Quality System. Requires an EPA AQS email + key.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | EPA AQS credential as "<email>:<key>", or just "<key>" with email= set. Register at https://aqs.epa.gov/data/api/signup?email=<your-email> |
| bbox | string | – | For by=box: "minLon,minLat,maxLon,maxLat" |
| bdate | string | yes | Start date YYYY-MM-DD |
| by | string | – | Geography: "state" (default), "county", "site", "cbsa", "box" |
| cbsa | string | – | Five-digit CBSA code |
| county | string | – | Three-digit county FIPS |
| edate | string | yes | End date YYYY-MM-DD — same calendar year as bdate |
| string | – | The email the AQS key was issued to, if not folded into _apiKey | |
| limit | number | – | Max summary rows to return (default 200, max 2000) |
| param | string | yes | Pollutant parameter code(s), comma-separated, max 5, e.g. "44201" |
| site | string | – | Four-digit site number |
| state | string | – | Two-digit state FIPS |
No output schema declared.
No examples provided.
aqs_list_parameters ~291
Look up the EPA AQS code lists the other tools in this pack need — pollutant parameter codes, parameter classes, states, counties, sites and monitoring agencies. Call this FIRST to turn "ozone" into 44201 or "North Carolina" into 37. Sourced from the EPA Air Quality System. Requires an EPA AQS email + key.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | EPA AQS credential as "<email>:<key>", or just "<key>" with email= set. Register at https://aqs.epa.gov/data/api/signup?email=<your-email> |
| county | string | – | Three-digit county FIPS, e.g. "183" |
| string | – | The email the AQS key was issued to, if not folded into _apiKey | |
| list | string | yes | Which list: "classes" (parameter groups), "parametersByClass" (needs pc), "states", "countiesByState" (needs state), "sitesByCounty" (needs state + county), "cbsas", "pqaos", "mas" |
| pc | string | – | Parameter class, e.g. "CRITERIA", "AQI POLLUTANTS", "ALL" — required for parametersByClass |
| state | string | – | Two-digit state FIPS, e.g. "37" for North Carolina |
No output schema declared.
No examples provided.
aqs_monitors ~347
EPA AQS monitor metadata for an area — which pollutants are measured where, by which agency, with what method and network membership (NCore, PAMS, SLAMS), the monitoring objective, and each monitor's open and close dates. Use it to find the site codes aqs_sample_data needs and to check whether a place is monitored at all. Sourced from the EPA Air Quality System. Requires an EPA AQS email + key.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | EPA AQS credential as "<email>:<key>", or just "<key>" with email= set. Register at https://aqs.epa.gov/data/api/signup?email=<your-email> |
| bbox | string | – | For by=box: "minLon,minLat,maxLon,maxLat" |
| bdate | string | yes | Start date YYYY-MM-DD |
| by | string | – | Geography: "state" (default), "county", "site", "cbsa", "box" |
| cbsa | string | – | Five-digit CBSA code |
| county | string | – | Three-digit county FIPS |
| edate | string | yes | End date YYYY-MM-DD — same calendar year as bdate |
| string | – | The email the AQS key was issued to, if not folded into _apiKey | |
| limit | number | – | Max monitor rows to return (default 200, max 2000) |
| param | string | yes | Pollutant parameter code(s), comma-separated, max 5, e.g. "44201" |
| site | string | – | Four-digit site number |
| state | string | – | Two-digit state FIPS |
No output schema declared.
No examples provided.
aqs_sample_data ~421
Raw measured air-pollutant sample values from EPA AQS for a date range — the regulatory record, by site, county, state or CBSA. AUTHORITATIVE for "what was the actual ozone/PM2.5/lead concentration here on these dates"; this is the quality-assured archive, not the provisional real-time AQI. Sourced from the EPA Air Quality System. Requires an EPA AQS email + key.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | EPA AQS credential as "<email>:<key>", or just "<key>" with email= set. Register at https://aqs.epa.gov/data/api/signup?email=<your-email> |
| bbox | string | – | For by=box: "minLon,minLat,maxLon,maxLat" |
| bdate | string | yes | Start date YYYY-MM-DD (converted to the AQS YYYYMMDD form for you) |
| by | string | – | Geography: "state" (default), "county", "site", "cbsa", "box" |
| cbsa | string | – | Five-digit CBSA code — required for by=cbsa |
| county | string | – | Three-digit county FIPS — required for by=county/site |
| edate | string | yes | End date YYYY-MM-DD — must be in the SAME calendar year as bdate |
| string | – | The email the AQS key was issued to, if not folded into _apiKey | |
| limit | number | – | Max sample rows to return (default 200, max 2000) |
| param | string | yes | Pollutant parameter code(s), comma-separated, max 5. e.g. "44201" (ozone), "88101" (PM2.5), "42401" (SO2), "14129" (lead) |
| site | string | – | Four-digit site number — required for by=site |
| state | string | – | Two-digit state FIPS — required for by=state/county/site |
No output schema declared.
No examples provided.
How do I install the Epa Aqs MCP server?
Epa Aqs runs locally as an npm package, launched with npx -y @pipeworx/mcp-epa-aqs. 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-aqs
claude mcp add pipeworx-io-epa-aqs -- npx -y @pipeworx/mcp-epa-aqs
What is the Epa Aqs MCP server?
Epa Aqs is an MCP server listed in the public MCP registry as io.github.pipeworx-io/epa-aqs. EPA AQS MCP, the Air Quality System, EPA's regulatory-grade air monitoring archive. This page covers its npm package (@pipeworx/mcp-epa-aqs).
Is the Epa Aqs MCP server safe to use?
Epa Aqs scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Aqs MCP server expose?
Epa Aqs exposes 4 tools: aqs_list_parameters, aqs_sample_data, aqs_annual_summary, aqs_monitors. Their descriptions and schemas cost roughly 1,386 tokens of context every time the server is loaded.
Is the Epa Aqs MCP server still maintained?
Epa Aqs is still listed as active in the MCP registry. We last reached this channel on 4 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 Aqs MCP server under?
Epa Aqs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.