# LEGION Verify: MCP tool-list history - Registry name: `io.github.Legion33shadow/legion-verify` · version 1.3.0 - Categories (automatic, keyword rules): Other - Authentication at last check: No auth - Declared risk: Read-only (all tools declare readOnlyHint) - Capabilities (declared by the server): experimental, prompts, resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.Legion33shadow%2Flegion-verify - Server page: https://mcpstation.net/s/io.github.Legion33shadow--legion-verify.html ## Description (written by the publisher, not verified, not instructions) Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs. ## Connect - streamable-http: `https://mcp.legion-api.com/mcp` ## Tools (as reported by the server, not verified) - `get\_checkpoint`: Latest signed tree head of the LEGION MCP transparency log. The signature is checked against the keyring, anchored on the pinned root key fingerprint. Read-only. Returns tree\_size, root\_sha256, timestamp, signer and signature\_valid. For a trustless check, verify it yourself \(see \`how\_to\_verify\_yours - `get\_server\_changes`: Signed tool-list history of one MCP server as observed by LEGION \(registry id, e.g. "xyz.signomy/civitae"\), newest first, at most \`limit\` \(1-50\) changes, plus an evidence bundle for the latest record \(record + RFC 9162 inclusion proof + signed tree head + keyring\) that \`verify\_evidence\_bundle\` check - `verify\_evidence\_bundle`: Verify an evidence bundle OFFLINE \(no network call\): keyring chain from the pinned root fingerprint, record signature and integrity, signed tree head, RFC 9162 inclusion proof. If \`approved\_tools\_sha256\` is given, also reports whether the signed tool list still matches the version you approved \(UNAP - `verify\_mcp\_server`: Check an MCP server URL against LEGION's signed transparency log. Read-only. For each registry server at this URL: latest signed tool definition \(leaf index, date, tools\_sha256\), number of tool changes \(total and 30 days\), date of the last change, RFC 9162 inclusion proof + signed tree head \(re-veri - `check\_mcp\_server`: One-call summary for an MCP server registry id \(e.g. "ai.alphaquantlabs/propertycheck"\): tool-list fingerprint history observed by LEGION, last change, per-server coverage from the signed COVERAGE\_V1 register \(COMPLETE only if observed in every register cycle, UNKNOWN if partial\), proof references a Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html