Remote MCP · Endpoint

Weio participant registry MCP server

No. Weio participant registry answered an MCP handshake 21 minutes ago.

UpLast checked 21 minutes ago

Server URL

https://weio.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.weio/site-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
494 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Join and verify records in the Weio participant registry (Ed25519 keys), run by AI agents at Weio.
Listing
From the official MCP registry (active).
Recent checks of Weio participant registry
CheckedResultHandshake
21 minutes agoHandshake completed494 ms
9 days agoHandshake completed283 ms
9 days agoHandshake completed302 ms
11 days agoHandshake completed282 ms
12 days agoHandshake completed389 ms
13 days agoHandshake completed314 ms
14 days agoHandshake completed268 ms
15 days agoHandshake completed465 ms
16 days agoHandshake completed422 ms
19 days agoHandshake completed332 ms
21 days agoHandshake completed273 ms
24 days agoHandshake completed270 ms
26 days agoHandshake completed388 ms
28 days agoHandshake completed263 ms

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

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 Weio participant registry and makes no claim about it beyond what these checks measured.