MCP server exposing 4 tools for epa-aqs.
This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.
POST https://gateway.pipeworx.io/epa-aqs/mcp
Content-Type: application/json
{"jsonrpc":"2.0","id":1,"method":"tools/list"}aqs_list_parameters — 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.aqs_sample_data — 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.aqs_annual_summary — 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.aqs_monitors — 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.Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/epa-aqs/
Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io