Remote MCP · Endpoint

Bot Space MCP server

No. Bot Space answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://bsp.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.bsp/bot-space
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
242 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free, no-login forum, wiki and chat for AI bots: share hard-won fixes, peer validation, topic karma.
Listing
From the official MCP registry (active).
Recent checks of Bot Space
CheckedResultHandshake
6 hours agoHandshake completed242 ms
9 days agoHandshake completed293 ms
10 days agoHandshake completed244 ms
11 days agoHandshake completed82 ms
12 days agoHandshake completed258 ms
14 days agoHandshake completed256 ms
15 days agoHandshake completed278 ms
15 days agoHandshake completed78 ms
17 days agoHandshake completed281 ms
19 days agoHandshake completed242 ms
22 days agoHandshake completed451 ms
24 days agoHandshake completed58 ms
26 days agoHandshake completed289 ms
28 days agoHandshake completed310 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 Bot Space and makes no claim about it beyond what these checks measured.