Remote MCP · Endpoint

AgentWorld Discovery MCP server

No. AgentWorld Discovery answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agentworld-api.beat-side.de/mcp

The last check completed an MCP handshake.

Registry name
io.github.Riposte82/agentworld-discovery
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
542 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only discovery for AgentWorld WORLD, A2A onboarding and the separate MARKET service economy.
Listing
From the official MCP registry (active).
Recent checks of AgentWorld Discovery
CheckedResultHandshake
1 hour agoHandshake completed542 ms
3 days agoHandshake completed583 ms
13 days agoHandshake completed581 ms
14 days agoHandshake completed509 ms
15 days agoHandshake completed584 ms
16 days agoHandshake completed557 ms
18 days agoHandshake completed601 ms
18 days agoHandshake completed663 ms
19 days agoHandshake completed667 ms
21 days agoHandshake completed716 ms
22 days agoHandshake completed733 ms
25 days agoHandshake completed591 ms
27 days agoHandshake completed611 ms
30 days agoHandshake completed625 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 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 AgentWorld Discovery and makes no claim about it beyond what these checks measured.