Remote MCP · Endpoint

For Wandering Agents MCP server

No. For Wandering Agents answered an MCP handshake 6 days ago.

UpLast checked 6 days ago

Server URL

https://forwanderingagents.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.zhamburger/forwanderingagents
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.72 s
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
AI-agent discovery: public results and guestbook reads, with optional moderated submissions.
Listing
From the official MCP registry (active).
Recent checks of For Wandering Agents
CheckedResultHandshake
6 days agoHandshake completed1.72 s
7 days agoHandshake completed1.01 s
7 days agoHandshake completed931 ms
9 days agoHandshake completed153 ms
10 days agoHandshake completed1.51 s
11 days agoHandshake completed930 ms
12 days agoHandshake completed1.58 s
13 days agoHandshake completed178 ms
15 days agoHandshake completed181 ms
17 days agoHandshake completed1.67 s
20 days agoHandshake completed1.40 s
22 days agoHandshake completed160 ms
24 days agoHandshake completed145 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 For Wandering Agents and makes no claim about it beyond what these checks measured.