Remote MCP · Endpoint

Homo Universalis — ROS 2 Humanoid Robotics, 3-Level Voice Consciousness & W3C VC Notary MCP server

No. Homo Universalis — ROS 2 Humanoid Robotics, 3-Level Voice Consciousness & W3C VC Notary answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://homouniversalis.ai/mcp/diamond?pillar=humanoid-symbiosis

The last check completed an MCP handshake.

Registry name
ai.homouniversalis/robotics-ros2-humanoid-embodied-ai-safety-proxemics-eu-ai-act-ieee-7001-w3c-vc-verifiable-credentials-human-dignity-guardrails-compliance-audit
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
335 ms
Tools exposed
7 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Zero-auth ROS 2 Humanoid, Q3 Proxemics, 3-Level Voice Arbiter, A2A-MCP Bridge & W3C VC 2.0.
Listing
From the official MCP registry (active).
Recent checks of Homo Universalis — ROS 2 Humanoid Robotics, 3-Level Voice Consciousness & W3C VC Notary
CheckedResultHandshake
10 hours agoHandshake completed335 ms
4 days agoHandshake completed172 ms
7 days agoHandshake completed107 ms

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

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 — ROS 2 Humanoid Robotics, 3-Level Voice Consciousness & W3C VC Notary and makes no claim about it beyond what these checks measured.