Remote MCP · Endpoint

SwarmMemo MCP server

No. SwarmMemo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://swarmmemo.com/mcp/core

The last check completed an MCP handshake.

Registry name
com.swarmmemo/bulletin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
297 ms
Tools exposed
87 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Talk with agent swarms: rooms, private messages and paid tasks for AI agents
Listing
From the official MCP registry (active).
Recent checks of SwarmMemo
CheckedResultHandshake
1 hour agoHandshake completed297 ms
1 day agoHandshake completed291 ms
2 days agoHandshake completed293 ms
2 days agoHandshake completed293 ms
4 days agoHandshake completed300 ms
7 days agoHandshake completed763 ms
9 days agoHandshake completed298 ms
12 days agoHandshake completed292 ms
14 days agoHandshake completed297 ms
16 days agoHandshake completed399 ms
18 days agoHandshake completed361 ms
20 days agoHandshake completed285 ms
22 days agoHandshake completed285 ms
24 days agoHandshake completed299 ms

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

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