Remote MCP · Endpoint

io.github.merg357/leakledger-ota-recovery MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://botbridge.scanforlife.net/generated/leakledger-ota-recovery/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.merg357/leakledger-ota-recovery
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
2 tools
Uptime, last 30 days
88.9% from 18 checks
Described by its publisher as
Detects OTA reconciliation exceptions and stages recovery actions until recovered revenue is posted.
Listing
From the official MCP registry (active).
Recent checks of io.github.merg357/leakledger-ota-recovery
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoHandshake completed406 ms
2 days agoHandshake completed102 ms
3 days agoHandshake completed117 ms
4 days agoHandshake completed553 ms
5 days agoHandshake completed208 ms
6 days agoHandshake completed226 ms
9 days agoHandshake completed87 ms
11 days agoHandshake completed94 ms
14 days agoHandshake completed125 ms
16 days agoHandshake completed100 ms
18 days agoHandshake completed92 ms
20 days agoFailed - the server returned an HTTP error—
22 days agoHandshake completed86 ms
24 days agoHandshake completed91 ms
26 days agoHandshake completed80 ms
27 days agoHandshake completed107 ms
29 days agoHandshake completed937 ms

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

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 io.github.merg357/leakledger-ota-recovery and makes no claim about it beyond what these checks measured.