# LEGION Verify: MCP tool-list history

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

- name: io.github.Legion33shadow/legion-verify
- version: 1.3.0
- connection class: R0 (autonomous)
- trust: 97/100
- quality: 94/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.Legion33shadow%2Flegion-verify
- tools: https://api.protogrid.dev/v1/servers/io.github.Legion33shadow%2Flegion-verify/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "legion-verify": {
      "type": "http",
      "url": "https://mcp.legion-api.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% +updated-3d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 94/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 925 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 2 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 5, about 925 tokens to load them all
- tool set hash: 766f818a435dfaffb37e8ee654ad248e
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.Legion33shadow/legion-verify.svg)](https://protogrid.dev/servers/io.github.Legion33shadow/legion-verify)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.legion-api.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (5)

- `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 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.
- `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_yourself`).
- `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` checks offline.
    A change is not a fault; history = what LEGION observed, not what other clients see.
- `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 (UNAPPROVED_CHANGE if not).
    Bundle = {record, proof, sth, keyring} as returned by get_server_changes (max 256 KB).
- `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-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.