In-depth architectural comparison of the Cnb and Horus Flow 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
Cnb
Finance & Fintech · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Horus Flow MCP
Finance & Fintech · Remote HTTP/SSE
Quality: 41/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Cnb if you need specialized Finance & Fintech tools running via a local process. Choose Horus Flow MCP if your workspace requires Finance & Fintech integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cnb when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Fetches full daily ČNB FX sheets, Retrieves individual currency rates, Converts currencies through CZK.
Czech National Bank (ČNB) daily FX rates: fetch official CZK exchange rates, convert between currencies, fetch historical rates. Cached 10 min to ease upstream load. npm @czagents/cnb or HTTP at cnb.cz-agents.dev/mcp.
Institutional-grade crypto and US equity orderflow engine for real-time liquidity analysis and institutional alpha.
Cnb is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Horus Flow MCP belongs to Finance & Fintech using remote streaming HTTP/SSE transport. Select Cnb when you need capabilities focused on finance & fintech and Horus Flow MCP when you require tools for finance & fintech.