protect-mcp-setup

You can add cryptographic governance to Claude Code by installing protect-mcp, configuring hooks in .claude/settings.json, and running a local signing server to enforce Cedar policies and generate Ed25519-signed receipts.

Offline verification of signed receipts uses Ed25519 cryptographic signatures to provide tamper-evident records of tool call decisions and inputs. This allows compliance audits to verify records without active network connections.

Yes, policy evaluation hooks intercept Claude Code tool calls to evaluate Cedar policies before execution. This security governance mechanism ensures only explicitly permitted tool usage proceeds in development pipelines.

The best way to create tamper-evident audit trails is using Ed25519-signed receipts for every tool call decision. This cryptographic approach satisfies compliance requirements across development pipelines by providing offline verifiable records.

Yes, you need to run a local signing server to produce Ed25519-signed receipts. This server integrates with your project environment to issue verifiable records for policy evaluation decisions and tool inputs.

You need cryptographic audit trails when operating in compliance contexts or development pipelines requiring strict accountability. Tamper-evident records ensure tool calls can be verified offline and trusted across teams.