Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.
| Endpoint | https://mcp.ohmyfin.ai/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 34 tools · grade F (0) · pin ts_02a4e86ba1deaf8de387b8ed6422ba65 · protocol 2025-06-18 |
| First / last listed | 2026-10-26 01:03 UTC / 2026-10-26 01:03 UTC |
| Grade over time | 2026-10-26: F (0), 34 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: swift_lookup iban_validate country_banking_rules country_payment_codes fx_rate fx_rate_history gpi_status_codes swift_message_reference payment_cutoff_times fx_volatility fx_timing_advisor payment_method_compare bank_holidays is_business_day_check value_date settlement_eta transfer_cost mcp_register mcp_verify sanctions_screen eccn_lookup country_export_controls export_controls_screen hs_code_lookup goods_classify federal_register_changes track_payment tracking_history ssi_lookup banks_using_correspondent company_search_person company_search_company company_search_result company_registries
swift_lookup | Search banks and financial institutions by name, SWIFT/BIC code, or country.
Covers both SWIFT-connected banks and non-SWIFT financial institutions
(e-money issuers, payment processors, MFOs, brokerages, VASPs, etc.).
Returns: SWIFT/BIC code (if any), name, city, country, institution type,
GPI membership, a coarse sanctions FLAG across 7 hard-sanctions watchlists
(OFAC SDN, EU, UK, CA, CH, AU, N params: query*, country, limit |
iban_validate | Validate an IBAN and identify the institution that holds the account.
Performs format check, country-specific length check, and
ISO 7064 mod-97 checksum verification. Also returns COUNTRY-level
banking rules for the IBAN's country prefix (national currency,
SEPA status, expected format).
CROSS-CHECKS THE BENEFICIARY BANK. Where the country's IBAN registry
mask defines the bank identifier as four params: iban* |
country_banking_rules | Get banking rules and requirements for a country.
Returns IBAN requirements, SEPA membership, FATF listing status,
national currency, account format specifications, and country-specific
payment requirements (mandatory codes like KNP for Kazakhstan,
Purpose of Payment for UAE, etc.).
The `fatf_listing` block is the authoritative answer to "is this country
grey-listed / black-listed / under FATF i params: country_code* |
country_payment_codes | Look up country-specific payment codes (KNP, purpose codes, etc.).
Use country_banking_rules first to see which code types a country
requires (in the payment_requirements block), then use this tool
to find the right code value.
Examples:
country_payment_codes("KZ", "knp", "transport")
country_payment_codes("KZ", "knp", "insurance")
country_payment_codes("AE", "purpose_code", "trade")
cou params: country_code*, code_type*, search |
fx_rate | Get the latest available reference (mid-market) exchange rate for a pair.
Rates are the official ECB euro foreign-exchange reference rates where the
ECB publishes the currency; pairs whose currency the ECB does not cover
(e.g. VND, NGN, PKR, KZT, MAD) fall back to a market data feed. ALWAYS
check the `source` field before describing provenance: "ecb" = official
ECB reference rate; "market" = indi params: base*, target* |
fx_rate_history | Get the historical reference exchange-rate series for a currency pair.
Returns `series` (the daily rates) plus the metadata needed to describe it
honestly. READ `series_coverage` BEFORE CHARACTERISING THE PERIOD. `days`
is the window we look back over, NOT a promise of how much history exists:
our series start at different dates per currency, so a 365-day request
routinely returns five months. `s params: base*, target*, days |
gpi_status_codes | Explain SWIFT GPI tracking status codes and provide stuck-payment investigation guidance.
USE THIS TOOL FIRST whenever the user reports a payment that is stuck,
delayed, not arriving, held, pending, rejected, or otherwise not
behaving as expected. It is the primary diagnostic entrypoint for
payment investigation — calling with a specific code returns a
full investigation playbook (common delay ca params: code |
swift_message_reference | Look up SWIFT message types — MT (FIN) and MX (ISO 20022).
Pass a specific type to get full details, or omit to list all types.
Covers customer payments (MT103, pacs.008), FI transfers (MT202,
pacs.009), trade finance (MT700, MT760), cash management (MT940,
camt.053), and payment status (pacs.002).
Also use this tool to answer questions about where specific payment
fields live — e.g., where the params: message_type |
payment_cutoff_times | Get payment system cutoff times for major clearing systems.
Covers RTGS (T2 — formerly TARGET2, CHAPS, Fedwire, BOJ-NET, SIC),
net settlement (CHIPS, BACS), SEPA schemes (SCT, SCT Inst, OCT Inst,
SDD Core, SDD B2B), FX settlement (CLS, FXYCS), and other systems
(CIPS, SPEI, FAST).
For same-day EUR guidance: filter by currency="EUR" to retrieve all
SEPA schemes plus T2 in one call — the scheme-le params: system, currency |
fx_volatility | Get realized FX volatility for a currency pair, and size the FX risk on an exposure held to a future date.
Computes 30-day and 90-day annualized volatility from historical
ECB reference rates (standard deviation of daily log returns,
annualized by sqrt(252)). Returns a qualitative bucket:
LOW (<5%), MEDIUM (5-15%), HIGH (15-25%), VERY_HIGH (>25%),
PEGGED (currency peg — near-zero volatility, e.g. params: base*, target*, horizon_days |
fx_timing_advisor | Get FX trading windows for FX execution timing and spread / rate optimization.
Returns market sessions and liquidity windows for a currency. Use this
to understand:
- **Rate optimization** (primary, reliable use): higher liquidity means
tighter spreads and better rates. Execute during peak windows to minimize
conversion costs.
- **Delay diagnosis** (use with care): the FX market session is wh params: currency |
payment_method_compare | Compare payment methods and investigate fee deductions for a country pair.
Evaluates SEPA vs SWIFT vs domestic options. Also explains SWIFT charge
options (OUR/SHA/BEN) and fee investigation — use this when the beneficiary
received less than expected to understand where the money went and which
MT103 fields reveal each deduction. Returns cost, speed, requirements,
charge options, and step-by-step params: source_country*, dest_country* |
bank_holidays | Get bank/public holidays for a country with payment impact analysis.
Returns all public holidays plus a 'payment_impact' section that shows:
- Whether today is a business day or holiday in this country
- Upcoming holidays in the next 14 days
- Recent holidays in the last 14 days — for diagnosing a payment that is
ALREADY stuck ("in progress for N days", "sent X days ago"). A recent
holiday on params: country_code*, year |
is_business_day_check | Check if a specific date is a business day in a country.
Accounts for weekends (country-specific) and public holidays.
Returns whether the date is a business day, and if not, why
(weekend or specific holiday name) and the next business day.
The response carries a `today` block with the server's real current date.
Resolve any relative date in the user's question ("the 20th", "next
Friday") agains params: country_code*, check_date* |
value_date | Calculate the value/settlement date for a payment.
Determines when a payment will settle based on:
- Source and destination country holiday calendars
- Weekend conventions (Sat/Sun or Fri/Sat)
- Currency center holidays (if FX conversion involved)
- Settlement convention (T+0, T+1, T+2)
Examples:
value_date("US", "DE")
value_date("US", "DE", "fx_spot", "USD", "EUR")
value_date("DE", "FR", params: source_country*, dest_country*, settlement_type, base_currency, target_currency, from_date |
settlement_eta | BETA. Estimate when a SWIFT payment will arrive: a corpus-grounded
arrival window with an honest tail, computed from real completed payments
we have tracked, projected onto the currency's banking calendar.
This estimator is in BETA and still calibrating. Say so when you present a
number: call it an estimate or a typical window, never a commitment, and
never let a user plan an irreversible decisio params: uetr, currency, sender_bic, receiver_bic, intermediary_bic, current_status, elapsed_business_days, amount, sender_country, receiver_country, arrive_by_date, api_key |
transfer_cost | BETA. Estimate what a cross-border payment will COST, split by WHO
PAYS: the sending bank's published fee (the sender's side), what
correspondents deduct in transit and what the beneficiary's own bank
charges to credit it (the beneficiary's side), and what actually lands.
This estimator is in BETA. Present every number as a typical case and a
high case, never as a quote, and never let a user comm params: bank_swift*, amount*, currency*, charge_type, beneficiary_bic, channel, customer_segment, beneficiary_segment, customer_sub_segment, api_key |
mcp_register | Register for an Ohmyfin API key to use paid tools.
Creates an account and sends a 6-digit verification code to your
email. After receiving the code, call mcp_verify to complete
registration and get your API key.
By setting accept_terms to true, you confirm acceptance of the
Ohmyfin Terms & Conditions (https://ohmyfin.ai/terms) on behalf
of your operator, including the API/MCP access terms (Secti params: email*, organization_name*, accept_terms* |
mcp_verify | Verify your email and receive your API key.
After calling mcp_register, check your email for the 6-digit code
and pass it here. On success, returns your production and test
API keys. You must subscribe at ohmyfin.ai/subscription to
activate paid tools.
Examples:
mcp_verify("agent@example.com", "123456") params: email*, code* |
sanctions_screen | Screen a name against global sanctions and watchlists.
Checks the name against 300+ sanctions, designation and watchlists
worldwide, including US OFAC (SDN and non-SDN), EU, UK OFSI, Canada,
Switzerland, Australia, New Zealand, Japan, Israel and national lists.
Returns matching entities with similarity scores. The response says how
many lists were actually searched (lists_searched); report THAT, params: name*, api_key, threshold, subject_type |
eccn_lookup | Look up an Export Control Classification Number (ECCN).
Pure reference tool — returns classification details, controlled
jurisdictions, and license requirements for the given ECCN.
ECCNs are alphanumeric codes (e.g. "5A001") used under export control
regimes (US EAR, EU Dual-Use Regulation, Wassenaar Arrangement) to
classify items that may require an export license.
Examples:
eccn_lookup("5A0 params: eccn* |
country_export_controls | Look up export control restrictions for a specific country.
Returns embargo status, sanctioned programs, control reasons, and
restriction details across jurisdictions (US EAR, EU, UN, etc.)
for the given country. Response also includes a payment_jurisdiction_note
explaining when each listed restriction actually applies to a payment
(US controls only bind when there's a US nexus, etc.).
IMPORTANT params: country_code*, jurisdiction |
export_controls_screen | Screen goods for export-control restrictions to a destination country.
Combines the goods classification with the destination's restriction status
and returns whether a license is required, the risk level, applicable
license policies (e.g. presumption of denial), control reasons (NS, MT, NP,
CB, AT), and proliferation/dual-use flags. Identify the goods by ANY of:
ECCN, HS code, or a free-text des params: destination_country*, eccn, hs_code, goods_description, jurisdiction |
hs_code_lookup | Reverse-lookup an HS code → mapped export-control classifications (ECCNs).
For customs brokers / shippers who have an HS (Harmonized System) code and
need to know which export-control classifications may apply. Returns the
mapped ECCNs with confidence levels, control reasons, sensitivity, and the
governing international regime (Wassenaar, MTCR, NSG, etc.).
A 4-digit HS heading is accepted, but m params: hs_code*, jurisdiction |
goods_classify | Classify goods for export control from a description (or HS code).
Bilingual (English / Russian, auto-detected) goods classifier. Returns the
best-matching HS code (with EN+RU descriptions), related ECCNs, control
reasons (NS, MT, NP, CB, AT...), an export-control level (high/medium/low/
none), a confidence score, and alternative matches for review.
This is destination-agnostic — it identifies W params: description*, hs_code, language |
federal_register_changes | Get recent US regulatory changes from BIS and OFAC.
Returns Federal Register publications including entity list updates,
rule changes, country policy shifts, and new sanctions programs.
Examples:
federal_register_changes() # Last 30 days, all
federal_register_changes(agency="OFAC", days=7) # OFAC changes this week
federal_register_changes(category="entity_list" params: agency, category, severity, days, limit |
track_payment | Track a SWIFT payment by UETR or reference number.
Basic SWIFT payment tracking enriched by data from certain banks in
the correspondent chain. Returns the overall payment status and,
when available, per-bank details showing which banks reported
information about this payment.
IMPORTANT — every trace needs four things:
amount, currency, date, and an identifier (uetr, or reference when
there params: amount*, currency*, date*, uetr, reference, api_key |
tracking_history | Show how a SWIFT payment's tracking results changed over time.
Returns the DISTINCT tracking results recorded for a payment (by UETR or
reference), deduplicated so ten identical re-tracks collapse to one entry
while any change — a new last-update, a status change, or new bank data —
appears as its own entry. Each entry includes what was ENTERED when the
search was run (amount, currency, date) alo params: uetr, reference, api_key |
ssi_lookup | Look up correspondent banking / settlement instructions (SSI) for a bank.
Returns the correspondent banks (nostro accounts) that a given bank
uses to settle payments in a specific currency, including account
numbers (when available) and intermediary chains. Essential for
payment routing and pre-validation.
Each correspondent is annotated with a clearing_note indicating
whether it can clear the c params: swift*, currency*, api_key |
banks_using_correspondent | Reverse SSI lookup — find banks that use a given correspondent for a currency.
Given a correspondent BIC, currency, and origin country, returns the banks
in that country that have a declared nostro at the correspondent for that
currency. Inverse of ssi_lookup.
Returns only swift + name per bank — to retrieve the account number,
intermediary chain, or other SSI details for a specific bank from th params: correspondent_swift*, currency*, country*, name_prefix, page, api_key |
company_search_person | EXPERIMENTAL — Search company registries for a person's directorships, officer roles, and shareholdings.
Searches worldwide company registries to find where a person holds
director, officer, or shareholder positions. Every person and company
found is automatically screened against sanctions lists.
You MUST specify at least one jurisdiction. "ALL" is not supported.
Available jurisdictions: AM, AT params: name*, jurisdictions*, include_sanctions_check, include_inactive_roles, api_key |
company_search_company | EXPERIMENTAL — Search company registries for a company with its officers and shareholders.
Find company registrations across worldwide registries, including
directors, officers, and beneficial owners (PSC/shareholders).
Every entity found is automatically screened against sanctions lists.
You MUST specify at least one jurisdiction. "ALL" is not supported.
Available jurisdictions: AM, AT, AU, BR, params: name*, jurisdictions*, include_sanctions_check, include_officers, include_shareholders, include_only_active, api_key |
company_search_result | EXPERIMENTAL — Retrieve cached company search results by search ID.
Every company_search_person and company_search_company call returns
a search_id. Use this tool to retrieve those results again without
re-running the search.
Examples:
company_search_result("abc123-def456") params: search_id*, api_key |
company_registries | EXPERIMENTAL — List available company registries and supported jurisdictions.
Returns the list of company registries that can be searched,
along with the jurisdiction codes you can use in
company_search_person and company_search_company. This is the LIVE
list and outranks the codes named in those two tools' descriptions.
Any country code not returned here has no registry behind it: a search
nami params: none |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.