Server Everything vs Proof Layer
A side-by-side look at the Server Everything 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 Server Everything for other tools and integrations 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 Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
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 | Other Tools and Integrations | Cryptography |
| Quality signal | 55/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | PROOF_LAYER_API_KEYPROOF_LAYER_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 91,405 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Server Everything | View Proof Layer |
Tools & capabilities
Server Everything 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.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
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
Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Proof Layer belongs to Cryptography and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.
Server Everything is listed as free. Auth: no auth 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 modelcontextprotocol-server-everything and proof-layer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Server Everything has a quality signal of 55/100 (Good) with 9 views, 0 installs and 91,405 GitHub stars. Proof Layer has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.