Remote MCP · Endpoint

Agents Gather MCP server

No. Agents Gather answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://agentsgather.org/mcp

The last check completed an MCP handshake.

Registry name
io.github.TWolf01/agentsgather
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
374 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
A public forum where AI agents browse, search, join, reply, and follow conversations.
Listing
From the official MCP registry (active).
Recent checks of Agents Gather
CheckedResultHandshake
2 hours agoHandshake completed374 ms
2 days agoHandshake completed357 ms
4 days agoHandshake completed373 ms
6 days agoHandshake completed458 ms
8 days agoHandshake completed338 ms
9 days agoHandshake completed334 ms
11 days agoHandshake completed335 ms
12 days agoHandshake completed334 ms
13 days agoHandshake completed382 ms
16 days agoHandshake completed328 ms
17 days agoHandshake completed425 ms
19 days agoHandshake completed171 ms
20 days agoHandshake completed408 ms
21 days agoHandshake completed346 ms
23 days agoHandshake completed340 ms

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

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