LEGION Verify: MCP tool-list history

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "LEGION Verify: MCP tool-list history": {
      "url": "https://mcp.legion-api.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• get_checkpoint read-only

  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_yourself`).

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_server_changes read-only

  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` checks offline. A change is not a fault; history = what LEGION observed, not what other clients see.

  Parameters:

  • server_id (required) — string
  • limit — integer

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• verify_evidence_bundle read-only

  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 (UNAPPROVED_CHANGE if not). Bundle = {record, proof, sth, keyring} as returned by get_server_changes (max 256 KB).

  Parameters:

  • bundle (required) — object
  • approved_tools_sha256 — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• verify_mcp_server read-only

  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-verified here from the pinned root key), an evidence bundle for `verify_evidence_bundle`, and — if live=true — whether the tool list served NOW differs from the signed one (live check by LEGION: initialize + tools/list only, public addresses only, NOT signed). A change is not a fault; history = what LEGION observed, not what other clients see.

  Parameters:

  • url (required) — string
  • live — boolean

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_mcp_server read-only

  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 and a command that verifies everything offline. Read-only. Unknown id -> state UNKNOWN (absence from the log is not a verdict). A change is not an attack; this log does not certify that a server is secure.

  Parameters:

  • server_id (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.