Keryx vs ResearchZosho — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Keryx vs ResearchZosho
In-depth architectural comparison of the Keryx and ResearchZosho MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Keryx
Research · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: No auth required
ResearchZosho
Research · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Keryx if you need specialized Research tools running via a hosted cloud SSE transport. Choose ResearchZosho if your workspace requires Research integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Keryx when:
You need dedicated capabilities in the Research domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Budgeted autonomous source selection, Buy, skip, and cache decisions, USDC x402 payments on Arc.
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: RESEARCHZOSHO_DRIVE, RESEARCHZOSHO_MODEL, RESEARCHZOSHO_JUDGE_DRIVE, RESEARCHZOSHO_JUDGE_MODEL, RESEARCHZOSHO_EMBED, RESEARCHZOSHO_LIBRARY.
Primary tools included: Web and scholarly literature search, PDF, web page, and folder ingestion, Claim-level citations and source quotes.
Keryx is categorized under Research and uses a remote streaming HTTP/SSE transport. In contrast, ResearchZosho belongs to Research using local stdio subprocess. Select Keryx when you need capabilities focused on research and ResearchZosho when you require tools for research.