Crypto vs MCP Cryptography
A side-by-side look at the Crypto and MCP Cryptography MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Crypto for cryptography work; choose MCP Cryptography 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 MCP Cryptography when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
generate_symmetric_key, generate_rsa_key, generate_x25519_key.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 27/100 · Emerging | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 14 |
| Full listing | View Crypto | View MCP Cryptography |
Tools & capabilities
Crypto tools
No tool names declared yet. Check the project README from the listing page.
MCP Cryptography tools 14
generate_symmetric_keyGenerate a Fernet symmetric keygenerate_rsa_keyGenerate an RSA key pairgenerate_x25519_keyGenerate an X25519 key pairhash_sha256SHA-256 hashhash_sha512SHA-512 hashhash_sha1SHA-1 hashhmac_signGenerate HMAChmac_verifyVerify HMACpbkdf2_derivePBKDF2 key derivationscrypt_deriveScrypt key derivationgenerate_self_signed_certGenerate self-signed certificateparse_certificateParse X.509 certificate- +2 more on the listing page
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.
Crypto
No confirmed install command for Crypto yet — follow the setup steps linked from its listing page rather than a guessed package name.
MCP Cryptography
{
"mcpServers": {
"mcp-cryptography": {
"command": "uvx",
"args": [
"mcp-cryptography"
]
}
}
}
Frequently asked questions
Crypto is categorized under Cryptography and uses an install path we have not confirmed yet. MCP Cryptography belongs to Cryptography and uses a local stdio subprocess. Pick Crypto for cryptography work and MCP Cryptography 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. Crypto has no confirmed install command yet — follow its own setup instructions.
Crypto has no declared pricing — check the project's own site. MCP Cryptography 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 crypto-2 and mcp-cryptography as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Crypto has a quality signal of 27/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. MCP Cryptography has 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.