Yade MCP vs Hlido MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Yade MCP vs Hlido MCP
In-depth architectural comparison of the Yade MCP 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
Yade MCP
Research · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Hlido MCP
Research · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Yade MCP 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 Yade 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).
MCP server for YADE — open-source discrete element method (DEM) engine for granular and particle simulation. Browse API docs with BM25 search, execute code via synchronous REPL or async background tasks, monitor progress, and review task history.
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
Yade MCP Tools (7)
yade_browse_api
Walk the YADE Python class tree
yade_query_api
BM25 keyword search across the API
yade_execute_code
Run Python in the live YADE process; returns synchronously
yade_execute_task
Submit a script as a long-running background task
yade_check_task_status
Inspect a running or finished task (output, status)
yade_interrupt_task
Gracefully stop a running task
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).
Yade MCP is categorized under Research and uses a local stdio subprocess. In contrast, Hlido MCP belongs to Research using local stdio subprocess. Select Yade MCP when you need capabilities focused on research and Hlido MCP when you require tools for research.