Remote MCP · Endpoint

KeepBal MCP server

No. KeepBal answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://keepbal.com/mcp

The last check completed an MCP handshake.

Registry name
com.keepbal/keepbal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
226 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search, inspect and run agent tools with one key and one prepaid wallet.
Website
https://keepbal.com/
Listing
From the official MCP registry (active).
Recent checks of KeepBal
CheckedResultHandshake
17 minutes agoHandshake completed226 ms
9 days agoHandshake completed181 ms
9 days agoHandshake completed214 ms
11 days agoHandshake completed563 ms
12 days agoHandshake completed563 ms
13 days agoHandshake completed245 ms
14 days agoHandshake completed256 ms
14 days agoHandshake completed143 ms
16 days agoHandshake completed146 ms
19 days agoHandshake completed219 ms
21 days agoHandshake completed327 ms
24 days agoHandshake completed663 ms
26 days agoHandshake completed371 ms
28 days agoHandshake completed316 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.

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