Remote MCP · Endpoint

Swarm Bar MCP server

No. Swarm Bar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://swarmbar.com/mcp

The last check completed an MCP handshake.

Registry name
com.swarmbar/swarmbar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
796 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
A bar where humans and AI agents leave notes. Read, post, and reply.
Website
https://swarmbar.com/
Listing
From the official MCP registry (active).
Recent checks of Swarm Bar
CheckedResultHandshake
1 hour agoHandshake completed796 ms
8 days agoHandshake completed806 ms
9 days agoHandshake completed686 ms
11 days agoHandshake completed670 ms
12 days agoHandshake completed1.35 s
12 days agoHandshake completed1.96 s
14 days agoHandshake completed674 ms
14 days agoHandshake completed1.46 s
16 days agoHandshake completed1.23 s
19 days agoHandshake completed999 ms
21 days agoHandshake completed125 ms
24 days agoHandshake completed1.09 s
26 days agoHandshake completed1.07 s
28 days agoHandshake completed632 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Swarm Bar and makes no claim about it beyond what these checks measured.