Hashproof vs MCP Ecdsa
A side-by-side look at the Hashproof and MCP Ecdsa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hashproof for cryptography work as a local process; choose MCP Ecdsa 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 Hashproof when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
Choose MCP Ecdsa when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
generate_key, sign_data, sign_digest.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 44/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Hashproof tools
No tool names declared yet. Check the project README from the listing page.
MCP Ecdsa tools 11
generate_keyGenerate ECDSA key pairsign_dataSign data (with hashing)sign_digestSign pre-hashed digestverify_signatureVerify signature over dataverify_digest_signatureVerify signature over digestimport_private_keyImport from PEM/DER/base64import_public_keyImport from PEM/DER/base64export_private_keyExport to PEM/DER/base64/SSHexport_public_keyExport to PEM/DER/base64/SSHget_key_infoGet key informationrecover_public_keyRecover public keys from signature
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.
Hashproof
{
"mcpServers": {
"hashproof": {
"command": "npx",
"args": [
"-y",
"hashproof-mcp"
]
}
}
}
MCP Ecdsa
{
"mcpServers": {
"mcp-ecdsa": {
"command": "uvx",
"args": [
"mcp-ecdsa"
]
}
}
}
Frequently asked questions
Hashproof is categorized under Cryptography and uses a local stdio subprocess. MCP Ecdsa belongs to Cryptography and uses a local stdio subprocess. Pick Hashproof for cryptography work and MCP Ecdsa 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.
Hashproof has no declared pricing — check the project's own site. MCP Ecdsa 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 hashproof and mcp-ecdsa as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hashproof has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. MCP Ecdsa has 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.