Remote MCP · Endpoint

io.github.cyanheads/epa-mcp-server MCP server

No. io.github.cyanheads/epa-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://epa.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/epa-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
143 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search EPA compliance, TRI, Superfund, drinking-water, EJScreen, and AirNow data.
Repository
https://github.com/cyanheads/epa-mcp-server
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/epa-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed143 ms
1 day agoHandshake completed263 ms
2 days agoHandshake completed268 ms
2 days agoHandshake completed243 ms
4 days agoHandshake completed317 ms
7 days agoHandshake completed284 ms
9 days agoHandshake completed268 ms
12 days agoHandshake completed276 ms
14 days agoHandshake completed305 ms
16 days agoHandshake completed229 ms
18 days agoHandshake completed181 ms
20 days agoHandshake completed145 ms
22 days agoHandshake completed143 ms
24 days agoHandshake completed109 ms
25 days agoHandshake completed132 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with io.github.cyanheads/epa-mcp-server and makes no claim about it beyond what these checks measured.