Research Hub vs Hlido MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Research Hub vs Hlido MCP
In-depth architectural comparison of the Research Hub and Hlido MCP 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
Research Hub
Research · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Hlido MCP
Research · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Research Hub if you need specialized Research tools running via a local process. Choose Hlido MCP 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 Research Hub when:
You need dedicated capabilities in the Research domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: ZOTERO_API_KEY, ZOTERO_USER_ID, NOTEBOOKLM_API_KEY, GOOGLE_API_KEY, GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET.
Primary tools included: Unified search across arXiv, Semantic Scholar, PubMed, and CrossRef, Integration with Zotero for reference management, Obsidian note syncing and dashboard visualization.
Research workspace MCP integrating Zotero, Obsidian, and NotebookLM. Search papers (arXiv/Semantic Scholar/PubMed/CrossRef), ingest into Zotero, sync notes to Obsidian, verify NotebookLM briefs. All three external tools optional. pip install research-hub-pipeline then research-hub serve.
Independent trust scores, claim audits, and comparisons for AI agents — queryable by your agent over MCP. Hosted Cloudflare Worker at hlido.eu/mcp (no install). Returns a 0–100 score, tier verdict, per-claim PASS/FAIL audit, and signed evidence for a reviewed agent. From Hlido.
Category & Scope
Tools & Capabilities Breakdown
Research Hub Tools (6)
Unified search across arXiv, Semantic Scholar, PubMed, and CrossRef
Integration with Zotero for reference management
Obsidian note syncing and dashboard visualization
NotebookLM brief verification
Local-first vault management with structured memory
Live dashboard with actionable controls
Hlido MCP Tools (9)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Research Hub is categorized under Research and uses a local stdio subprocess. In contrast, Hlido MCP belongs to Research using local stdio subprocess. Select Research Hub when you need capabilities focused on research and Hlido MCP when you require tools for research.