Remote MCP · Endpoint

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

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours 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
94.1% from 17 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
2 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed86 ms
4 days agoHandshake completed91 ms
5 days agoHandshake completed80 ms
7 days agoHandshake completed107 ms
8 days agoHandshake completed937 ms
9 days agoHandshake completed288 ms
12 days agoHandshake completed93 ms
13 days agoHandshake completed78 ms
15 days agoHandshake completed82 ms
17 days agoHandshake completed90 ms
18 days agoHandshake completed80 ms
19 days agoHandshake completed77 ms
20 days agoHandshake completed84 ms
20 days agoHandshake completed75 ms
21 days agoHandshake completed84 ms
23 days agoHandshake completed115 ms

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

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.