{"data":{"name":"ai.ohmyfin/banking-intelligence","title":null,"description":"Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.","version":"1.0.0","websiteUrl":"https://mcp.ohmyfin.ai","repositoryUrl":null,"remotes":[{"url":"https://mcp.ohmyfin.ai/mcp","type":"streamable-http"}],"packages":[],"status":"active","isLatest":true,"publishedAt":"2026-06-12T11:47:06.337Z","updatedAt":"2026-06-12T11:47:06.337Z","source":"official-registry","verification":"official","confidence":100,"stars":null,"sources":[{"stars":null,"title":null,"source":"official-registry","sourceId":"ai.ohmyfin/banking-intelligence","updatedAt":"2026-06-12T11:47:06.337Z","confidence":100,"websiteUrl":"https://mcp.ohmyfin.ai","description":"Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.","verification":"official","repositoryUrl":null}],"toolIndex":{"tools":[{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"bank_holidays","title":"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  country's banking weekend closed nothing that was open — neither may be\n  subtracted or given to the user as a cause. An empty list affirmatively\n  means no recent holiday explains the delay — do not invent one from\n  training data.\n- Every holiday entry (upcoming, recent, and next_holiday_after_today)\n  carries 'costs_a_business_day'. Roughly one holiday date in six lands on\n  its own country's weekend and shortens nothing; check the flag before\n  quoting a holiday as a delay, a closure or a reason a window was short.\n- elapsed_business_days_by_send_date — the AUTHORITATIVE elapsed\n  business-day count keyed by send date (weekends + this country's\n  holidays already excluded). Use it verbatim instead of hand-counting.\n- Next business day and how many consecutive non-business days remain\nThis context helps determine if holidays are causing payment delays.\n\nExamples:\n  bank_holidays(\"US\")\n  bank_holidays(\"DE\", 2026)\n  bank_holidays(\"GB\", 2025)","inputSchema":{"type":"object","properties":{"country_code":{"description":"ISO 3166-1 alpha-2 country code, e.g. \"US\", \"DE\", \"GB\".","type":"string"},"year":{"anyOf":[{"type":"integer"},{"type":"null"}],"default":null,"description":"Calendar year, 2020-2030 (default: the current year). Values outside the range are clamped."}},"required":["country_code"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":true},"definitionHash":"f34b35a038c8ffd5a09dfbc3b79f525f72c64510859b14699f0862d2fc6d55af","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"banks_using_correspondent","title":"Banks Using a Correspondent","description":"Reverse SSI lookup — find banks that use a given correspondent for a currency.\n\nGiven a correspondent BIC, currency, and origin country, returns the banks\nin that country that have a declared nostro at the correspondent for that\ncurrency. Inverse of ssi_lookup.\n\nReturns only swift + name per bank — to retrieve the account number,\nintermediary chain, or other SSI details for a specific bank from the\nresult list, call ssi_lookup(bank_swift, currency) on it.\n\nCountry and currency are required (not optional) — both bound the result\nset and the query is rejected without them.\n\nRequires an API key with an active PRO, VIP, or FI subscription.\n\nExamples:\n  banks_using_correspondent(\"IRVTUS3N\", \"USD\", \"AE\")\n  banks_using_correspondent(\"CITIUS33\", \"USD\", \"SA\", name_prefix=\"AL\")","inputSchema":{"type":"object","properties":{"correspondent_swift":{"description":"BIC of the correspondent bank, 8 or 11 characters (e.g. \"IRVTUS3N\").","type":"string"},"currency":{"description":"ISO 4217 currency code (e.g. \"USD\").","type":"string"},"country":{"description":"ISO 3166-1 alpha-2 country code of the client banks (e.g. \"AE\").","type":"string"},"name_prefix":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Optional prefix on the client bank's name (e.g. \"AL\")."},"page":{"default":1,"description":"Result page, 1-4 (default 1). Any other value is refused.","type":"integer"},"api_key":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Your Ohmyfin API key (prod-...). Optional here: it can be sent instead as a KEY header or an Authorization: Bearer header. What the tool requires of the key is in its description."}},"required":["correspondent_swift","currency","country"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"723c3587e0690647856bd669abeaf5ebcab2c05faf437b27034de833d11c1be9","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"company_registries","title":"Available Company Registries (Experimental)","description":"EXPERIMENTAL — List available company registries and supported jurisdictions.\n\nReturns the list of company registries that can be searched,\nalong with the jurisdiction codes you can use in\ncompany_search_person and company_search_company. This is the LIVE\nlist and outranks the codes named in those two tools' descriptions.\n\nAny country code not returned here has no registry behind it: a search\nnaming it comes back empty and \"completed\", which does not mean the\ncompany is unregistered. `XX` (GLEIF LEI) is global and is the fallback\nfor those jurisdictions.\n\nNo API key required.\n\nExamples:\n  company_registries()","inputSchema":{"type":"object","properties":{},"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"ad37e55202c1fd99f57bc433848a145d068fd23dd1e837cdb5ccf276f0a706a2","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"company_search_company","title":"Company Registry Search: Company (Experimental)","description":"EXPERIMENTAL — Search company registries for a company with its officers and shareholders.\n\nFind company registrations across worldwide registries, including\ndirectors, officers, and beneficial owners (PSC/shareholders).\nEvery entity found is automatically screened against sanctions lists.\n\nYou MUST specify at least one jurisdiction. \"ALL\" is not supported.\nAvailable jurisdictions: AM, AT, AU, BR, CA, CH, CZ, DE, DK, EE, FI,\nFR, IE, IL, IS, LT, LV, NL, NO, PL, SG, UK, XX. Call\ncompany_registries() for the live list — this one can go stale.\n\nXX is GLEIF LEI, a GLOBAL registry rather than a country. Reach for it\nwhenever the company sits outside the national registries above — a\nsupplier in Hong Kong, mainland China, the US or the UAE. Hits carry an\nLEI, a registered address and a search.gleif.org URL the user can open.\n\nA jurisdiction NOT on that list is dropped silently by the backend: you\nget total_results 0 with status \"completed\" and no error. That means the\ncompany was never searched for — it is NOT evidence that it is\nunregistered or fake, and saying so to someone checking a counterparty\nbefore wiring money is the most damaging thing this tool can do. Check\n`jurisdictions_not_searched` and `coverage_warning` in the response\nbefore you report an empty result.\n\nExamples:\n  company_search_company(\"Equinor\", jurisdictions=[\"NO\"])\n  company_search_company(\"Acme Corp\", jurisdictions=[\"UK\", \"DE\"], include_only_active=True)","inputSchema":{"type":"object","properties":{"name":{"description":"Company name to search for.","type":"string"},"jurisdictions":{"description":"Registry codes to search, at least one (e.g. [\"UK\"]). \"ALL\" is not supported. The UK registry is \"UK\", not \"GB\"; \"XX\" is GLEIF LEI (global). company_registries() returns the live list.","items":{"type":"string"},"type":"array"},"include_sanctions_check":{"default":true,"description":"Screen every company and person found against sanctions lists (default true).","type":"boolean"},"include_officers":{"default":true,"description":"Include directors and officers (default true).","type":"boolean"},"include_shareholders":{"default":true,"description":"Include PSC / beneficial owners (default true).","type":"boolean"},"include_only_active":{"default":false,"description":"Return active companies only (default false).","type":"boolean"},"api_key":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Your Ohmyfin API key (prod-...). Optional here: it can be sent instead as a KEY header or an Authorization: Bearer header. What the tool requires of the key is in its description."}},"required":["name","jurisdictions"],"additionalProperties":false},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true},"definitionHash":"be15a956af65427bc2bdff00d9279c103c25c93007e73620ed196f97f64b8f64","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"company_search_person","title":"Company Registry Search: Person (Experimental)","description":"EXPERIMENTAL — Search company registries for a person's directorships, officer roles, and shareholdings.\n\nSearches worldwide company registries to find where a person holds\ndirector, officer, or shareholder positions. Every person and company\nfound is automatically screened against sanctions lists.\n\nYou MUST specify at least one jurisdiction. \"ALL\" is not supported.\nAvailable jurisdictions: AM, AT, AU, BR, CA, CH, CZ, DE, DK, EE, FI,\nFR, IE, IL, IS, LT, LV, NL, NO, PL, SG, UK, XX. Call\ncompany_registries() for the live list — this one can go stale.\n\nXX is GLEIF LEI, a GLOBAL registry rather than a country. Use it for\nanyone connected to a company outside the national registries above.\n\nA jurisdiction NOT on that list is dropped silently by the backend: you\nget total_results 0 with status \"completed\" and no error. That means the\nperson was never searched for — it is NOT evidence they hold no roles.\nCheck `jurisdictions_not_searched` and `coverage_warning` in the response\nbefore you report an empty result to the user.\n\nExamples:\n  company_search_person(\"John Smith\", jurisdictions=[\"UK\", \"NO\"])\n  company_search_person(\"Jane Doe\", jurisdictions=[\"DE\"])","inputSchema":{"type":"object","properties":{"name":{"description":"Person name to search for.","type":"string"},"jurisdictions":{"description":"Registry codes to search, at least one (e.g. [\"UK\", \"NO\"]). \"ALL\" is not supported. The UK registry is \"UK\", not \"GB\"; \"XX\" is GLEIF LEI (global). company_registries() returns the live list.","items":{"type":"string"},"type":"array"},"include_sanctions_check":{"default":true,"description":"Screen every person and company found against sanctions lists (default true).","type":"boolean"},"include_inactive_roles":{"default":true,"description":"Include resigned and ceased roles (default true).","type":"boolean"},"api_key":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Your Ohmyfin API key (prod-...). Optional here: it can be sent instead as a KEY header or an Authorization: Bearer header. What the tool requires of the key is in its description."}},"required":["name","jurisdictions"],"additionalProperties":false},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true},"definitionHash":"f3a3bb73e49b1b6ef0b98546d9e5df338e4ad8e6ed6b8d1de7667dc62c5a947c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"company_search_result","title":"Company Search Result (Experimental)","description":"EXPERIMENTAL — Retrieve cached company search results by search ID.\n\nEvery company_search_person and company_search_company call returns\na search_id. Use this tool to retrieve those results again without\nre-running the search.\n\nExamples:\n  company_search_result(\"abc123-def456\")","inputSchema":{"type":"object","properties":{"search_id":{"description":"The search_id returned by a previous company_search_person or company_search_company call.","type":"string"},"api_key":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Your Ohmyfin API key (prod-...). Optional here: it can be sent instead as a KEY header or an Authorization: Bearer header. What the tool requires of the key is in its description."}},"required":["search_id"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"45856c2352f694e27a2d08852d7957be3f925cd2c7290dd9c319546487a6dece","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"country_banking_rules","title":"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 note that the coarse `fatf` field is a separate, weaker\nsignal about regional-body membership that says nothing about listing.\n\nEverything here is COUNTRY-level. `currency` is the country's national\ncurrency, not the denomination of any beneficiary account — never pair it\nwith the payment currency to diagnose a currency mismatch (see\n`currency_note` in the response).\n\nUse this to check country-specific STP rules that could cause payment delays, repairs, or rejections (e.g., missing purpose codes, regulatory fields).\n\n`payment_code_requirement.required` is what our data holds on country-specific\npurpose / payment codes: true (a requirement is on file; payment_requirements\nlists the code tables when we hold them), false (our profile states that none\nis imposed), \"conditional\", or \"unknown\" (not covered: an absence of data,\nnever a finding that no code is required). Use country_payment_codes to look\nup specific code values.\n\nExamples:\n  country_banking_rules(\"DE\")\n  country_banking_rules(\"KZ\")   # includes KNP requirement info\n  country_banking_rules(\"AE\")   # includes Purpose of Payment info","inputSchema":{"type":"object","properties":{"country_code":{"description":"ISO 3166-1 alpha-2 country code, e.g. \"DE\", \"US\", \"KZ\".","type":"string"}},"required":["country_code"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"c1723b6b05eaa0c9727832c44d4ea6cfe887d86934abb31a176fee7fd106b696","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"country_export_controls","title":"Country Export-Control Restrictions","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\ncountry, clearing currency, intermediary banks). For a CHF/EUR payment\nwith no US bank in the chain, US export controls are informational only\n— do NOT cite them as compliance blockers without confirming a US nexus.\n\nExamples:\n  country_export_controls(\"RU\")          # Russia — heavily embargoed\n  country_export_controls(\"CN\")          # China — partial restrictions\n  country_export_controls(\"DE\")          # Germany — minimal controls\n  country_export_controls(\"RU\", \"US\")    # Russia, US jurisdiction only\n\nUse case: 'What export restrictions apply to shipping to Russia?'","inputSchema":{"type":"object","properties":{"country_code":{"description":"ISO 3166-1 alpha-2 country code, e.g. \"RU\", \"CN\", \"DE\".","type":"string"},"jurisdiction":{"default":"","description":"Optional filter by jurisdiction, e.g. \"US\", \"EU\". Omit it for every jurisdiction.","type":"string"}},"required":["country_code"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"f7f77d4b666e9851a00c314d1aefcab239c1b9785801dada1ef7d7d123ad10f3","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"country_payment_codes","title":"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\nExamples:\n  country_payment_codes(\"KZ\", \"knp\", \"transport\")\n  country_payment_codes(\"KZ\", \"knp\", \"insurance\")\n  country_payment_codes(\"AE\", \"purpose_code\", \"trade\")\n  country_payment_codes(\"KZ\", \"knp\")   # all codes (large response)","inputSchema":{"type":"object","properties":{"country_code":{"description":"ISO 3166-1 alpha-2 country code, e.g. \"KZ\", \"AE\".","type":"string"},"code_type":{"description":"Which code table to search, as named in country_banking_rules payment_requirements.required_fields[].code_type (e.g. \"knp\", \"purpose_code\"). Case-insensitive.","type":"string"},"search":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Optional keyword filter (e.g. \"transport\", \"trade\", \"insurance\"). Omit it to list every code in the table, which is a large response."}},"required":["country_code","code_type"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"81afcee0b9814c6b7f797bd1761d4433c558b602478c8060c280bb54791c48e3","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"eccn_lookup","title":"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\nExamples:\n  eccn_lookup(\"5A001\")   # Telecommunications security equipment\n  eccn_lookup(\"3A001\")   # Electronic components\n  eccn_lookup(\"1C351\")   # Human pathogens, zoonoses, toxins","inputSchema":{"type":"object","properties":{"eccn":{"description":"Export Control Classification Number, e.g. \"5A001\", \"3A001\", \"1C351\". Case-insensitive.","type":"string"}},"required":["eccn"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"df961bfc6472300585bcd3cdb8a51f048b045a05319ca4372a49c5cc41c3a4ad","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"export_controls_screen","title":"Export-Control Goods Screening","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-clearing, and US-origin items; EU/UK/JP bind their persons,\ncurrencies, and origin). Use jurisdiction=\"ALL\" for a comprehensive\nmulti-jurisdiction view, or pick the one matching the actual touchpoints.\n\nIMPORTANT, prefer eccn or hs_code: goods_description is a fallback: the\nclassifier matches it lexically, so a vague description still returns one\nspecific HS code and it is usually the wrong one (\"industrial machinery\"\nreturns bakery and pasta machinery). When you pass a description only, the\nresult carries classification_basis and classification_confidence_note;\nread them, never quote the inferred code back to the user as their HS code\nor ECCN, and ask for the code on their invoice or export declaration. The\ndestination findings (embargo, transshipment risk, screening duties) are\nNOT affected by that doubt, so report them normally.\n\nProvide at least one of eccn / hs_code / goods_description.\n\nExamples:\n  export_controls_screen(\"RU\", eccn=\"3A001\")                       # electronics → Russia\n  export_controls_screen(\"CN\", eccn=\"3A090\")                       # advanced computing → China\n  export_controls_screen(\"IR\", goods_description=\"industrial valves\")\n  export_controls_screen(\"RU\", goods_description=\"drone\", jurisdiction=\"ALL\")\n  export_controls_screen(\"DE\", hs_code=\"854231\")                   # → Germany (allied)\n\nUse case: 'Can we ship integrated circuits to Russia?'","inputSchema":{"type":"object","properties":{"destination_country":{"description":"Destination country, ISO 3166-1 alpha-2 country code (e.g. \"RU\", \"CN\").","type":"string"},"eccn":{"default":"","description":"Export Control Classification Number, e.g. \"3A001\". Give at least one of eccn, hs_code, goods_description.","type":"string"},"hs_code":{"default":"","description":"Harmonized System code, 4-8 digits (e.g. \"854231\"). Give at least one of eccn, hs_code, goods_description.","type":"string"},"goods_description":{"default":"","description":"Free-text goods description, English or Russian. A fallback for when no eccn or hs_code is known; see the description.","type":"string"},"jurisdiction":{"default":"US","description":"\"US\" (default), \"EU\", \"UK\", \"JP\", \"ITAR\", or \"ALL\".","type":"string"}},"required":["destination_country"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"6a3f88e62c8042c14b8a113943f936f34b382f008de94cb92dcce190cbeb5d38","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"federal_register_changes","title":"Federal Register Export and Sanctions Changes","description":"Get recent US regulatory changes from BIS and OFAC.\n\nReturns Federal Register publications including entity list updates,\nrule changes, country policy shifts, and new sanctions programs.\n\nExamples:\n  federal_register_changes()                          # Last 30 days, all\n  federal_register_changes(agency=\"OFAC\", days=7)     # OFAC changes this week\n  federal_register_changes(category=\"entity_list\", severity=\"critical\")\n\nUse case: 'Any new entity list additions affecting China?'","inputSchema":{"type":"object","properties":{"agency":{"default":"","description":"Optional: \"BIS\" (Bureau of Industry and Security) or \"OFAC\" (Office of Foreign Assets Control). Omit it for both.","type":"string"},"category":{"default":"","description":"Optional: \"entity_list\", \"rule_change\", \"country_policy\" or \"sanctions\". Omit it for every category.","type":"string"},"severity":{"default":"","description":"Optional: \"critical\", \"high\", \"medium\" or \"low\". Omit it for every level.","type":"string"},"days":{"default":30,"description":"Days to look back, 1-365 (default 30). A value outside the range is refused.","type":"integer"},"limit":{"default":50,"description":"Maximum number of changes to return (default 50).","type":"integer"}},"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"aeae8734728e7c7643c5874195aa70bcdc9b16f0088d4635829c33b488316aac","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"fx_rate","title":"FX Reference 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 currencies (e.g. CLP, COP, PEN) have no rate on file at\nall. When a leg is missing, the error names exactly which currency is\nuncovered: relay that we hold no rate rather than supplying one from your\nown knowledge. Non-EUR pairs are\ncomputed as cross-rates via EUR (e.g., USD/GBP = EUR/GBP / EUR/USD), so\nthey are indicative mid-rates, not dealable/executable rates.\n\nBOTH currencies are required. Always pass the exact pair you intend.\nThere is no implicit default pair: a call that omits or mis-names a\ncurrency returns a \"missing required argument\" error rather than a\nsilently-wrong rate. Never assume EUR/USD when the user asked about a\ndifferent pair such as USD/VND.\n\nExamples:\n  fx_rate(\"EUR\", \"USD\")\n  fx_rate(\"GBP\", \"JPY\")\n  fx_rate(\"USD\", \"VND\")","inputSchema":{"type":"object","properties":{"base":{"description":"Base currency, ISO 4217 (e.g. \"USD\"). The rate is quoted as units of target per 1 base.","type":"string"},"target":{"description":"Target currency, ISO 4217 (e.g. \"VND\").","type":"string"}},"required":["base","target"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"6b36c1fbba318b7919a947afb8b0fe1356649dfd2d235fd40d6991392f9e626c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"fx_rate_history","title":"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 past year\", and never fill the gap from your own knowledge.\n\nCHECK `source` BEFORE ATTRIBUTING PROVENANCE. \"ecb\" = official ECB euro\nreference fixings, weekdays only. \"market\" = an indicative market data feed\nfor a currency the ECB does not publish (AED, QAR, SAR, KWD, NGN, PKR, VND,\nKZT, RUB, UAH and ~20 more). A market series is NOT an ECB series and must\nnever be described as one. Where a pair mixes the two, `series_coverage`\nreports the dates lost to aligning them.\n\n`peg_context` appears when either currency is pegged, including when the\npeg is against some third currency: it names the anchor and the pair whose\nmovement you are really looking at. Take the peg date from there rather\nthan from memory.\n\nAn uncovered pair returns an `error` naming the missing leg instead of an\nempty series. Report that we hold no history rather than describing the\nrate as stable or range-bound.\n\nBOTH currencies are required. Always pass the exact pair you intend.\nThere is no implicit EUR/USD default: an omitted or mis-named currency\nerrors rather than returning the wrong pair's history.\n\nExamples:\n  fx_rate_history(\"EUR\", \"USD\", 30)\n  fx_rate_history(\"GBP\", \"CHF\", 365)","inputSchema":{"type":"object","properties":{"base":{"description":"Base currency, ISO 4217 (e.g. \"EUR\"). Rates are quoted as units of target per 1 base.","type":"string"},"target":{"description":"Target currency, ISO 4217 (e.g. \"USD\").","type":"string"},"days":{"default":90,"description":"Lookback window in calendar days, 1-365 (default 90). Values outside the range are clamped. A ceiling on the window, not a promise of that many data points.","type":"integer"}},"required":["base","target"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"49d6155df5d5f9b6ae400bd0dcc2a531f31bbb1c6a846f6ff25a8ee6a6080a9f","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"fx_timing_advisor","title":"FX Market Session Timing","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-specific (some convert in real time\n  during the session, others batch once or twice daily), so do NOT tell the\n  user a payment is \"held until the next session\" and do not quote specific\n  hold durations (\"adds X hours\", \"overnight delay\"); those are bank policy\n  and are not in our data. For the binding delivery-side cutoff that gates the\n  converted local-currency leg, call country_banking_rules(destination) and\n  read local_clearing.systems. When a currency is restricted, this tool's own\n  output carries an inbound_processing_note with the accurate framing to quote.\n\nPass a currency code to get its optimal window, or omit to get\nall market sessions and overlap windows.\n\nExamples:\n  fx_timing_advisor(\"EUR\")\n  fx_timing_advisor(\"JPY\")\n  fx_timing_advisor(\"INR\")  # Check INR conversion windows\n  fx_timing_advisor()","inputSchema":{"type":"object","properties":{"currency":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Optional ISO 4217 code (e.g. \"EUR\", \"JPY\"). Omit it to get every session and overlap."}},"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"3522837faddc5108ecfca33660c1f48cf0d12a02044fc9ed0af41cf3110e5d56","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"fx_volatility","title":"FX Volatility and Exposure Band","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 users on FX\nrisk for their specific payment.\n\nPASS horizon_days WHENEVER THE USER'S EXPOSURE RUNS PAST SETTLEMENT.\nIt returns a `horizon` block: the volatility scaled to that horizon as an\nactual rate band at 1 and 2 sigma, which end of the band hurts a payer\nversus a receiver, and what the band does and does not tell them about\nhedging. Use it for questions shaped like:\n  - \"should I hedge / lock in / take a forward for <future period>?\"\n  - \"how far could <pair> move by <date>?\"\n  - \"what rate should I budget for next year?\"\n  - \"I have invoices in <currency> through 2027 — what is my risk?\"\n  - any exposure not settling within a few days.\nCount the calendar days from today to the date the exposure ends and pass\nthat. Rough is fine — the band moves with the square root of time, so a\nmonth either way barely changes it.\n\nRead `sample_depth` before quoting any figure: this is REALISED volatility\nfrom a short history, not implied volatility, and the sample may be shorter\nthan the horizon asked about (`horizon.beyond_sample`). Say so.\n\nIMPORTANT — the band is the range of FUTURE SPOT. It is not a rate anyone\ncan transact at, and the width of the band is NOT the cost of a hedge. A\nforward is priced off the interest-rate differential between the two\ncurrencies, which we do not hold and must not guess or recall from memory.\nRelay `horizon.hedge_cost_note` rather than inventing forward points, a\ncarry figure, or a \"typical\" hedging cost. Never state a forward rate.\n\nExamples:\n  fx_volatility(\"EUR\", \"USD\")\n  fx_volatility(\"USD\", \"TRY\")\n  fx_volatility(\"GBP\", \"JPY\", 506)   # exposure running to end-2027\n  fx_volatility(\"EUR\", \"PLN\", 90)    # invoice settling in a quarter","inputSchema":{"type":"object","properties":{"base":{"description":"Base currency, ISO 4217 (e.g. \"EUR\").","type":"string"},"target":{"description":"Target currency, ISO 4217 (e.g. \"TRY\").","type":"string"},"horizon_days":{"anyOf":[{"type":"integer"},{"type":"null"}],"default":null,"description":"Optional. Calendar days from today to the end of the exposure, 1-1825. A value outside that range returns an error instead of a band. Omit it for spot / settlement risk only."}},"required":["base","target"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"dd5dbe3cf365626c3dc0220956d1e6ad5307fd2144898df6950d6f063e5ba46c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"goods_classify","title":"Goods Classification","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, and confidence scores the strength of\nthe string match, not the correctness of the classification: \"equipment\"\nreturns semiconductor manufacturing equipment at confidence 1.0. Treat the\ncode as a suggestion for narrowing the question. When no hs_code was\nsupplied the result carries classification_basis and\nclassification_confidence_note; read them before quoting any code, and ask\nthe user for the HS code or ECCN on their shipping documentation.\n\nExamples:\n  goods_classify(\"uranium centrifuge\")                 # → HS 840120, ECCN 0B001\n  goods_classify(\"центрифуга для обогащения урана\")    # Russian query, same result\n  goods_classify(\"semiconductor manufacturing equipment\")\n  goods_classify(\"\", hs_code=\"840120\")                 # direct HS lookup\n\nUse case: 'Is a semiconductor lithography machine export-controlled?'","inputSchema":{"type":"object","properties":{"description":{"description":"Goods description, at least 2 characters (e.g. \"uranium centrifuge\", \"центрифуга для урана\").","type":"string"},"hs_code":{"default":"","description":"Optional known HS code (4 or 6 digits) for a direct lookup.","type":"string"},"language":{"default":"","description":"Optional hint: \"en\" or \"ru\" (auto-detected if omitted).","type":"string"}},"required":["description"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"57a4291bceeb21e0ea715de07961c29745990f18c669bc7527b0d80feafaf124","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"gpi_status_codes","title":"Payment Status Codes and Stuck-Payment Playbooks","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\")   → playbook for in-progress payments\n  - Payment explicitly \"on hold\" / compliance review:\n      gpi_status_codes(\"PDNG\")   → playbook for held payments\n  - Payment \"blocked\" / sanctions flag:\n      gpi_status_codes(\"BLCK\")   → playbook for blocked payments\n  - Payment rejected by a bank in the chain (never credited):\n      gpi_status_codes(\"RJCT\")   → rejection investigation playbook\n  - Payment returned to sender (accepted then sent back):\n      gpi_status_codes(\"RTRN\")   → return investigation playbook\n  - Reference for ISO 20022 codes:\n      gpi_status_codes()         → list all codes\n\nEach code call returns:\n  - Code description and meaning\n  - For ACSP/PDNG/BLCK/RJCT/RTRN: investigation playbook with common\n    causes, recommended actions (request gCCT tracker, request\n    pacs.002/pacs.004 reason code, verify beneficiary details,\n    escalate via MT199, etc.), and common ISO 20022 reason codes\n    (AC01, AC04, AG01, RR01-RR04, etc.) when applicable\n  - Child reason codes (e.g., G001-G004 for ACSP) that narrow the\n    cause further\n\nCommon codes: ACCC (success), ACSP (in progress), RJCT (rejected),\nPDNG (on hold), BLCK (blocked). GPI reason codes (G000-G004) qualify\nACSP with more detail (e.g. G001 = passed on to a bank that is not a\ngpi member, G002 = credit pending, may not be same day).\n\nExamples:\n  gpi_status_codes(\"ACSP\")   # stuck-payment diagnostic playbook\n  gpi_status_codes(\"G001\")   # detail on a specific reason code\n  gpi_status_codes()         # full reference list","inputSchema":{"type":"object","properties":{"code":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Optional ISO 20022 status code (ACSP, ACCC, PDNG, RJCT, RTRN, BLCK) or reason code (e.g. G001), case-insensitive. A status code returns its investigation playbook. Omit it to list every code."}},"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"025c01385ebc2ca6414c7da0585b04de3e69b14422effe8ce874fef51f6a0754","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"hs_code_lookup","title":"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 are uncontrolled; confirm with goods_classify or a\nformal classification.\n\nExamples:\n  hs_code_lookup(\"854231\")          # semiconductors → 3A001 / 3A090 ...\n  hs_code_lookup(\"841112\")          # turbojet engines → 9A001 ...\n  hs_code_lookup(\"854231\", \"US\")    # US mappings only\n\nUse case: 'What export controls might apply to HS code 854231?'","inputSchema":{"type":"object","properties":{"hs_code":{"description":"HS code, 4-6 digits (e.g. \"854231\", \"8411\"). Dots and spaces are fine.","type":"string"},"jurisdiction":{"default":"","description":"Optional filter: \"US\", \"EU\", \"UK\" or \"JP\".","type":"string"}},"required":["hs_code"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"cfb0b2115924d690a2f7201f533ed816ee51908123c3ef9e112f62ce54da185a","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"iban_validate","title":"IBAN Validation","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 whenever the user supplies an IBAN AND names a\nbeneficiary bank or BIC — if the two disagree, that mismatch is a far\nbetter explanation for a rejected or returned payment than anything you\ncan infer, and it is invisible without this call. Everywhere else the\nbank identifier is a NATIONAL bank/sort code (the German BLZ, Italian\nABI, French code banque): `bank_identifier.code` is those characters,\n`is_bic_prefix` is false, and no institution is named — quote the code\nwhen telling the user what to check, never a bank name derived from it.\n\nA FAILURE IS NOT ALWAYS A CHECKSUM FAILURE. An IBAN of the right length\nwhose characters break the country's mask (a letter where the country\nrequires a digit — O for 0, I for 1) is refused BEFORE mod-97 runs, with\n`format_violations` naming the position. Report the position and the\ncharacter; do not tell the user the check digits are wrong.\n\n`valid: true` means the check digits are right and NOTHING MORE — not\nthat the account exists, is open, or belongs to the named beneficiary or\nthe named bank. Never rule out the account details on the strength of it\nwhen diagnosing a failed payment (see `verification_note`).\n\nAn IBAN encodes country + bank + account number and carries NO\ncurrency information. `country_currency` is the country's national\ncurrency, NOT this account's denomination — never infer a currency\nmismatch or a \"resend in X\" recommendation from it (see\n`currency_note` in the response).\n\nExamples:\n  iban_validate(\"DE89370400440532013000\")\n  iban_validate(\"GB29 NWBK 6016 1331 9268 19\")","inputSchema":{"type":"object","properties":{"iban":{"description":"The IBAN to check, e.g. \"DE89370400440532013000\". Spaces and hyphens are ignored and letters are upper-cased.","type":"string"}},"required":["iban"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"0af95c6bc660e323690210a45af4b36cb6d462281737cc15f586f9373eedbb39","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"is_business_day_check","title":"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-08-20 is a Thursday).\n\nExamples:\n  is_business_day_check(\"US\", \"2026-12-25\")\n  is_business_day_check(\"DE\", \"2026-03-12\")\n  is_business_day_check(\"GB\", \"2026-01-01\")","inputSchema":{"type":"object","properties":{"country_code":{"description":"ISO 3166-1 alpha-2 country code, e.g. \"US\", \"DE\".","type":"string"},"check_date":{"description":"The date to check, YYYY-MM-DD (ISO 8601).","type":"string"}},"required":["country_code","check_date"],"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":true},"definitionHash":"ff728ba65278356407b90fd3ed463d44ba18b3f9119335408d824f59386dd5a1","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"mcp_register","title":"Register for an API Key","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\nExamples:\n  mcp_register(\"agent@example.com\", \"Acme Corp\", true)","inputSchema":{"type":"object","properties":{"email":{"description":"Your email address. The verification code is sent to it.","type":"string"},"organization_name":{"description":"Your company or project name.","type":"string"},"accept_terms":{"description":"Must be true. Confirms acceptance of the Ohmyfin Terms & Conditions at https://ohmyfin.ai/terms.","type":"boolean"}},"required":["email","organization_name","accept_terms"],"additionalProperties":false},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true},"definitionHash":"5066c999ad424085b7075fa86dcaeaabfdd9162310df145fb59276fa3a96029c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"mcp_verify","title":"Verify Email and Activate API Key","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\nExamples:\n  mcp_verify(\"agent@example.com\", \"123456\")","inputSchema":{"type":"object","properties":{"email":{"description":"The email address you registered with.","type":"string"},"code":{"description":"The 6-digit verification code from that email.","type":"string"}},"required":["email","code"],"additionalProperties":false},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true},"definitionHash":"5a935b4a97d53b3fe1f7070d43b8c51333de6412f1f3a05fde29570f65cebc88","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"my_tracked_payments","title":"My Tracked Payments","description":"List the payments the signed-in account has tracked, newest first.\n\nOne row per payment tracked in the last 90 days, at most 50 (`truncated`\nis true when there are more): uetr, reference, amount, currency, status,\nreason_code, sender_bic, receiver_bic, and last_tracked (ISO 8601, UTC).\nArchived payments are not listed.\n\nWHEN TO USE THIS:\n  - The user refers to a payment they tracked before (\"my payment\", \"my\n    last transfer\", \"the EUR one to Hamburg\") and gives no UETR or\n    reference. Call this BEFORE asking for the payment's details, and ask\n    only for what it does not settle.\n\nThe rows are the calling account's own: other users' and other\norganisations' searches are never included. status is the last recorded\ngpi status, not a live one; call track_payment for the current status.\n\nRequires a signed-in account: Ohm on ohmyfin.ai, or an API key that\nbelongs to one user (an organisation-wide key has no payments of its own).","inputSchema":{"type":"object","properties":{"api_key":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Your Ohmyfin API key (prod-...). Optional here: it can be sent instead as a KEY header or an Authorization: Bearer header. What the tool requires of the key is in its description."}},"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"eed99710f6e189a01c8e5e83bc7526345fba479f3f7e5cb1c1b3a7ff7440bde5","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"},{"serverName":"ai.ohmyfin/banking-intelligence","endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","name":"payment_cutoff_times","title":"Clearing System 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 computed for the current date. cutoff_utc/cutoff_local are the\nSTANDARD-TIME (winter) values; summer_offset holds the DST value. Quote the\ncutoff that `operative_cutoff_today` points at for TODAY's season — do not\ndefault to the winter figure when DST is currently in force (e.g. the T2\ncustomer cutoff is 15:00 UTC in summer, not the 16:00 UTC winter value).\n\nExamples:\n  payment_cutoff_times(system=\"T2\")\n  payment_cutoff_times(currency=\"EUR\")\n  payment_cutoff_times(currency=\"USD\")\n  payment_cutoff_times()","inputSchema":{"type":"object","properties":{"system":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Optional clearing system code or name, e.g. \"T2\", \"FEDWIRE\", \"CHAPS\". Case-insensitive; \"TARGET2\" resolves to T2, its name since March 2023. Omit it to list every system or to filter by currency."},"currency":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"Optional ISO 4217 code to filter by (e.g. \"USD\", \"EUR\")."}},"additionalProperties":false},"annotations":{"readOnlyHint":true,"openWorldHint":false},"definitionHash":"c3567383a4c18619ff1c7eadb4432e315b6604ba375362a2ed1c19c11947eb5c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T22:46:51.036Z","metadataTrust":"untrusted"}],"endpoints":[{"endpointFingerprint":"fc8da32c8040b1d8ebc505964aa322c906bf2c90a0263230dfb559698eabc339","protocol":"streamable-http","status":"indexed","toolCount":35,"observedAt":"2026-11-13T22:46:51.036Z"}],"authentication":"unknown"},"connectionConfigurations":{"status":"ready","authentication":"not embedded","clients":{"Claude Desktop":{"mcpServers":{"ai.ohmyfin/banking-intelligence":{"url":"https://mcp.ohmyfin.ai/mcp"}}},"Cursor":{"mcpServers":{"ai.ohmyfin/banking-intelligence":{"url":"https://mcp.ohmyfin.ai/mcp"}}},"VS Code":{"servers":{"ai.ohmyfin/banking-intelligence":{"type":"http","url":"https://mcp.ohmyfin.ai/mcp"}}}}},"resourceType":"mcp-server","callable":true,"runtime":{"callable":true,"protocols":["mcp"]},"interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://mcp.ohmyfin.ai/mcp"}],"profile":{"apiVersion":"1","schemaVersion":"1","id":"mcp-server:ai.ohmyfin%2Fbanking-intelligence","resourceType":"mcp-server","canonicalUrl":"https://www.agentsjunction.com/api/v1/servers/ai.ohmyfin%2Fbanking-intelligence","name":"ai.ohmyfin/banking-intelligence","description":"Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.","interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://mcp.ohmyfin.ai/mcp"}],"capabilities":[],"identity":{"source":"official-registry","websiteUrl":"https://mcp.ohmyfin.ai","repositoryUrl":null,"version":"1.0.0"},"verification":{"state":"official","confidence":100},"operations":{"resourceType":"mcp-server","name":"ai.ohmyfin/banking-intelligence","status":"online","lastCheckedAt":"2026-11-20T05:17:08.498Z","lastSuccessfulCheck":"2026-11-20T05:17:08.498Z","latencyMs":754,"consecutiveFailures":0,"isStale":false,"checks":{"endpointReachable":true,"protocolValid":true,"agentCardValid":null,"mcpHandshakeValid":true},"lastSeen":null,"lastSuccessfulInteraction":null,"lastHealthCheck":"2026-11-20T05:17:08.498Z","source":{"type":"health-check","url":null},"observedAt":"2026-11-20T05:17:08.498Z"},"security":null,"timestamps":{"createdAt":"2026-06-12T11:47:06.337Z","updatedAt":"2026-06-12T11:47:06.337Z","observedAt":"2026-11-20T05:17:08.498Z"},"compatibility":{"serverVersion":"1.0.0","protocolVersions":[{"protocol":"mcp","version":null}]}}}}