Hlido MCP vs Research Hub — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Hlido MCP vs Research Hub
In-depth architectural comparison of the Hlido MCP and Research Hub 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
Hlido MCP
Research · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Research Hub
Research · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Hlido MCP if you need specialized Research tools running via a local process. Choose Research Hub 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 Hlido MCP when:
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 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.
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.
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.
Category & Scope
Tools & Capabilities Breakdown
Hlido MCP Tools (9)
trust_check
"Is agent X trustworthy?" — score, tier, verdict for a slug
find_trusted
"Find me a trusted agent for <need>" — filtered registry search
verify_claim
"Does X really do Y?" — per-claim PASS/FAIL evidence
compare_agents
Side-by-side scorecard comparison
get_scorecard
Full sanitized scorecard JSON for a slug
find_similar_agents
Semantic nearest neighbours to a given agent
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).
Hlido MCP is categorized under Research and uses a local stdio subprocess. In contrast, Research Hub belongs to Research using local stdio subprocess. Select Hlido MCP when you need capabilities focused on research and Research Hub when you require tools for research.