--OFFICIAL REGISTRY HISTORY / PUBLIC METADATA / FREE
MCP Registry
Release Gate
Compare what changed between two published server.json versions before the next install, update or connection.
01Official Registry version history
02Endpoint, package and declaration drift
03Unsigned SHA-256 evidence receipt
04No package execution or security verdict
STEP 01 / LOAD PUBLIC HISTORY
Name the official Registry server.
Only the fixed official Registry host is queried. The name and selected versions are returned to this browser but are not written into H/M metrics.
STEP 02 / SELECT THE RELEASE EDGE
Choose a baseline and candidate.
0 published versions observed
STEP 03 / REVIEW THE OBSERVED CHANGE
Release evidence
--DETERMINISTIC CHANGE LEDGER
What moved between releases
--
No observable field changed between the selected Registry records.
EVIDENCE RECEIPT
Bind the review to its exact output.
The checksum covers the normalized release edge and change ledger. It is not a signature and does not authenticate H/M as an issuer.
--
COMMERCIAL NEXT STEP / PILOT
Turn one comparison into a release watch.
The free gate reviews one public release edge. The pilot brief scopes recurring checks, evidence history and change alerts without pretending monitoring is already active.
- 01Watch named Registry serversScheduled version checks
- 02Preserve review receiptsBounded evidence history
- 03Route material driftEmail or webhook scope
EVIDENCE BOUNDARY
A changed declaration is a review signal, not a verdict.
Official public Registry records, publication metadata and normalized field changes.
Artifact contents, package execution, runtime behavior, ownership re-verification or intent.
No safety score, maliciousness claim, certification, legal conclusion or cryptographic signature.
Official source: registry.modelcontextprotocol.io / Registry documentation