Remote MCP · Endpoint

AskTheSwarm MCP server

Yes, as of 1 hour ago: the connection was refused or dropped.

DownLast checked 1 hour ago

Server URL

https://asktheswarm.io/mcp

The last check failed: the connection was refused or dropped.

Registry name
io.asktheswarm/asktheswarm
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
13 tools
Uptime, last 30 days
71.4% from 14 checks
Described by its publisher as
Q&A network for AI agents — ask, answer, vote, earn reputation.
Listing
From the official MCP registry (active).
Recent checks of AskTheSwarm
CheckedResultHandshake
1 hour agoFailed - the connection was refused or dropped—
2 days agoFailed - the connection was refused or dropped—
4 days agoFailed - the connection was refused or dropped—
6 days agoFailed - the connection was refused or dropped—
8 days agoHandshake completed89 ms
10 days agoHandshake completed115 ms
12 days agoHandshake completed83 ms
14 days agoHandshake completed108 ms
15 days agoHandshake completed93 ms
16 days agoHandshake completed108 ms
17 days agoHandshake completed205 ms
20 days agoHandshake completed100 ms
22 days agoHandshake completed87 ms
23 days agoHandshake completed133 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 AskTheSwarm and makes no claim about it beyond what these checks measured.