Catalog vs Monobank — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Catalog vs Monobank
In-depth architectural comparison of the Catalog and Monobank 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
Catalog
Finance & Fintech · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: No auth required
Monobank
Finance & Fintech · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Catalog if you need specialized Finance & Fintech tools running via a hosted cloud SSE transport. Choose Monobank if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Catalog when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
All MFOs with borrower rating, quick terms and canonical card URLs, ordered by rating position.
get_mfo
Full MFO card: terms for new/repeat clients (amount, term, rate, full cost of credit), borrower requirements, fees, legal entity, OGRN, Bank of Russia registry number, 4-criteria rating, record update date. Empty fields are omitted.
Catalog is categorized under Finance & Fintech and uses a remote streaming HTTP/SSE transport. In contrast, Monobank belongs to Finance & Fintech using local stdio subprocess. Select Catalog when you need capabilities focused on finance & fintech and Monobank when you require tools for finance & fintech.
Latest borrower reviews for an MFO: rating, date, text.
get_market_rules
Legal context of microlending in Russia (0.8%/day rate cap under Art. 6.1 of Law 353-FZ, 100% total-cost cap since 2026-04-01, self-ban via Gosuslugi, cooling-off periods, debt collection rules under Law 230-FZ) with last-review date.
Monobank Tools (3)
get_currency_rates
Get the list of currency exchange rates from Monobank. This is a public endpoint and does not require an API token. Monobank permits only one request per 5 minutes, so the response is cached in memory for 5 minutes: calls made within that window return the cached rates instead of failing with a rate-limit error.
get_client_info
Get information about the client together with the list of their accounts and jars. Requires the MONOBANK_API_TOKEN environment variable. Monobank permits only one request per 60 seconds, so the response is cached in memory for 60 seconds: calls made within that window return the cached data instead of failing with a rate-limit error. All monetary amounts are returned in currency units, not in cents. The account and jar identifiers returned by this tool can be passed to get_statement.
get_statement
Get the Monobank statement for an account or jar between the {from} and {to} dates. Requires the MONOBANK_API_TOKEN environment variable. The maximum period for which a statement can be obtained is 31 days + 1 hour (2682000 seconds). Monobank permits only one request per 60 seconds, so every distinct account/date-range request is cached in memory for 60 seconds: repeating the same request within that window returns the cached statement instead of failing with a rate-limit error. All monetary amounts are returned in currency units, not in cents.