AI + AUTOMATION INTERFACES

Let agents find recoverable reserves—without giving them custody.

The MCP server, CLI, and HTTP API accept public addresses only. They can inspect chain state and explain candidates; they cannot create, sign, or broadcast transactions.

Remote MCP

Five read-only tools over Streamable HTTP for AI clients.

Installable CLI

Scriptable JSON output plus an interactive terminal mode.

OpenAPI 3.1

Stable HTTP contracts for product facts and public-address scans.

Connect an AI client

The canonical production endpoint is live at https://recoversolrent.com/mcp. Client configuration shapes vary; the values below are the portable parts.

{
  "mcpServers": {
    "claimsol": {
      "type": "streamable-http",
      "url": "https://recoversolrent.com/mcp"
    }
  }
}

Tools: claimsol.scan_solana, claimsol.scan_reserves, claimsol.get_pricing, claimsol.get_supported_chains, and claimsol.get_methodology.

Automate public scans

The repository-local package has passed its installed-command production test suite. Public package-registry publication remains pending an owner-controlled account.

python -m pip install ./agent-harness
cli-anything-claimsol status --json
cli-anything-claimsol pricing --json
cli-anything-claimsol chains --json
cli-anything-claimsol scan solana <PUBLIC_WALLET> --json

https://recoversolrent.com is the default backend. Set CLAIMSOL_BASE_URL or pass --base-url only to target another deployment.

A deliberate read-only boundary

Agent calls are logged only as aggregate interface events. No exact referring URL, user agent, IP address, wallet, prompt, seed phrase, private key, or transaction signature is stored in discovery analytics. Any future write-capable MCP tool must ship behind authentication and explicit human confirmation; none is included here.