LEGION Verify: MCP tool-list history
Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs.
Connect it
Settings → Connectors → Add custom connector
URL: https://mcp.legion-api.com/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://mcp.legion-api.com/mcp{
"mcpServers": {
"legion-verify": {
"url": "https://mcp.legion-api.com/mcp"
}
}
}claude mcp add --transport http legion-verify https://mcp.legion-api.com/mcp{
"servers": {
"legion-verify": {
"type": "http",
"url": "https://mcp.legion-api.com/mcp"
}
}
}5 tools, pulled live
get_checkpointread-onlyLatest 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_yourself`).
get_server_changesread-onlySigned 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` checks offline. A change is not a fault; history = what LEGION observed, not what other clien
verify_evidence_bundleread-onlyVerify 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 (UNAPPROVED_CHANGE if not). Bundle = {record, proof, sth, keyring} as returned by get_server_
verify_mcp_serverread-onlyCheck 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-verified here from the pinned root key), an evidence bundle for `verify_evidence_bundle`, an
check_mcp_serverread-onlyOne-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 and a command that verifies everything offline. Read-only. Unknown id -> state UNKNOWN (a
Alternatives in Developer Tools
Compare →
Compiler ExplorerA
Compile code with thousands of compilers, inspect the assembly, and share godbolt.org links
MIMiroOfficialA
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
Context7A
Up-to-date docs for AI agents
OMOmnaraA
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
AAAirbyte AgentsOfficialA
Let AI agents query data and act across all your business apps via MCP.
ARApple RagA
Apple developer docs and WWDC transcripts with RAG retrieval and Jev relevance ranking.