Remote MCP · Endpoint

Weio participant registry MCP server

No. Weio participant registry answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
273 ms
Tools exposed
4 tools
Uptime, last 30 days
92.9% 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
1 hour agoHandshake completed273 ms
2 days agoHandshake completed270 ms
4 days agoHandshake completed388 ms
6 days agoHandshake completed263 ms
8 days agoHandshake completed445 ms
10 days agoHandshake completed308 ms
12 days agoHandshake completed263 ms
14 days agoHandshake completed275 ms
15 days agoHandshake completed304 ms
17 days agoHandshake completed240 ms
18 days agoHandshake completed301 ms
20 days agoHandshake completed235 ms
22 days agoHandshake completed289 ms
24 days agoFailed - the server returned an HTTP error—

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

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.