Validates a MCP Registry server.json entry: $schema URI, reverse-DNS name/slug, semver version, and at least one package or remote endpoint. Terminal node of the mcp-server-governance-conformance chain.
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `check_mcp_registry_entry`. Task: Validate a MCP Registry server.json entry: $schema URI, reverse-DNS name, semver version, and at least one package or remote endpoint.
Call it with arguments: {"policy_parameters":{"entry":{"$schema":"https://registry.mcp.io/schema/server.json","name":"com.example/my-mcp-server","version":"1.0.0","packages":[{"registry":"npm","name":"@example/mcp-server","version":"1.0.0"}]}}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-149-mcp-registry-entry-conformance.html#p=v1.H4sIAAAAAAAA_wHGADn_eyJlbnRyeSI6eyIkc2NoZW1hIjoiaHR0cHM6Ly9yZWdpc3RyeS5tY3AuaW8vc2NoZW1hL3NlcnZlci5qc29uIiwibmFtZSI6ImNvbS5leGFtcGxlL215LW1jcC1zZXJ2ZXIiLCJ2ZXJzaW9uIjoiMS4wLjAiLCJwYWNrYWdlcyI6W3sicmVnaXN0cnkiOiJucG0iLCJuYW1lIjoiQGV4YW1wbGUvbWNwLXNlcnZlciIsInZlcnNpb24iOiIxLjAuMCJ9XX19k-LNcsYAAAA