Intact vs Chembl — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Intact vs Chembl
In-depth architectural comparison of the Intact and Chembl 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
Intact
Databases · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Chembl
Databases · Remote HTTP/SSE
Quality: 37/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Intact if you need specialized Databases tools running via a hosted cloud SSE transport. Choose Chembl if your workspace requires Databases integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
I
Choose Intact when:
You need dedicated capabilities in the Databases domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
IntAct (EBI) molecular-interaction database — find protein-protein and other molecular interactions for a gene/protein (by name or UniProt id), with detection method, interaction type, organism, PubMed ref, and MI confidence score. Keyless.
interaction_count
IntAct (EBI) — fast count of how many molecular interactions a gene/protein (by name or UniProt id) has. Keyless.
Chembl Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
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).
Intact is categorized under Databases and uses a remote streaming HTTP/SSE transport. In contrast, Chembl belongs to Databases using remote streaming HTTP/SSE transport. Select Intact when you need capabilities focused on databases and Chembl when you require tools for databases.