MCP Server Attestation · ApexLogics Showcase SC-60

Paste a server's advertised tool surface twice, once as the baseline and once as a later check, one line per tool in the shape name colon description. This tool fingerprints each paste, compares them line by line, and flags whether the surface matches what you were originally told to expect. A tool description that changes after you have already reviewed and trusted it is a live path for an agent to be redirected, and a structural comparison catches that drift even when the change is small.

Data: Model Context Protocol specification · illustrative demo, no external data

Tool Surfaces STEP 1

Surface A (baseline) One line per tool, as: tool_name: description

Surface B (later check) Paste the same surface again to confirm nothing moved

Declared Tool Count How many tools the server operator told you to expect

Surface Status

—

Unchanged, count mismatch, drift, or empty

Tools in Surface A

—

Non-empty lines pasted as the baseline

Changed Lines

—

Positions that differ between the two pastes

Detail

Tool count A—

Tool count B—

Declared tool count—

Surface A digest (mutation detector, not a cryptographic digest)—

Surface B digest (mutation detector, not a cryptographic digest)—

Surface match—

Count matches declared—

Changed line count—

Status—

Policy Mandate v2.0 · what is this?

Exhibit: a worked example that computes in your browser. It is not regulatory-grade output. Source card on AINumbers: industry card c10-3.

MCP ServerAttestation

MCP Server
Attestation