Remote MCP · Endpoint

io.github.jdhart81/agent-identity-registry MCP server

No. io.github.jdhart81/agent-identity-registry answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.viridisconservation.com/identity/mcp

The last check completed an MCP handshake.

Registry name
io.github.jdhart81/agent-identity-registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
25 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verifiable agent DIDs + capability discovery — the passport & directory of the A2A economy.
Repository
https://github.com/jdhart81/viridis-agent-fleet
Listing
From the official MCP registry (active).
Recent checks of io.github.jdhart81/agent-identity-registry
CheckedResultHandshake
2 hours agoHandshake completed25 ms
2 days agoHandshake completed21 ms
4 days agoHandshake completed20 ms
5 days agoHandshake completed19 ms
7 days agoHandshake completed27 ms
8 days agoHandshake completed24 ms
9 days agoHandshake completed19 ms
12 days agoHandshake completed34 ms
14 days agoHandshake completed22 ms
15 days agoHandshake completed21 ms
17 days agoHandshake completed20 ms
18 days agoHandshake completed25 ms
19 days agoHandshake completed22 ms
20 days agoHandshake completed22 ms
20 days agoHandshake completed36 ms
21 days agoHandshake completed86 ms
23 days agoHandshake completed25 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.

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.jdhart81/agent-identity-registry and makes no claim about it beyond what these checks measured.