# LEGION Verify: MCP tool-list history (remote · mcp.legion-api.com)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.legion-api.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/legion33shadow-legion-verify/mcp.md), [page](https://verifymcp.io/servers/legion33shadow-legion-verify/mcp)

## Channel facts

- Endpoint: `https://mcp.legion-api.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 633 tokens (~126/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the LEGION Verify: MCP tool-list history server?

LEGION Verify: MCP tool-list history is a hosted endpoint at https://mcp.legion-api.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http legion33shadow-legion-verify 'https://mcp.legion-api.com/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.legion33shadow-legion-verify]
url = "https://mcp.legion-api.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "legion33shadow-legion-verify": {
      "type": "remote",
      "url": "https://mcp.legion-api.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add legion33shadow-legion-verify --url 'https://mcp.legion-api.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  legion33shadow-legion-verify:
    url: "https://mcp.legion-api.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "legion33shadow-legion-verify": {
      "Transport": "http",
      "Url": "https://mcp.legion-api.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add legion33shadow-legion-verify -t streamable-http -u 'https://mcp.legion-api.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-17 (score 63)

First indexed and scored.

## MCP tools (5)

### `get_checkpoint` (~78 tokens)

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` (~127 tokens)

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.

Input parameters:

- `limit` (integer)
- `server_id` (string, required)

### `verify_evidence_bundle` (~124 tokens)

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

Input parameters:

- `approved_tools_sha256` (string)
- `bundle` (object, required)

### `verify_mcp_server` (~174 tokens)

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.

Input parameters:

- `live` (boolean)
- `url` (string, required)

### `check_mcp_server` (~130 tokens)

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.

Input parameters:

- `server_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/legion33shadow-legion-verify/mcp#diagnostics

## Score history

- 2026-10-18: 64
- 2026-10-17: 63

## Common questions

### What is the LEGION Verify: MCP tool-list history server?

LEGION Verify: MCP tool-list history is listed in the public MCP registry as io.github.Legion33shadow/legion-verify. Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs. This page covers its hosted endpoint (https://mcp.legion-api.com/mcp).

### Is the LEGION Verify: MCP tool-list history server safe to use?

LEGION Verify: MCP tool-list history scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the LEGION Verify: MCP tool-list history server expose?

LEGION Verify: MCP tool-list history exposes 5 tools: get_checkpoint, get_server_changes, verify_evidence_bundle, verify_mcp_server, check_mcp_server. Their descriptions and schemas cost roughly 633 tokens of context every time the server is loaded.

### Does the LEGION Verify: MCP tool-list history server require authentication?

No. We connected to LEGION Verify: MCP tool-list history without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LEGION Verify: MCP tool-list history server still maintained?

LEGION Verify: MCP tool-list history is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.legion-api.com/mcp
- Repository: https://github.com/Legion33shadow/legion-mcp
- Website: https://legion-api.com/tlog/check/
- Changelog RSS feed: https://verifymcp.io/servers/legion33shadow-legion-verify/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/legion33shadow-legion-verify/mcp.json
- HTML version of this page: https://verifymcp.io/servers/legion33shadow-legion-verify/mcp