banking-intelligence

{
  "id": "aix_1fdc0212b6",
  "name": "banking-intelligence",
  "operator": "(unclaimed - source: registry-official · publisher: ai.ohmyfin)",
  "description": "Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "calendar-sync",
    "data-enrichment",
    "market-data"
  ],
  "protocols": {
    "mcp": "https://mcp.ohmyfin.ai/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 720,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 64,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T21:00:36.918Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://mcp.ohmyfin.ai/"
    }
  ],
  "profile": {
    "mcp_server": "Ohmyfin Banking Intelligence",
    "mcp_version": "3.1.0",
    "tool_count": 34,
    "tools": [
      {
        "name": "swift_lookup",
        "description": "Search banks and financial institutions by name, SWIFT/BIC code, or country.\n\nCovers both SWIFT-connected banks and non-SWIFT financial institutions\n(e-money issuers, payment processors, MFOs, brokerages, VASPs, etc.).\n\nReturns: SWIFT/BIC code (if any), name, city, country, institution type,\nGPI membership, a coarse sanctions FLAG across 7 hard-sanctions watchlists\n(OFAC SDN, EU, UK, CA, CH, AU, NZ — see sanctions_note; this is NOT a full\nscreen, use sanctions_screen for a compliance verdict), and enriched bank\nprofile when available.\n\nEVERY BANK COMES BACK SAYING WHETHER WE HOLD ITS CORRESPON"
      },
      {
        "name": "iban_validate",
        "description": "Validate an IBAN and identify the institution that holds the account.\n\nPerforms format check, country-specific length check, and\nISO 7064 mod-97 checksum verification. Also returns COUNTRY-level\nbanking rules for the IBAN's country prefix (national currency,\nSEPA status, expected format).\n\nCROSS-CHECKS THE BENEFICIARY BANK. Where the country's IBAN registry\nmask defines the bank identifier as four alpha characters (GB, NL, IE,\nRO, PK, MT, JO, QA, KW and others), `bank_identifier.resolved_institution`\nnames the institution that actually holds the account, read out of the\nIBAN itself. Call this "
      },
      {
        "name": "country_banking_rules",
        "description": "Get banking rules and requirements for a country.\n\nReturns IBAN requirements, SEPA membership, FATF listing status,\nnational currency, account format specifications, and country-specific\npayment requirements (mandatory codes like KNP for Kazakhstan,\nPurpose of Payment for UAE, etc.).\n\nThe `fatf_listing` block is the authoritative answer to \"is this country\ngrey-listed / black-listed / under FATF increased monitoring\". Both FATF\npublic lists are held in full, so a `not_listed` status is a positive\ndetermination and not missing data. Use it instead of training data for any\nFATF question, and not"
      },
      {
        "name": "country_payment_codes",
        "description": "Look up country-specific payment codes (KNP, purpose codes, etc.).\n\nUse country_banking_rules first to see which code types a country\nrequires (in the payment_requirements block), then use this tool\nto find the right code value.\n\nArgs:\n    country_code: ISO 3166-1 alpha-2 (e.g., \"KZ\", \"AE\")\n    code_type: Code table to search (from payment_requirements\n               required_fields[].code_type, e.g., \"knp\", \"purpose_code\")\n    search: Optional keyword filter (e.g., \"transport\", \"trade\", \"insurance\")\n\nExamples:\n  country_payment_codes(\"KZ\", \"knp\", \"transport\")\n  country_payment_codes(\"KZ\", \"kn"
      },
      {
        "name": "fx_rate",
        "description": "Get the latest available reference (mid-market) exchange rate for a pair.\n\nRates are the official ECB euro foreign-exchange reference rates where the\nECB publishes the currency; pairs whose currency the ECB does not cover\n(e.g. VND, NGN, PKR, KZT, MAD) fall back to a market data feed. ALWAYS\ncheck the `source` field before describing provenance: \"ecb\" = official\nECB reference rate; \"market\" = indicative mid-market rate, NOT an ECB\nfixing — never call it \"the ECB rate\". The `source_note` field in the\nresult states this explicitly. Coverage is wide (~60 currencies) but NOT\nuniversal — some curre"
      },
      {
        "name": "fx_rate_history",
        "description": "Get the historical reference exchange-rate series for a currency pair.\n\nReturns `series` (the daily rates) plus the metadata needed to describe it\nhonestly. READ `series_coverage` BEFORE CHARACTERISING THE PERIOD. `days`\nis the window we look back over, NOT a promise of how much history exists:\nour series start at different dates per currency, so a 365-day request\nroutinely returns five months. `series_coverage.first_date`/`last_date` are\nwhat the numbers actually span, and `series_coverage.truncated` is true\nwhen that is shorter than you asked for. Say \"the ~N months we hold\", never\n\"over the"
      },
      {
        "name": "gpi_status_codes",
        "description": "Explain SWIFT GPI tracking status codes and provide stuck-payment investigation guidance.\n\nUSE THIS TOOL FIRST whenever the user reports a payment that is stuck,\ndelayed, not arriving, held, pending, rejected, or otherwise not\nbehaving as expected. It is the primary diagnostic entrypoint for\npayment investigation — calling with a specific code returns a\nfull investigation playbook (common delay causes, recommended\nactions, GPI SLA timeframes, escalation steps).\n\nRecommended calls by scenario:\n  - Payment \"stuck\" / \"in progress\" / \"pending\" / \"not arrived\":\n      gpi_status_codes(\"ACSP\")   → pl"
      },
      {
        "name": "swift_message_reference",
        "description": "Look up SWIFT message types — MT (FIN) and MX (ISO 20022).\n\nPass a specific type to get full details, or omit to list all types.\nCovers customer payments (MT103, pacs.008), FI transfers (MT202,\npacs.009), trade finance (MT700, MT760), cash management (MT940,\ncamt.053), and payment status (pacs.002).\n\nAlso use this tool to answer questions about where specific payment\nfields live — e.g., where the UETR sits in an MT103 (Field 121, Block 3\nheader), where charges appear (71A/71F/71G), or which fields carry\nrouting info (56/57). MT103 and pacs.008 responses include a\n`tracing_note` explaining UETR"
      },
      {
        "name": "payment_cutoff_times",
        "description": "Get payment system cutoff times for major clearing systems.\n\nCovers RTGS (T2 — formerly TARGET2, CHAPS, Fedwire, BOJ-NET, SIC),\nnet settlement (CHIPS, BACS), SEPA schemes (SCT, SCT Inst, OCT Inst,\nSDD Core, SDD B2B), FX settlement (CLS, FXYCS), and other systems\n(CIPS, SPEI, FAST).\n\nFor same-day EUR guidance: filter by currency=\"EUR\" to retrieve all\nSEPA schemes plus T2 in one call — the scheme-level view is usually\nwhat treasurers need. Underlying CSMs (TIPS, RT1, EURO1, STEP2) are\nreferenced in scheme notes.\n\nDST-observing systems also carry `season_now` and `operative_cutoff_today`\nfields c"
      },
      {
        "name": "fx_volatility",
        "description": "Get realized FX volatility for a currency pair, and size the FX risk on an exposure held to a future date.\n\nComputes 30-day and 90-day annualized volatility from historical\nECB reference rates (standard deviation of daily log returns,\nannualized by sqrt(252)). Returns a qualitative bucket:\nLOW (<5%), MEDIUM (5-15%), HIGH (15-25%), VERY_HIGH (>25%),\nPEGGED (currency peg — near-zero volatility, e.g., USD/AED, USD/HKD).\n\nAlso returns practical daily/weekly movement estimates and a\nsettlement_risk_note explaining what the volatility means over a\ntypical T+2 settlement period — use these to advise "
      },
      {
        "name": "fx_timing_advisor",
        "description": "Get FX trading windows for FX execution timing and spread / rate optimization.\n\nReturns market sessions and liquidity windows for a currency. Use this\nto understand:\n- **Rate optimization** (primary, reliable use): higher liquidity means\n  tighter spreads and better rates. Execute during peak windows to minimize\n  conversion costs.\n- **Delay diagnosis** (use with care): the FX market session is when a\n  currency TRADES. It is NOT a guaranteed processing schedule for an inbound\n  foreign-currency payment that the beneficiary bank converts on arrival.\n  Conversion timing is beneficiary-bank-spec"
      },
      {
        "name": "payment_method_compare",
        "description": "Compare payment methods and investigate fee deductions for a country pair.\n\nEvaluates SEPA vs SWIFT vs domestic options. Also explains SWIFT charge\noptions (OUR/SHA/BEN) and fee investigation — use this when the beneficiary\nreceived less than expected to understand where the money went and which\nMT103 fields reveal each deduction. Returns cost, speed, requirements,\ncharge options, and step-by-step fee investigation guidance.\n\nArgs:\n    source_country: ISO 3166-1 alpha-2 code (e.g., \"DE\", \"US\")\n    dest_country: ISO 3166-1 alpha-2 code (e.g., \"GB\", \"TR\")\n\nExamples:\n  payment_method_compare(\"DE\""
      },
      {
        "name": "bank_holidays",
        "description": "Get bank/public holidays for a country with payment impact analysis.\n\nReturns all public holidays plus a 'payment_impact' section that shows:\n- Whether today is a business day or holiday in this country\n- Upcoming holidays in the next 14 days\n- Recent holidays in the last 14 days — for diagnosing a payment that is\n  ALREADY stuck (\"in progress for N days\", \"sent X days ago\"). A recent\n  holiday only counts if BOTH hold: it falls INSIDE the payment's own\n  window (on or after the send date), AND its 'costs_a_business_day' is\n  true. One that predates the send date is irrelevant, and one on the\n"
      },
      {
        "name": "is_business_day_check",
        "description": "Check if a specific date is a business day in a country.\n\nAccounts for weekends (country-specific) and public holidays.\nReturns whether the date is a business day, and if not, why\n(weekend or specific holiday name) and the next business day.\n\nThe response carries a `today` block with the server's real current date.\nResolve any relative date in the user's question (\"the 20th\", \"next\nFriday\") against that, not against your own sense of today. A check_date\nalready in the past also returns `date_anchor_warning` — heed it: a\nmis-resolved year flips the answer outright (2025-07-20 is a Sunday,\n2026-"
      },
      {
        "name": "value_date",
        "description": "Calculate the value/settlement date for a payment.\n\nDetermines when a payment will settle based on:\n- Source and destination country holiday calendars\n- Weekend conventions (Sat/Sun or Fri/Sat)\n- Currency center holidays (if FX conversion involved)\n- Settlement convention (T+0, T+1, T+2)\n\nArgs:\n    source_country: Sender's country (ISO 3166-1 alpha-2, e.g., \"US\")\n    dest_country: Receiver's country (ISO 3166-1 alpha-2, e.g., \"DE\")\n    settlement_type: One of \"wire\" (T+0 domestic / T+1 international),\n                     \"fx_spot\" (T+1 or T+2 based on pair),\n                     \"sepa\" (D+1),"
      },
      {
        "name": "settlement_eta",
        "description": "BETA. Estimate when a SWIFT payment will arrive: a corpus-grounded\narrival window with an honest tail, computed from real completed payments\nwe have tracked, projected onto the currency's banking calendar.\n\nThis estimator is in BETA and still calibrating. Say so when you present a\nnumber: call it an estimate or a typical window, never a commitment, and\nnever let a user plan an irreversible decision (a cutoff, a contractual\nsettlement date) on it without that caveat. The payload carries beta=true\nwhile this holds.\n\nTwo modes:\n- Forward (default): \"when will it land\" — returns P50/P90/P95 arriva"
      },
      {
        "name": "transfer_cost",
        "description": "BETA. Estimate what a cross-border payment will COST, split by WHO\nPAYS: the sending bank's published fee (the sender's side), what\ncorrespondents deduct in transit and what the beneficiary's own bank\ncharges to credit it (the beneficiary's side), and what actually lands.\n\nThis estimator is in BETA. Present every number as a typical case and a\nhigh case, never as a quote, and never let a user commit to a contractual\namount on it. The payload carries beta=true while this holds.\n\nHOW TO READ THE ANSWER (relay these honestly):\n- `answered=false` means we REFUSED. The most common reason is that we"
      },
      {
        "name": "mcp_register",
        "description": "Register for an Ohmyfin API key to use paid tools.\n\nCreates an account and sends a 6-digit verification code to your\nemail. After receiving the code, call mcp_verify to complete\nregistration and get your API key.\n\nBy setting accept_terms to true, you confirm acceptance of the\nOhmyfin Terms & Conditions (https://ohmyfin.ai/terms) on behalf\nof your operator, including the API/MCP access terms (Section 3A),\nsanctions screening terms (Section 3B), and financial data\ndisclaimer (Section 3C).\n\nArgs:\n    email: Your email address.\n    organization_name: Your company or project name.\n    accept_terms:"
      },
      {
        "name": "mcp_verify",
        "description": "Verify your email and receive your API key.\n\nAfter calling mcp_register, check your email for the 6-digit code\nand pass it here. On success, returns your production and test\nAPI keys. You must subscribe at ohmyfin.ai/subscription to\nactivate paid tools.\n\nArgs:\n    email: The email you registered with.\n    code: The 6-digit verification code from your email.\n\nExamples:\n  mcp_verify(\"[email protected]\", \"123456\")"
      },
      {
        "name": "sanctions_screen",
        "description": "Screen a name against global sanctions and watchlists.\n\nFREE TIER: 3 screens per day without an API key.\nPAID: Unlimited screens with an API key.\n\nChecks the name against 300+ sanctions, designation and watchlists\nworldwide, including US OFAC (SDN and non-SDN), EU, UK OFSI, Canada,\nSwitzerland, Australia, New Zealand, Japan, Israel and national lists.\nReturns matching entities with similarity scores. The response says how\nmany lists were actually searched (lists_searched); report THAT, and do not\npresent a fixed per-jurisdiction table of \"clear\" rows, which asserts a\nper-list result the screen"
      },
      {
        "name": "eccn_lookup",
        "description": "Look up an Export Control Classification Number (ECCN).\n\nPure reference tool — returns classification details, controlled\njurisdictions, and license requirements for the given ECCN.\n\nECCNs are alphanumeric codes (e.g. \"5A001\") used under export control\nregimes (US EAR, EU Dual-Use Regulation, Wassenaar Arrangement) to\nclassify items that may require an export license.\n\nArgs:\n    eccn: The ECCN to look up (e.g. \"5A001\", \"3A001\", \"1C351\").\n\nExamples:\n  eccn_lookup(\"5A001\")   # Telecommunications security equipment\n  eccn_lookup(\"3A001\")   # Electronic components\n  eccn_lookup(\"1C351\")   # Human "
      },
      {
        "name": "country_export_controls",
        "description": "Look up export control restrictions for a specific country.\n\nReturns embargo status, sanctioned programs, control reasons, and\nrestriction details across jurisdictions (US EAR, EU, UN, etc.)\nfor the given country. Response also includes a payment_jurisdiction_note\nexplaining when each listed restriction actually applies to a payment\n(US controls only bind when there's a US nexus, etc.).\n\nIMPORTANT: Each jurisdiction's controls only bind a payment when the\npayment has a nexus to that jurisdiction. Use the jurisdiction filter\nwhen you know the payment's actual jurisdictional touchpoints (sender\n"
      },
      {
        "name": "export_controls_screen",
        "description": "Screen goods for export-control restrictions to a destination country.\n\nCombines the goods classification with the destination's restriction status\nand returns whether a license is required, the risk level, applicable\nlicense policies (e.g. presumption of denial), control reasons (NS, MT, NP,\nCB, AT), and proliferation/dual-use flags. Identify the goods by ANY of:\nECCN, HS code, or a free-text description (English or Russian).\n\nIMPORTANT — jurisdiction nexus: each jurisdiction's controls only bind a\npayment/shipment when there is a nexus to that jurisdiction (US EAR binds\nUS persons, USD-clear"
      },
      {
        "name": "hs_code_lookup",
        "description": "Reverse-lookup an HS code → mapped export-control classifications (ECCNs).\n\nFor customs brokers / shippers who have an HS (Harmonized System) code and\nneed to know which export-control classifications may apply. Returns the\nmapped ECCNs with confidence levels, control reasons, sensitivity, and the\ngoverning international regime (Wassenaar, MTCR, NSG, etc.).\n\nA 4-digit HS heading is accepted, but mappings are richest at the 6-digit\nsubheading level (e.g. \"854231\" rather than \"8542\"). An empty mapping list\nmeans no export-control mapping is on file for that code — it is NOT a\nguarantee the goods"
      },
      {
        "name": "goods_classify",
        "description": "Classify goods for export control from a description (or HS code).\n\nBilingual (English / Russian, auto-detected) goods classifier. Returns the\nbest-matching HS code (with EN+RU descriptions), related ECCNs, control\nreasons (NS, MT, NP, CB, AT...), an export-control level (high/medium/low/\nnone), a confidence score, and alternative matches for review.\n\nThis is destination-agnostic — it identifies WHAT the goods are and whether\nthey are controlled in principle. To get the license decision FOR A SPECIFIC\ndestination, pass the result into export_controls_screen.\n\nIMPORTANT, the matcher is lexical,"
      }
    ],
    "profiled_at": "2026-09-24T21:00:36.918Z"
  },
  "unreachable": false
}