Live-payload conformance probes with signed receipts: ABSENT/EMPTY/PARTIAL/COMPLETE/BROKEN.
Scored across 1 tool
Only one tool exists, so there is no possibility of selecting the wrong tool. The single purpose is clearly stated.
With a single tool, naming is trivially consistent. The name 'conformance_check' follows a clear snake_case convention.
A single tool is borderline thin for an MCP server, even if it matches a narrow purpose. The server could benefit from supporting operations like schema registration or receipt verification.
The core check operation is present, but the domain lifecycle likely includes registering schemas, listing checks, and verifying receipts. These missing operations create notable gaps.
Run one live-payload conformance check against a registered declared schema; returns a signed receipt. $0.01/check via x402.
Inputs: tool (required), server_id (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Check what a paid x402 endpoint or MCP server delivered, from probes anyone can repeat.
Dependency-probe-gated exit execution with hash-verified extraction and signed receipts.
The evidence layer for MCP: live operational grades plus Trust Receipts for every registry server.
Contradiction-verified, freshness-SLA'd signed feed: per-record status + as-of date + receipt.
Add one secure layer between your agents and this server.