About rubric-protocol
rubric-protocol is an MCP server for producing and checking AI compliance attestations, intended for teams working with regulatory evidence. It signs decisions, chains records, and anchors them to Hedera, with tools spanning verification, reporting, governance, and regulatory workflows.
Key features
- 01Attest and verify AI decisions
- 02Create signed, chained evidence anchored to Hedera
- 03Generate compliance reports and filings
- 04Check regulatory frameworks and jurisdiction gaps
- 05Manage incidents and human review
Use cases
- 01Record evidence for AI decisions
- 02Verify attestation chains and proofs
- 03Prepare regulatory compliance reports
- 04Track incidents requiring human review
MCP support
The server exposes attestation, verification, compliance, regulatory, governance, registry, and operations tools to MCP-compatible hosts. The default profile provides core tools; additional modules can be selected through an environment variable.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @rubric-protocol/mcp-serverRUBRIC_API_KEYSecretRubric API key for Hedera mainnet anchoring. Optional — omit for free local PQ-signed attestation.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMERubric Protocol MCP Server
AI compliance attestation for Claude Desktop, Cursor, Windsurf, and any MCP-compatible host.
Every AI decision PQ-signed, Merkle-chained, and anchored to Hedera mainnet. Built for EU AI Act Article 12, SR 11-7, HIPAA, and NIST AI RMF.
Quickstart
Add to your claude_desktop_config.json:
{
"mcpServers": {
"rubric": {
"command": "npx",
"args": ["-y", "@rubric-protocol/mcp-server@latest"],
"env": {
"RUBRIC_API_KEY": "your-key-here"
}
}
}
}
Free local tier, no key required:
{
"mcpServers": {
"rubric": {
"command": "npx",
"args": ["-y", "@rubric-protocol/mcp-server@latest"]
}
}
}
Restart Claude Desktop. Rubric tools appear automatically.
Tools
47 tools across 8 modules. Default profile exposes the core 8; set RUBRIC_MCP_MODULES=all (or a comma list, e.g. core,compliance) for more.
core (default): attest, verify, get_proof, register_agent, status, framework_detect, cost_estimate, bundle_query attestation: attest_batch, attestation_status, attestation_get, pipeline_trace, bundle_get verification: verify_chain, verify_tree, verify_batch, zk_verify, zk_proof_get, ledger_lookup compliance: annex4_generate, annex4_status, c2pa_attest, c2pa_assertion, credential_issue, credential_get, compliance_query, compliance_report, filing_generate regulatory: gpai_register, gpai_downstream, nist_rmf_certify, nist_rmf_status, jurisdiction_map, jurisdiction_assess, jurisdiction_gap governance: incident_create, incident_attest, incident_resolve, human_review, adversarial_session_start, adversarial_session_conclude registry: agent_add, agent_get, model_register, model_get ops: usage_report, auditor_token_create
The only MCP tools whose outputs are ML-DSA-65 (FIPS 204) signed, Hedera-anchored, and exportable as EU AI Act Annex IV, OSCAL, C2PA, and W3C Verifiable Credential evidence.
Get a Free API Key
Run register_agent directly inside Claude Desktop, no browser required. Or visit https://rubric-protocol.com
Regulatory Coverage
EU AI Act | SR 11-7 | NIST AI RMF | HIPAA | NYC Local Law 144 | ECOA Reg B
Links
https://rubric-protocol.com https://www.npmjs.com/package/@rubric-protocol/mcp-server https://registry.modelcontextprotocol.io
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.