LEGION Verify: MCP tool-list history MCP Server

by legion33shadow Your server? Claim it

answering

LEGION Verify: MCP tool-list history is answering right now. Last checked 1 min ago. It exposes 5 tools. Last commit 17 Oct 2026.

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

Uptime history 9 days of history · worst day 99%

9 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

636 ms

Response time

average over 24h

Stars

last commit 17 Oct 2026

What the code does

We read the source, 5 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable legion_tlog_verify.py:695

    j = lambda n: json.load(open(os.path.join(d, n), encoding="utf-8"))

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add legion-verify --transport http https://mcp.legion-api.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.legion-api.com/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

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.

checkpoint

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

mcp

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.

server

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.legion-api.com/mcp	streamable-http	answering	294 ms	1 min ago

Alternatives to LEGION Verify: MCP tool-list history

same job, measured the same way

Nginx Proxy Manager

by baeck

MCP server for Nginx Proxy Manager with full API coverage (43 tools)

196 installs/wk local only

Agent Tested

by agenttested

Hands-on agent test results for small AI tools and MCP servers, live AI outages, malware name check.

8 tools answering

Yandex Tracker

by sdamarketing

MCP server for Yandex Tracker: full API v3 coverage (187 tools)

56 installs/wk local only

Companybetatel

by companybetatel

Phone verification: free keyless coverage/pricing discovery + 4-channel OTP send. 15 tools.

13 installs/wk local only

Coverctl

by klarlabs-studio

Go code coverage analysis tool with MCP server for AI-powered coverage workflows

local only

Coverctl

by felixgeelhaar

Go code coverage analysis tool with MCP server for AI-powered coverage workflows

local only

Test MCP

by riskprofiler

An MCP server that provides a hello tool

1 tools answering

Untappd

by darrenjrobinson

MCP server exposing Untappd API tools for AI agents — full v4 read API coverage

36 installs/wk local only

LEGION Verify: MCP tool-list history — questions

Answers built from our own checks of this server.

What can LEGION Verify: MCP tool-list history do?

It exposes 5 tools, read directly from the server on our last check. Among them: check_mcp_server, get_checkpoint, get_server_changes, verify_evidence_bundle, verify_mcp_server. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is LEGION Verify: MCP tool-list history working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 636 ms. The bar chart above shows every period we have measured.

How do I connect LEGION Verify: MCP tool-list history?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does LEGION Verify: MCP tool-list history need an API key?

No. LEGION Verify: MCP tool-list history completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is LEGION Verify: MCP tool-list history?

It answers our handshake in 636 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is LEGION Verify: MCP tool-list history open source?

The code is open source: it is published under the MIT licence, written in Python and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.legion-api.com, which runs on its operator's own terms.