banking-intelligence

warnings

mcp.ohmyfin.ai

Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.

https://mcp.ohmyfin.ai/mcpWebsiteNo authMCP 2025-11-25v3.1.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 669 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 34 tools listable
Credentials demanded in prose	✕country_banking_rules, settlement_eta, mcp_register, track_payment, tracking_history, ssi_lookup, banks_using_correspondent, company_search_person, company_search_company, company_registries These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

10 of the 34 tools listed anonymously say in their own descriptions that they need an account or a key (country_banking_rules, settlement_eta, mcp_register, track_payment, tracking_history, ssi_lookup, banks_using_correspondent, company_search_person, company_search_company, company_registries), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

bank_holidaysbanks_using_correspondentcompany_registriescompany_search_companycompany_search_personcompany_search_resultcountry_banking_rulescountry_export_controlscountry_payment_codeseccn_lookupexport_controls_screenfederal_register_changesfx_ratefx_rate_historyfx_timing_advisorfx_volatilitygoods_classifygpi_status_codeshs_code_lookupiban_validateis_business_day_checkmcp_registermcp_verifypayment_cutoff_timespayment_method_comparesanctions_screensettlement_etassi_lookupswift_lookupswift_message_referencetrack_paymenttracking_historytransfer_costvalue_date

Contract history

24 Aug 2026v3.1.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/banking-intelligence/badge.svg)](https://mcpi.app/servers/banking-intelligence)