Remote MCP · Endpoint

BotKelp MCP server

No. BotKelp answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://www.botkelp.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.aiscimi-code/botkelp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
90 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verified component catalog over remote MCP: agents pick ids and get a project that builds.
Listing
From the official MCP registry (active).
Recent checks of BotKelp
CheckedResultHandshake
56 minutes agoHandshake completed90 ms
3 days agoHandshake completed282 ms
12 days agoHandshake completed208 ms
13 days agoHandshake completed142 ms
15 days agoHandshake completed135 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed147 ms
18 days agoHandshake completed129 ms
18 days agoHandshake completed133 ms
20 days agoHandshake completed90 ms
22 days agoHandshake completed82 ms
25 days agoHandshake completed110 ms
27 days agoHandshake completed163 ms

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

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