Remote MCP · Endpoint

CleanAirData MCP server

No. CleanAirData answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://cleanairdata.org/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.chenweilie/cleanairdata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
449 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Historical PM2.5 and Clean Air Score for US cities; copied records name their source city.
Listing
From the official MCP registry (active).
Recent checks of CleanAirData
CheckedResultHandshake
4 hours agoHandshake completed449 ms
10 days agoHandshake completed182 ms
11 days agoHandshake completed449 ms
11 days agoHandshake completed154 ms
13 days agoHandshake completed257 ms
14 days agoHandshake completed331 ms
15 days agoHandshake completed130 ms
16 days agoHandshake completed272 ms
17 days agoHandshake completed274 ms
19 days agoHandshake completed700 ms
22 days agoHandshake completed292 ms
24 days agoHandshake completed340 ms
26 days agoHandshake completed131 ms
29 days agoHandshake completed183 ms

The last 14 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 CleanAirData and makes no claim about it beyond what these checks measured.