Magic MCP vs Proof Layer
A side-by-side look at the Magic MCP and Proof Layer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Magic MCP for architecture & design work as a local process; choose Proof Layer for cryptography as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Magic MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
Choose Proof Layer when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROOF_LAYER_API_KEY, PROOF_LAYER_API_URL. - You want tools like
pl_evaluate, pl_get_receipt, pl_verify_receipt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Cryptography |
| Quality signal | 53/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST | PROOF_LAYER_API_KEYPROOF_LAYER_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6,138 | 0 |
| Directory activity | 16 views 1 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Magic MCP | View Proof Layer |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
Proof Layer tools 8
pl_evaluateSubmit an AI agent action proposal to Proof Layer for governance evaluation. Returns a cryptographically-signed receipt with a verdict of EXECUTE, BLOCK, REVIEW, or SHADOW. Use this before any consequential agent action (sending emails, modifying data, making payments, etc.).pl_get_receiptRetrieve a Proof Layer audit receipt by its UUID. Returns the full receipt including verdict, signature, and policy pack hash.pl_verify_receiptCryptographically verify a Proof Layer receipt. Checks the Ed25519 signature and confirms the signing key is ACTIVE. Returns valid: true/false with a reason.pl_list_receiptsList recent Proof Layer audit receipts for the authenticated tenant. Supports filtering by agent and verdict.pl_usageGet current Proof Layer quota usage — receipts used, receipts remaining, credit balance, billing cycle dates, and plan tier.pl_list_policy_packsList all governance policy packs for the authenticated tenant, including which one is currently active.pl_create_planA human approves a governed plan — a scoped, time-bounded set of future actions across named agents. Returns a plan_id and JTI that agents use to request delegation receipts via pl_delegate. Scope patterns support wildcards: 'build:*' authorizes any action starting with 'build:'.pl_delegateAn agent requests authorization to perform a specific action under a parent plan. Returns 'ok' with a signed receipt (proceed with the action), 'checkpoint_required' (human must re-approve this specific action), or 'denied' (agent or action not authorized under the plan).
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
Proof Layer
{
"mcpServers": {
"proof-layer": {
"command": "npx",
"args": [
"-y",
"@proof-layer/mcp@latest"
],
"env": {
"PROOF_LAYER_API_KEY": "YOUR_PROOF_LAYER_API_KEY_HERE",
"PROOF_LAYER_API_URL": "YOUR_PROOF_LAYER_API_URL_HERE"
}
}
}
}
Frequently asked questions
Magic MCP is categorized under Architecture & Design and uses a local stdio subprocess. Proof Layer belongs to Cryptography and uses a local stdio subprocess. Pick Magic MCP for architecture & design work and Proof Layer for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Magic MCP is listed as a paid service. Auth: api key required. Proof Layer has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add 21st-dev-magic-mcp and proof-layer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic MCP has a quality signal of 53/100 (Good) with 16 views, 1 installs and 6,138 GitHub stars. Proof Layer has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.