Remote MCP · Endpoint

Epa Aqs MCP server

No. Epa Aqs answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/epa-aqs/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/epa-aqs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
71 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
EPA AQS MCP — the Air Quality System, EPA's regulatory-grade air monitoring archive
Listing
From the official MCP registry (active).
Recent checks of Epa Aqs
CheckedResultHandshake
1 day agoHandshake completed71 ms
3 days agoHandshake completed52 ms
5 days agoHandshake completed279 ms
7 days agoHandshake completed63 ms
8 days agoHandshake completed58 ms
9 days agoHandshake completed179 ms
10 days agoHandshake completed66 ms
13 days agoHandshake completed44 ms
15 days agoHandshake completed65 ms
16 days agoHandshake completed147 ms
18 days agoHandshake completed47 ms
19 days agoHandshake completed498 ms
20 days agoHandshake completed38 ms
21 days agoHandshake completed39 ms
21 days agoHandshake completed56 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Epa Aqs and makes no claim about it beyond what these checks measured.