
Rubric Protocol
Generate AI compliance attestations aligned to EU AI Act, SR 11-7, and HIPAA before or after you ship agent features.
Overview
rubric-protocol is a MCP server for the Ship phase that produces AI compliance attestations for frameworks including EU AI Act, SR 11-7, and HIPAA.
What is this MCP server?
- Attestation tooling for EU AI Act, SR 11-7, and HIPAA framed for AI systems
- Free local tier with post-quantum-signed attestation and no API key required
- Optional RUBRIC_API_KEY enables Hedera mainnet anchoring for stronger provenance
- npm @rubric-protocol/mcp-server v2.0.2 over stdio MCP transport
- Lets agents produce compliance artifacts without a separate compliance portal UI
- npm package @rubric-protocol/mcp-server version 2.0.2
- Stdio transport; RUBRIC_API_KEY documented as optional secret
- Free local tier explicitly requires no API key per server description
What problem does it solve?
Shipping AI features without structured attestations leaves you scrambling to prove compliance when customers, auditors, or regulators ask.
Who is it for?
Builders shipping AI agents or automations who need documented attestation aligned to named regulatory frameworks and want a no-key local tier to start.
Skip if: Teams that need a full legal review substitute, non-AI products with no compliance scope, or builders unwilling to interpret regulatory requirements with counsel.
What do I get? / Deliverables
After connecting the MCP server, you can generate locally signed—or optionally Hedera-anchored—compliance attestations from agent-driven review workflows.
- Compliance-oriented attestation outputs from agent sessions
- Local PQ-signed attestations without API key on the free tier
- Optional mainnet-anchored attestations when RUBRIC_API_KEY is configured
Recommended MCP Servers
Journey fit
How it compares
Compliance attestation MCP, not a penetration-testing skill or general-purpose policy generator without regulatory framing.
Common Questions / FAQ
Who is rubric-protocol for?
Indie and small-team AI builders who must show structured compliance evidence for EU AI Act, SR 11-7, or HIPAA contexts and want MCP-native attestation.
When should I use rubric-protocol?
During ship security and launch prep when you document controls, generate attestations, or iterate compliance artifacts before customers or auditors review your AI system.
How do I add rubric-protocol to my agent?
Add stdio server @rubric-protocol/mcp-server to MCP config; run without RUBRIC_API_KEY for local PQ-signed attestations or set the key for Hedera mainnet anchoring.