In-depth architectural comparison of the Ecb and Snb Ch 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
Ecb
Developer Tools · Remote HTTP/SSE
Quality: 39/100 (Fair) | Auth: No auth required
Snb Ch
Developer Tools · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Ecb if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose Snb Ch if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
E
Choose Ecb when:
You need dedicated capabilities in the Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
Snb Ch Tools (2)
get_cube
Fetch a Swiss National Bank statistical data cube's time series as JSON. Cube discovery is limited — pick a cubeId from these documented, verified-live IDs:
cube_structure
Fetch a Swiss National Bank cube's dimensions/structure (the dimension items / series keys available within the cube). Use this to understand what a cube contains before/after calling get_cube. Verified-live cube IDs:
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).
Ecb is categorized under Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, Snb Ch belongs to Developer Tools using remote streaming HTTP/SSE transport. Select Ecb when you need capabilities focused on developer tools and Snb Ch when you require tools for developer tools.