Leakledger Ota Recovery

io.github.merg357Published by GitHub account merg357v0.1.0Updated Oct 24, 2026

Detects OTA reconciliation exceptions and stages recovery actions until recovered revenue is posted.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that evaluates OTA reconciliation records for exceptions and revenue risk, and describes its own product domain and tools.

What you can do
Evaluate a single record for domain-specific exceptions and revenue/workflow risk, staging recovery actions until recovered revenue is posted. Retrieve a description of the product domain, its tools and expected inputs.
When to use it
Useful when an assistant needs to triage OTA reconciliation records or flag revenue and workflow exceptions before recovery actions are posted.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. No authentication is declared.
Before you install
The server is remote and unauthenticated, so records sent to it leave your environment. It stages recovery actions, so check what is written or changed before relying on results.

Installation

In SourceWeft

  1. Open Leakledger Ota Recovery in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.merg357%2Fleakledger-ota-recovery/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "leakledger-ota-recovery": {
      "type": "http",
      "url": "https://botbridge.scanforlife.net/generated/leakledger-ota-recovery/mcp"
    }
  }
}

Tools

2

evaluate_exception

Evaluate one record for domain-specific exceptions and revenue/workflow risk.

Parametersrecord_jsonrequiredcontext_json

tool_catalog

Describe this product domain, tools, and input expectations.

Takes no parameters.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.