Validate a new-spec MCP server identity document — subject, issuer, serverInfo, and attestation reference at the well-known path (art-147) → validate OAuth 2.0 Protected Resource Metadata per RFC 9728: resource URI, authorization servers, scopes, and bearer methods (art-148) → validate the MCP Registry server.json entry: schema, reverse-DNS name, semver version, and endpoint (art-149). Full governance attestation with execution_hash. Zero network, zero PII.
validate_mcp_server_identity{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_mcp_server_identity",
"arguments": {
"identity": {
"subject": "did:web:example.com",
"issuer": "did:web:registry.mcp.io",
"serverInfo": { "name": "ExampleMCPServer", "version": "1.2.0" },
"attestation": { "ref": "https://registry.mcp.io/attestations/abc123" }
},
"well_known_path": "/.well-known/mcp-server-identity",
"signature_valid": true
}
},
"id": 1
}
validate_mcp_authorization_metadata{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "validate_mcp_authorization_metadata",
"arguments": {
"metadata": {
"resource": "https://api.example.com/mcp",
"authorization_servers": ["https://auth.example.com"],
"scopes_supported": ["tools:read", "tools:call"],
"bearer_methods_supported": ["header"]
}
}
},
"id": 2
}
check_mcp_registry_entry{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "check_mcp_registry_entry",
"arguments": {
"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" }]
}
}
},
"id": 3
}