Orphograph vs Qeaas MCP
A side-by-side look at the Orphograph and Qeaas MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Orphograph for cryptography work as a local process; choose Qeaas MCP for cryptography. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Orphograph when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 40/100 · Fair | 32/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| 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 |
Tools & capabilities
Orphograph tools
No tool names declared yet. Check the project README from the listing page.
Qeaas MCP tools
No tool names declared yet. Check the project README from 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.
Orphograph
{
"mcpServers": {
"orphograph": {
"command": "uvx",
"args": [
"orphograph-mcp"
]
}
}
}
Qeaas MCP
No confirmed install command for Qeaas MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Orphograph is categorized under Cryptography and uses a local stdio subprocess. Qeaas MCP belongs to Cryptography and uses an install path we have not confirmed yet. Pick Orphograph for cryptography work and Qeaas MCP 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. Qeaas MCP has no confirmed install command yet — follow its own setup instructions.
Orphograph has no declared pricing — check the project's own site. Qeaas MCP 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 orphograph and qeaas-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Orphograph has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Qeaas MCP has 32/100 (Emerging) with 2 views, 0 installs and 2 GitHub stars.