protect-mcp

Q: How to install protect-mcp?

Open your MCP config: ~/.claude.json. Then add the config to "mcpServers": { "protect-mcp": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.

Q: What is protect-mcp best for?

protect-mcp is categorized under General. It covers: mcp, plugin, cedar, receipts, ed25519, policy, governance, audit.

35.8kCommunity RegistryGeneralby Tom Farley · MIT

Cedar policy enforcement + Ed25519 signed receipts for every Claude Code tool call. First cryptographic governance plugin â decisions are policy-gated before they run and every decision produces a tamper-evident receipt verifiable offline.

First seen 4/17/2026

Summary

This skill enforces Cedar policies on every Claude Code tool call and generates Ed25519-signed receipts for each decision.

It provides cryptographic governance for MCP plugins, ensuring that actions are policy-gated before execution and producing tamper-evident receipts that can be verified offline for auditability.

Install & Usage

Open your MCP config

~/.claude.json

Add the server config

Add the configuration to "mcpServers": { "protect-mcp": { "command": "...", "args": [] } }

Restart Claude Code

/mcp

Use Cases

Enforce access control policies on tool calls to prevent unauthorized operations in a multi-tenant Claude Code environment.

Generate signed receipts for every tool invocation to create an immutable audit trail for compliance with internal or regulatory standards.

Verify offline that a previous tool call was policy-approved and untampered using the Ed25519 signature on the receipt.

Integrate Cedar policy-as-code into Claude Code workflows to automate governance without manual approval steps.

Debug policy violations by inspecting the signed receipt to see which rule denied a specific tool call.

Enable zero-trust security for MCP plugins by requiring cryptographic proof of policy enforcement before trusting any output.

Usage Examples

/protect-mcp allow tool read_file if user == 'admin'

Check the receipt for the last tool call and verify its signature.

List all denied tool calls from today with their signed receipts.

View source on GitHub

mcpplugincedarreceiptsed25519policygovernanceaudit

Security Audits

LicensePassSourceWarnRepositoryPass

Frequently Asked Questions

What is protect-mcp?

This skill enforces Cedar policies on every Claude Code tool call and generates Ed25519-signed receipts for each decision. It provides cryptographic governance for MCP plugins, ensuring that actions are policy-gated before execution and producing tamper-evident receipts that can be verified offline for auditability.

How to install protect-mcp?

To install protect-mcp: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "protect-mcp": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.

What is protect-mcp best for?

protect-mcp is a mcp categorized under General. It is designed for: mcp, plugin, cedar, receipts, ed25519, policy, governance, audit. Created by Tom Farley.

What can I use protect-mcp for?

protect-mcp is useful for: Enforce access control policies on tool calls to prevent unauthorized operations in a multi-tenant Claude Code environment.; Generate signed receipts for every tool invocation to create an immutable audit trail for compliance with internal or regulatory standards.; Verify offline that a previous tool call was policy-approved and untampered using the Ed25519 signature on the receipt.; Integrate Cedar policy-as-code into Claude Code workflows to automate governance without manual approval steps.; Debug policy violations by inspecting the signed receipt to see which rule denied a specific tool call.; Enable zero-trust security for MCP plugins by requiring cryptographic proof of policy enforcement before trusting any output..