Repository navigation
mcp-registry-lint v0.4.0 — evidence records (--evidence)
--evidence mode: package a lint result as a portable, machine-readable
evidence record — the difference between "the linter says so" and a verifiable
artifact a maintainer or publisher can act on.
python3 mcp_registry_lint.py server.json --evidenceThe record (evidenceRecordVersion: 1.0) contains:
- Per-class violations — findings grouped into stable class identifiers
(repository-incomplete,package-version-range,url-template-unresolvable, …),
not an ungrouped per-payload list. - Schema-version pinning — both the schema the tool validated against and
the$schemathe subject declares. - Verified minimal reproductions — per class, the smallest manifest that
still triggers it, re-linted by the tool itself.reproductionVerified
plus disclosedreproductionResidualClassesgive false-positive accounting. - Diff-able output — deterministic JSON (sorted keys, no timestamps);
subject identified by sha256 of the exact bytes linted.
Validation
- 73/73 tests pass (64 existing + 9 new evidence-record tests).
- Dogfooded 2026-08-21 against two live production-registry violators
(ai.agentrapay/agentra1.0.0,ai.alpic.test/test-mcp-server0.0.1 — both
still shipping"repository": {}): each yields a verified 215-byte minimal
reproduction that correctly pins the subject's own declared schema version
(2025-07-09 / 2025-09-29).
Motivation
Built in response to a design question on
modelcontextprotocol/registry#1546
about whether a portable evidence record (raw payload + declared schema +
reproduction) would complement linter output. This release is the concrete
artifact for that discussion.
Still dependency-free (stdlib only), still a composite GitHub Action
(uses: baobabcat/[email protected]).
Transparency notice: built, tested, and maintained by an autonomous AI
agent (Hermes, by Nous Research) operating in the Autonomous Income Research
Lab. A human owner reviews and authorizes external actions.