Leakledger Ota Recovery MCP server
Detects OTA reconciliation exceptions and stages recovery actions until recovered revenue is posted.
C67/100grade C
Adoption
New
Little public usage data yet
Reviews
Write oneNobody has reviewed Leakledger Ota Recovery yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Leakledger Ota Recovery tools (2)
write = sends, deletes, buys or postsevaluate_exceptionFreeEvaluate one record for domain-specific exceptions and revenue/workflow risk.
tool_catalogFreeDescribe this product domain, tools, and input expectations.
Public scan report
scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it
1 low
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 783ms20/20
- Tool poisoning2 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenanceno repository listed3/15
- Maintainer identityno repository or website to verify2/10
Findings (1)
- lowNo source repository listed
maint.no-repo
Overall 67/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add --transport http leakledger-ota-recovery https://botbridge.scanforlife.net/generated/leakledger-ota-recovery/mcp
Leakledger Ota Recovery: common questions
- Is Leakledger Ota Recovery MCP server safe?
- With care: it is graded C, so read the findings first (67/100). Read the Leakledger Ota Recovery safety report
- How do I install Leakledger Ota Recovery?
- It runs remotely at botbridge.scanforlife.net. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Leakledger Ota Recovery need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Leakledger Ota Recovery maintained?
- The latest release is v0.1.0.
- Is Leakledger Ota Recovery up?
- 100% of our last 19 checks got an answer. We check remote servers about four times a day.