Remote MCP · Endpoint

io.github.jdhart81/regulatory-radar MCP server

No. io.github.jdhart81/regulatory-radar answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.viridisconservation.com/regulatory-radar/mcp

The last check completed an MCP handshake.

Registry name
io.github.jdhart81/regulatory-radar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
85 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
California, US, and global climate compliance scans with source-linked deadlines.
Listing
From the official MCP registry (active).
Recent checks of io.github.jdhart81/regulatory-radar
CheckedResultHandshake
2 hours agoHandshake completed85 ms
2 days agoHandshake completed65 ms
4 days agoHandshake completed78 ms
5 days agoHandshake completed54 ms
7 days agoHandshake completed59 ms
8 days agoHandshake completed40 ms
9 days agoHandshake completed49 ms
12 days agoHandshake completed61 ms
14 days agoHandshake completed49 ms
15 days agoHandshake completed21 ms
17 days agoHandshake completed20 ms
18 days agoHandshake completed210 ms
19 days agoHandshake completed21 ms
20 days agoHandshake completed22 ms
20 days agoHandshake completed26 ms
22 days agoHandshake completed27 ms
23 days agoHandshake completed20 ms

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

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 io.github.jdhart81/regulatory-radar and makes no claim about it beyond what these checks measured.