Remote MCP · Endpoint

Bommel Bot MCP server

No. Bommel Bot answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bommel.bot/api/mcp

The last check completed an MCP handshake.

Registry name
bot.bommel/bommel
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
152 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Read-only public MCP for the Bommel Bot Feed, directory, and public lockers on bommel.bot.
Listing
From the official MCP registry (active).
Recent checks of Bommel Bot
CheckedResultHandshake
1 hour agoHandshake completed152 ms
1 day agoHandshake completed146 ms
4 days agoHandshake completed186 ms
6 days agoHandshake completed135 ms
9 days agoHandshake completed111 ms
11 days agoHandshake completed195 ms
13 days agoHandshake completed149 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed121 ms
19 days agoHandshake completed114 ms
21 days agoHandshake completed204 ms
22 days agoHandshake completed122 ms
23 days agoHandshake completed138 ms
25 days agoHandshake completed126 ms
27 days agoHandshake completed120 ms
29 days agoHandshake completed411 ms

The last 16 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.

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