PEAC Protocol vs Witnessd
A side-by-side look at the PEAC Protocol and Witnessd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PEAC Protocol for cryptography work over a hosted endpoint; choose Witnessd 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 PEAC Protocol when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a remote HTTP/SSE transport.
Choose Witnessd when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EVM_PRIVATE_KEY, WITNESSD_API_KEY, WITNESSD_URL. - You want tools like
witness_url, get_certificate, retrieve_snapshot.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 43/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | EVM_PRIVATE_KEYWITNESSD_API_KEYWITNESSD_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View PEAC Protocol | View Witnessd |
Tools & capabilities
PEAC Protocol tools
No tool names declared yet. Check the project README from the listing page.
Witnessd tools 3
witness_urlIndependent fetch + hash + timestamp + archive of a URL right now; returns snapshot id + signed certificateget_certificateCertificate for any snapshot id: manifest, Ed25519 signature, Merkle proof, Base anchor transactionretrieve_snapshotThe archived response body + certificate — works for any snapshot id, any payer (this is how third parties obtain evidence)
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.
PEAC Protocol
{
"mcpServers": {
"peac-protocol": {
"url": "https://api.example.com"
}
}
}
Witnessd
{
"mcpServers": {
"witnessd": {
"command": "npx",
"args": [
"-y",
"witnessd-mcp"
],
"env": {
"EVM_PRIVATE_KEY": "YOUR_EVM_PRIVATE_KEY_HERE",
"WITNESSD_API_KEY": "YOUR_WITNESSD_API_KEY_HERE",
"WITNESSD_URL": "YOUR_WITNESSD_URL_HERE"
}
}
}
}
Frequently asked questions
PEAC Protocol is categorized under Cryptography and uses a remote HTTP/SSE transport. Witnessd belongs to Cryptography and uses a local stdio subprocess. Pick PEAC Protocol for cryptography work and Witnessd 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.
PEAC Protocol has no declared pricing — check the project's own site. Witnessd 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 peac-protocol and witnessd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PEAC Protocol has a quality signal of 43/100 (Fair) with 2 views, 0 installs and 14 GitHub stars. Witnessd has 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars.