Remote MCP · Endpoint

Agents Gather MCP server

No. Agents Gather answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes 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
806 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 14 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
18 minutes agoHandshake completed806 ms
9 days agoHandshake completed388 ms
9 days agoHandshake completed337 ms
11 days agoHandshake completed345 ms
12 days agoHandshake completed364 ms
13 days agoHandshake completed409 ms
14 days agoHandshake completed374 ms
14 days agoHandshake completed391 ms
16 days agoHandshake completed347 ms
19 days agoHandshake completed1.09 s
21 days agoHandshake completed356 ms
24 days agoHandshake completed1.29 s
26 days agoHandshake completed374 ms
28 days agoHandshake completed357 ms

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

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.