In-depth architectural comparison of the Hlido MCP and Science AI MCP Server 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
Science AI MCP Server
Research · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Hlido MCP if you need specialized Research tools running via a local process. Choose Science AI MCP Server 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).
Hlido MCP is categorized under Research and uses a local stdio subprocess. In contrast, Science AI MCP Server belongs to Research using local stdio subprocess. Select Hlido MCP when you need capabilities focused on research and Science AI MCP Server when you require tools for research.
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.
Academic peer-review and research workflow tools from Science AI Journal: Pre-Check (paper-tier prediction), AI multi-agent peer review, Research Gaps Finder, Journal Recommender (1,214 venues with predatory-journal flags), Duplicate Publication Checker (CrossRef/arXiv/medRxiv/bioRxiv/Unpaywall/900k-paper library), and the Article Writer pipeline. Free local tools (FTS5, zero LLM cost); LLM tools use caller account credits.