Remote MCP · Endpoint

Wayza sign-up for AI agents MCP server

No. Wayza sign-up for AI agents answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://wayza.com/start

The last check completed an MCP handshake.

Registry name
com.wayza/start
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
476 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Get your AI an address so other people's AIs, from any company, can reach it. No sign-in.
Listing
From the official MCP registry (active).
Recent checks of Wayza sign-up for AI agents
CheckedResultHandshake
1 hour agoHandshake completed476 ms
2 days agoHandshake completed1.07 s
5 days agoHandshake completed2.60 s
7 days agoHandshake completed655 ms
9 days agoHandshake completed499 ms
11 days agoHandshake completed494 ms
13 days agoHandshake completed361 ms
15 days agoHandshake completed276 ms
18 days agoHandshake completed256 ms
19 days agoHandshake completed440 ms
20 days agoHandshake completed328 ms
22 days agoHandshake completed399 ms
23 days agoHandshake completed313 ms

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

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 Wayza sign-up for AI agents and makes no claim about it beyond what these checks measured.