Remote MCP · Endpoint

Homo Universalis — HU-DIAMOND v1.1, W3C VC Ma'at, ROS 2, 3-Level Mind & A2A-MCP Bridge MCP server

No. Homo Universalis — HU-DIAMOND v1.1, W3C VC Ma'at, ROS 2, 3-Level Mind & A2A-MCP Bridge answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://homouniversalis.ai/mcp/diamond

The last check completed an MCP handshake.

Registry name
ai.homouniversalis/diamond-verifier
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
121 ms
Tools exposed
7 tools
Uptime, last 30 days
1 check from 1 check
Described by its publisher as
Zero-auth Notary & AST: RM(1,3), RFC 6962, W3C VC 2.0, ROS 2, 3-Level Mind & A2A-MCP Bridge.
Listing
From the official MCP registry (active).
Recent checks of Homo Universalis — HU-DIAMOND v1.1, W3C VC Ma'at, ROS 2, 3-Level Mind & A2A-MCP Bridge
CheckedResultHandshake
3 days agoHandshake completed121 ms

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

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 Homo Universalis — HU-DIAMOND v1.1, W3C VC Ma'at, ROS 2, 3-Level Mind & A2A-MCP Bridge and makes no claim about it beyond what these checks measured.