{"$schema":"https://verifymcp.io/schemas/trust-report.json","schemaVersion":1,"license":{"name":"CC BY-NC 4.0","url":"https://creativecommons.org/licenses/by-nc/4.0/"},"generatedAt":"2026-11-21T23:24:31.375Z","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp","markdownUrl":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp.md","server":{"slug":"ai-ohmyfin-sanctions","name":"ai.ohmyfin/sanctions","registryName":"ai.ohmyfin/sanctions","description":"Sanctions and export-control screening for AI agents: 320+ watchlists, transliteration, HS and ECCN.","registryStatus":"active","deletedAt":null,"statusMessage":null,"liveness":"live","publisher":{"class":"unknown","claimed":false}},"component":{"slug":"mcp","type":"remote","identifier":"https://mcp.ohmyfin.ai/mcp?from=registry-sanctions","withdrawn":false,"url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp","version":"1.0.0","transport":null,"scoredAt":"2026-11-21T04:15:56.748Z"},"score":{"total":67,"tier":"medium","status":"scored","weekDelta":4,"history":[{"date":"2026-11-21","total":67},{"date":"2026-11-20","total":66},{"date":"2026-11-19","total":66},{"date":"2026-11-18","total":65},{"date":"2026-11-17","total":65},{"date":"2026-11-16","total":64},{"date":"2026-11-15","total":64},{"date":"2026-11-14","total":63},{"date":"2026-11-13","total":63},{"date":"2026-11-12","total":62},{"date":"2026-11-11","total":62},{"date":"2026-11-10","total":62},{"date":"2026-11-09","total":61},{"date":"2026-11-08","total":61},{"date":"2026-11-07","total":60},{"date":"2026-11-06","total":60}]},"categories":[{"name":"Endpoint Security","score":63,"verdict":"fail","reasons":["The endpoint's TLS certificate is valid, in date, and uses a strong key.","Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.","HTTPS is enforced; there's no plaintext access path.","The HSTS (Strict-Transport-Security) header is present.","DNSSEC check failed: this domain isn't protected by DNSSEC."],"codes":[{"code":"tls.valid","args":{}},{"code":"auth.none_undeclared","args":{"undeclared_tools":"1"}},{"code":"https.enforced","args":{}},{"code":"headers.hsts_present","args":{}},{"code":"dnssec.absent","args":{}}]},{"name":"Transport & Reachability","score":100,"verdict":"pass","reasons":["Verified streamable-http transport via a live MCP handshake."],"codes":[{"code":"transport.verified","args":{"transport":"streamable-http"}}]},{"name":"Schema Quality & AI Usability","score":61,"verdict":"fail","reasons":["AI-judged instruction clarity (excellent).","Context-footprint check failed: tool/resource definitions use about 20778 tokens (~546/item across 38 items; 38 tools + 0 resources), over budget; trim descriptions and params.","Usage-examples check failed: none of the tools include examples."],"codes":[{"code":"schema.ai_quality","args":{"band":"excellent"}},{"code":"schema.footprint_heavy","args":{"avg":"546","items":"38","tools":"38","tokens":"20778","resources":"0"}},{"code":"schema.examples_absent","args":{}}]},{"name":"Stability & Change Management","score":50,"verdict":"partial","reasons":["Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses."],"codes":[{"code":"stability.building_history","args":{"days":"15"}}]},{"name":"Tool Coverage","score":100,"verdict":"pass","reasons":["100% of tools have a non-trivial description (not blank, and not just the tool's name).","100% of tool parameters carry a description.","Structured output schemas are declared (100% of tools); any adoption earns full credit."],"codes":[{"code":"toolquality.descriptions","args":{"pct":"100"}},{"code":"toolquality.param_docs","args":{"pct":"100"}},{"code":"toolquality.output_present","args":{"pct":"100"}}]},{"name":"Tool Safety","score":25,"verdict":"fail","reasons":["Injection-marker check failed: the description of tool \"iban_validate\" contains an instruction to conceal the call from the user, the text \"do not tell the user\", at byte 1444 of that field, plus 2 further marker(s) of the same kind.","0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; \"transfer_cost\" implies \"transfer\" and declares readOnlyHint instead, contradicting what its own name says it does.","An AI judge read all 39 captured unit(s) of tool text and found none that tries to manipulate the model reading it."],"codes":[{"code":"toolsafety.injection_markers","args":{"tool":"iban_validate","count":"3","field":"tool_description","quote":"do not tell the user","marker":"concealment","offset":"1444","markers":"concealment"}},{"code":"toolsafety.destructive_undeclared","args":{"pct":"0","tool":"transfer_cost","verb":"transfer","declared":"read_only","annotated":"0","destructive":"1"}},{"code":"toolsafety.manipulation_clean","args":{"units":"39","judged":"39"}}]},{"name":"Capabilities","score":100,"verdict":"pass","reasons":["Implements a current MCP spec version (2026-07-28)."],"codes":[{"code":"protocol.current","args":{"version":"2026-07-28"}}]}],"inconclusive":["Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe."],"malware":[],"components":[{"slug":"mcp","type":"remote","identifier":"https://mcp.ohmyfin.ai/mcp?from=registry-sanctions","withdrawn":false,"score":67,"current":true,"url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp","markdownUrl":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp.md"}],"facts":[{"label":"Endpoint","value":"https://mcp.ohmyfin.ai/mcp?from=registry-sanctions"},{"label":"Transports","value":"streamable-http"},{"label":"Auth","value":"none"},{"label":"Version","value":"1.0.0"}],"install":{"available":true,"bundleSha256":null},"tools":[{"name":"swift_lookup","title":"Bank and BIC Directory Search","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 CORRESPONDENT CHAIN.\nRead `settlement_instructions` on each bank: `on_file: true` with a\n`currencies_on_file` count means we hold that BIC8's actual correspondent\nBIC, nostro account number and national clearing ID, and `read_with` is the\nexact ssi_lookup call that returns them. `on_file: false` means we hold none\nin any currency — a gap in our data, not a finding about the bank. A null is\n\"not established yet\" and is neither. This is the answer to \"which\nintermediary bank do I put on the instruction?\", and it is a fact we either\nhave or do not have — never one to recall from training data.\n\nA BIC IDENTIFIES AN OFFICE, NOT A BRAND, AND THE DIFFERENCE IS PRICED.\nA name search returns ONE representative office per bank, elected by BIC\nconvention rather than by relevance to the payment, and `office_note` says\nso whenever the bank holds more than one. Published tariffs, correspondent\nchains and settlement instructions are filed per BIC, so the choice changes\nthe answer: transfer_cost(\"COBADEFF\") returns Commerzbank's published 0.15%\nsending fee and transfer_cost(\"COBADEBB\") refuses for want of a filed\ntariff, and both of those are Commerzbank AG in Germany. So:\n  - If the user named a CITY, put it in the query — \"Commerzbank Frankfurt\"\n    resolves to the Frankfurt office, and the plain name cannot.\n  - If they did not, ask which BIC is on their statement or payment\n    instruction before…","inputs":[{"name":"country","type":null,"required":false,"description":"Optional country filter: an ISO 3166-1 alpha-2 code (\"ID\", \"DE\") or a full English name (\"Indonesia\", \"Germany\"). Names are resolved automatically."},{"name":"details_section","type":null,"required":false,"description":"Optional name of one research-profile section to return in full, as listed in a bank's `details_left_out` (e.g. \"official_documents\" or a details_raw section name). Omit it for the normal answer."},{"name":"details_section_page","type":"integer","required":false,"description":"Optional page of the details_section, from 1 (default). Used only when an answer says that section comes in pages and names the page that holds the rest."},{"name":"limit","type":"integer","required":false,"description":"Maximum number of banks to return, 1-100 (default 20). Values outside the range are clamped."},{"name":"page","type":"integer","required":false,"description":"Optional page of the matched banks, from 1 (default). Used only when an answer says banks were left out to fit and names the page that holds them."},{"name":"query","type":"string","required":true,"description":"Bank name, BIC, or bank name plus city (\"Commerzbank Frankfurt\"). A BIC may be 8 or 11 characters; an 11-character BIC ending in XXX is searched as its 8-character form. The 12-character address in a…"}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":951},{"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\" recommend…","inputs":[{"name":"iban","type":"string","required":true,"description":"The IBAN to check, e.g. \"DE89370400440532013000\". Spaces and hyphens are ignored and letters are upper-cased."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":551},{"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","inputs":[{"name":"country_code","type":"string","required":true,"description":"ISO 3166-1 alpha-2 country code, e.g. \"DE\", \"US\", \"KZ\"."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":406},{"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)","inputs":[{"name":"code_type","type":"string","required":true,"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."},{"name":"country_code","type":"string","required":true,"description":"ISO 3166-1 alpha-2 country code, e.g. \"KZ\", \"AE\"."},{"name":"page","type":"integer","required":false,"description":"Optional page of the codes, from 1 (default). Used only when an answer says codes were left out to fit and names the page that holds them."},{"name":"search","type":null,"required":false,"description":"Optional keyword filter (e.g. \"transport\", \"trade\", \"insurance\"). Omit it to list every code in the table, which is a large response."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":273},{"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\")","inputs":[{"name":"base","type":"string","required":true,"description":"Base currency, ISO 4217 (e.g. \"USD\"). The rate is quoted as units of target per 1 base."},{"name":"target","type":"string","required":true,"description":"Target currency, ISO 4217 (e.g. \"VND\")."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":403},{"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)","inputs":[{"name":"base","type":"string","required":true,"description":"Base currency, ISO 4217 (e.g. \"EUR\"). Rates are quoted as units of target per 1 base."},{"name":"days","type":"integer","required":false,"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."},{"name":"target","type":"string","required":true,"description":"Target currency, ISO 4217 (e.g. \"USD\")."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":531},{"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_statu…","inputs":[{"name":"code","type":null,"required":false,"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."}],"outputs":[{"name":"result","type":null,"required":true,"description":null}],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":603},{"name":"swift_message_reference","title":"Payment Message Reference (MT and ISO 20022)","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 recovery for customers who only have\na reference number.\n\nExamples:\n  swift_message_reference(\"MT103\")\n  swift_message_reference(\"pacs.008\")\n  swift_message_reference()","inputs":[{"name":"message_type","type":null,"required":false,"description":"Optional message type, e.g. \"MT103\", \"pacs.008\", \"MT940\". Case-insensitive. Omit it to list every type."}],"outputs":[{"name":"result","type":null,"required":true,"description":null}],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":255},{"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()","inputs":[{"name":"currency","type":null,"required":false,"description":"Optional ISO 4217 code to filter by (e.g. \"USD\", \"EUR\")."},{"name":"page","type":"integer","required":false,"description":"Optional page of the systems, from 1 (default). Used only when an answer says systems were left out to fit and names the page that holds them."},{"name":"system","type":null,"required":false,"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."}],"outputs":[{"name":"result","type":null,"required":true,"description":null}],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":432},{"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 forwa…","inputs":[{"name":"base","type":"string","required":true,"description":"Base currency, ISO 4217 (e.g. \"EUR\")."},{"name":"horizon_days","type":null,"required":false,"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."},{"name":"target","type":"string","required":true,"description":"Target currency, ISO 4217 (e.g. \"TRY\")."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":671},{"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()","inputs":[{"name":"currency","type":null,"required":false,"description":"Optional ISO 4217 code (e.g. \"EUR\", \"JPY\"). Omit it to get every session and overlap."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":353},{"name":"payment_method_compare","title":"Payment Method Comparison","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\nExamples:\n  payment_method_compare(\"DE\", \"FR\")   # Both SEPA — will recommend SCT\n  payment_method_compare(\"US\", \"TR\")   # Non-SEPA — will recommend SWIFT\n  payment_method_compare(\"GB\", \"GB\")   # Domestic — will show CHAPS/FPS\n  payment_method_compare(\"US\", \"VN\")   # Fee investigation — why beneficiary got less","inputs":[{"name":"dest_country","type":"string","required":true,"description":"Receiving country, ISO 3166-1 alpha-2 country code (e.g. \"GB\", \"TR\")."},{"name":"source_country","type":"string","required":true,"description":"Sending country, ISO 3166-1 alpha-2 country code (e.g. \"DE\", \"US\")."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":240},{"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)","inputs":[{"name":"country_code","type":"string","required":true,"description":"ISO 3166-1 alpha-2 country code, e.g. \"US\", \"DE\", \"GB\"."},{"name":"year","type":null,"required":false,"description":"Calendar year, 2020-2030 (default: the current year). Values outside the range are clamped."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":430},{"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\")","inputs":[{"name":"check_date","type":"string","required":true,"description":"The date to check, YYYY-MM-DD (ISO 8601)."},{"name":"country_code","type":"string","required":true,"description":"ISO 3166-1 alpha-2 country code, e.g. \"US\", \"DE\"."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":258},{"name":"value_date","title":"Value Date Calculator","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\nExamples:\n  value_date(\"US\", \"DE\")\n  value_date(\"US\", \"DE\", \"fx_spot\", \"USD\", \"EUR\")\n  value_date(\"DE\", \"FR\", \"sepa\")\n  value_date(\"US\", \"US\", \"wire\", from_date=\"2026-07-03\")","inputs":[{"name":"base_currency","type":null,"required":false,"description":"Base currency for FX, ISO 4217 (e.g. \"USD\"). Required when settlement_type is \"fx_spot\"."},{"name":"dest_country","type":"string","required":true,"description":"Receiver's country, ISO 3166-1 alpha-2 country code (e.g. \"DE\")."},{"name":"from_date","type":null,"required":false,"description":"Start date, YYYY-MM-DD (default: today). You do not know today's date: omit this argument unless the user named a specific send date. If the user's date is relative (\"the 20th\", \"next Friday\", \"month…"},{"name":"settlement_type","type":"string","required":false,"description":"One of \"wire\" (T+0 domestic / T+1 international, the default), \"fx_spot\" (T+1 or T+2 depending on the pair), \"sepa\" (D+1), \"sepa_instant\" (T+0)."},{"name":"source_country","type":"string","required":true,"description":"Sender's country, ISO 3166-1 alpha-2 country code (e.g. \"US\")."},{"name":"target_currency","type":null,"required":false,"description":"Target currency for FX, ISO 4217 (e.g. \"EUR\"). Required when settlement_type is \"fx_spot\"."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":406},{"name":"settlement_eta","title":"Payment Arrival Estimate (Beta)","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 arrival\n  dates, sample size, confidence, competing non-arrival risk, delay-risk\n  factors, and (where validated) the most likely correspondent route.\n- Reverse: pass arrive_by_date (YYYY-MM-DD) — returns the latest send\n  date such that arrival by that day is likely (\"send by Thursday to\n  land by month-end\").\n\nINPUT DISCIPLINE (important):\n- Mid-flight payment: pass ONLY the uetr (from TrackingContext or\n  track_payment). The server resolves the current status, currency and\n  elapsed time deterministically from the tracking record. NEVER compute\n  elapsed_business_days yourself.\n- Pre-trade question (\"how long will a USD wire from X to Y take?\"):\n  pass currency + sender_bic/receiver_bic (8 or 11 chars, or bank names).\n  current_status / elapsed_business_days are for this path only.\n\nReading the answer honestly (relay these to the user):\n- basis.n is the sample size and confidence reflects it; when confidence\n  is \"low\", present the window as a rough range, never a promise.\n- basis.level says whose payments basis.n counts: `corridor` this bank\n  pair, `sender_ccy` / `receiver_ccy` this sending / receiving bank in\n  this currency, `currency` every bank in this currency, `global` every\n  tracked payment in every currency. basis.currency is the PAYMENT's\n  currency, not the pool's: a global answer is never \"<currency>\n  payments\". basis.pool says it in words where it matters.\n- basis…","inputs":[{"name":"amount","type":null,"required":false,"description":"Payment amount; it improves the delay-risk assessment. A plain number is fine: 50000 and \"50,000.00\" are both accepted."},{"name":"api_key","type":null,"required":false,"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."},{"name":"arrive_by_date","type":null,"required":false,"description":"YYYY-MM-DD; switches to reverse send-by mode. You do not know today's date: a deadline stated as \"the 20th\" or \"by month-end\" must be resolved against the `today` block returned by bank_holidays / va…"},{"name":"currency","type":null,"required":false,"description":"3-letter ISO 4217 currency. Needed without a uetr. With a uetr, leave it out: the tracking record's currency is used, and a currency you pass replaces it. Pass it with a uetr only when the answer's u…"},{"name":"current_status","type":null,"required":false,"description":"Status code such as ACSP, for the path without a uetr only."},{"name":"elapsed_business_days","type":null,"required":false,"description":"Business days already in flight, for the path without a uetr only."},{"name":"intermediary_bic","type":null,"required":false,"description":"Optional BIC of a known intermediary bank."},{"name":"receiver_bic","type":null,"required":false,"description":"Receiving bank's BIC (8 or 11 characters) or bank name, for the pre-trade path."},{"name":"receiver_country","type":null,"required":false,"description":"Optional ISO 3166-1 alpha-2 country code of the receiving bank."},{"name":"sender_bic","type":null,"required":false,"description":"Sending bank's BIC (8 or 11 characters) or bank name, for the pre-trade path."},{"name":"sender_country","type":null,"required":false,"description":"Optional ISO 3166-1 alpha-2 country code of the sending bank."},{"name":"uetr","type":null,"required":false,"description":"UETR of a tracked payment, UUID v4 (e.g. \"eb6305c8-0710-4e41-84ad-f58db3083e82\"). Preferred for a payment already in flight; see INPUT DISCIPLINE in the description."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":1242},{"name":"transfer_cost","title":"Transfer Fee Estimate (Beta)","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\n  hold no published tariff rule for the sending bank, in which case there\n  is deliberately no total and no \"recipient receives\" figure. Say we do\n  not know what that bank charges. Do NOT add up the parts yourself and\n  present a total: treating the unknown fee as zero is the exact defect\n  this tool was built to remove.\n- The correspondent fee is a RANGE (`p50` typical, `p90` high case), not a\n  point. The spread is real: SWIFT tracking never reveals whether a\n  payment was sent OUR, SHA or BEN, so a single cohort mixes all three.\n- THREE FEES, THREE DIFFERENT PAYERS, AND THEY ARE NOT INTERCHANGEABLE.\n  `sending_fee` is billed to the SENDER by their own bank.\n  `correspondent_fee` comes out of the payment in transit, so the\n  BENEFICIARY bears it. `beneficiary_fee` is what the RECEIVING bank\n  charges its own customer to credit the payment, so the beneficiary bears\n  that too - and it is frequently the largest of the three (measured\n  2026-08-22 on one live corridor: 35.26 USD of sender-side cost against a\n  245.68 USD beneficiary bank fee). Never quote one of them as \"the cost\",\n  and never call the beneficiary bank's fee a correspondent charge.\n  `total` is the sending fee plus the transit deduction; `total_both_sides`\n  adds the beneficiary bank's fee and is the all-in figure.\n- WHERE EACH NUMBER COMES FROM. The correspondent fee is OBSERVED, from\n  payments we have trac…","inputs":[{"name":"amount","type":"number","required":true,"description":"Transfer amount in `currency`, greater than zero."},{"name":"api_key","type":null,"required":false,"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."},{"name":"bank_swift","type":"string","required":true,"description":"Sending bank's BIC, 8 or 11 characters."},{"name":"beneficiary_bic","type":null,"required":false,"description":"Receiving bank's BIC (8 or 11 characters); needed for a total."},{"name":"beneficiary_segment","type":null,"required":false,"description":"Who is being PAID: individual | business | financial_institution. Omitted, it mirrors customer_segment."},{"name":"channel","type":null,"required":false,"description":"Sending channel: online | branch | mobile_app | any."},{"name":"charge_type","type":"string","required":false,"description":"SHA (default), OUR or BEN. Ask the user rather than guessing."},{"name":"currency","type":"string","required":true,"description":"3-letter ISO 4217 transfer currency."},{"name":"customer_segment","type":null,"required":false,"description":"Who is SENDING: individual | business | financial_institution."},{"name":"customer_sub_segment","type":null,"required":false,"description":"The sender's tier at their bank: standard | premium | private_banking | vip."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":2100},{"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)","inputs":[{"name":"accept_terms","type":"boolean","required":true,"description":"Must be true. Confirms acceptance of the Ohmyfin Terms & Conditions at https://ohmyfin.ai/terms."},{"name":"email","type":"string","required":true,"description":"Your email address. The verification code is sent to it."},{"name":"organization_name","type":"string","required":true,"description":"Your company or project name."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":209},{"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\")","inputs":[{"name":"code","type":"string","required":true,"description":"The 6-digit verification code from that email."},{"name":"email","type":"string","required":true,"description":"The email address you registered with."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":111},{"name":"sanctions_screen","title":"Sanctions and Watchlist Screening","description":"Screen a name against global sanctions and watchlists.\n\nA crypto wallet address is checked as an address, never as a name.\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 does not return and understates the coverage.\n\nFor a company or an individual the screen covers every list, including\nadverse media, PEP and debarment registers. For a BANK or other financial\ninstitution it returns sanctions DESIGNATIONS only: a warning-list entry\nnaming a bank is usually a clone-firm alert about fraudsters impersonating\nit, and the feed carries nothing that tells the two apart.\n\nWhen the name resolves in our bank directory, each designation is also\ncross-referenced against that institution's record (country, entity type,\nand the name or ALIAS that earned the fuzzy score) and contradicted rows are\nremoved. ALWAYS read the `verification` block, which is on every response:\n`applied: false` means nothing was cross-referenced and the rows are raw\nfeed output — either the name is not in our bank directory, or the subject\nis a company or individual, which has no directory record to check against.\nNever report an `applied: false` result as verified, and never report an\nempty one as verified-clear. Screening a bank by BIC, or calling\nswift_lookup, gets a verified answer.\n\nA row surviving that cross-reference is NOT the same as a row the\ncross-reference supported. Each verified row carries `adjudication`:\n`corroborated` means the check backed it and it is a designation against\nthis institution; `not_corroborated` means it survived the false-positive\nfloor but nothing tied it to this institu…","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"name","type":"string","required":true,"description":"The person or entity name to screen."},{"name":"subject_type","type":"string","required":false,"description":"What is being screened: \"bank\" for a financial institution, \"party\" for a company or individual, or \"auto\" (default). A name the bank directory resolves is treated as a financial institution whatever…"},{"name":"threshold","type":"integer","required":false,"description":"Minimum match score, 0-100 (default 85). Values above 95 are treated as 95."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":1530},{"name":"crypto_wallet_screen","title":"Crypto Wallet Check","description":"Check a crypto wallet address: who owns it, which lists name it, and where its funds came from.\n\nA crypto wallet address is checked as an address, never as a name. Pass\nthe address as written; the chain is detected when omitted.\n\nThe answer is the verdict block: `state`, `tier` (block, high, review,\nmonitor or clear), `score` (0 to 10), `headline`, `main_reason` (a\nsentence and its data; `data.kind` is `state_order` when an Israeli\nNBCTF seizure or forfeiture order names the address, which is not a\nsanctions listing), `owner` with its `evidence` (official_list,\nown_publication or bought_label), `list_hits`, `checked` (the chains,\nassets, hops and lists covered, and when), `recommended_action`,\n`check_id`, `report_url` (the wallet page) and `report_price` (how opening\nthe full report would be paid).\n\nEach `list_hits` item and `owner` carry `listed_at` (the date the list\nnames the entry since), `list_ref` (the list's own id of the entry, e.g.\nthe OFAC uid) and `entry_url` (that entry's official page, e.g. OFAC's\nSanctions List Search). When `entry_url` is null, `source_url` is the\nlist's own file or notice: say so, never call it the entry's page.\n\n`state`:\n- `finished`: the check ran to the end; `checked` says what it covered.\n- `pending`: the check is still running (`running: true`). It is not\n  finished; collect it with crypto_wallet_result and the `check_id`.\n- `incomplete`: not finished. Report it as not finished, never as\n  nothing found.\n- `unavailable`: no answer could be obtained just now.\n- `no_activity`: no transactions were found for the address on the\n  chains checked; it may be mistyped, on another chain, or never used.\n- `lists_only`: the chain is covered by sanctions lists only, with no\n  tracing of funds.\n- `invalid`: the address fails its checksum, so it was not checked.\n\nSay what was found and what `checked` covered. The full report is\ncrypto_wallet_report. `paths_found` is how many paths of funds it holds:\nwith 0 it states what was read (`checked.r…","inputs":[{"name":"address","type":"string","required":true,"description":"The crypto wallet address to check, exactly as written (for example a TRON address starting with T, an Ethereum address starting with 0x, or a Bitcoin address)."},{"name":"api_key","type":null,"required":false,"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."},{"name":"chain","type":null,"required":false,"description":"Optional chain, e.g. \"tron\", \"ethereum\", \"bitcoin\", \"litecoin\". Detected from the address when omitted."},{"name":"customer_ref","type":null,"required":false,"description":"Optional reference of your own (a customer or case id), kept with the check and returned with it."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":734},{"name":"crypto_wallet_result","title":"Crypto Wallet Check Result","description":"Read a crypto wallet check again, or collect one that was still running.\n\nA crypto wallet address is checked as an address, never as a name. This\nreads the check crypto_wallet_screen started, by its `check_id`, and\nanswers the same verdict block. Reading it again starts nothing new.\n\n`pending` (`running: true`) means it is still running: ask again in a\nminute. `pending` and `incomplete` are not finished, never nothing\nfound. The meaning of every field is in crypto_wallet_screen.\n\nExamples:\n  crypto_wallet_result(\"01JD8Q7T6XK3M5N9P2R4S6V8W0\")","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"check_id","type":"string","required":true,"description":"The check_id returned by crypto_wallet_screen."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":214},{"name":"crypto_wallet_report","title":"Crypto Wallet Full Report","description":"Open the full report of a crypto wallet check: why it got its verdict, and the paths of funds behind it.\n\nA crypto wallet address is checked as an address, never as a name. The\nreport belongs to a check crypto_wallet_screen made (`check_id`) and\nanswers `report` (`why`, `paths`, `decision`, `score_lines`, `read`,\n`paths_note`), `pdf_url` and the `wallet` verdict block.\n\n`report.paths` is empty when nothing that was read came from or went to\na listed or risky source within 2 hops; `report.paths_note` then says so\nwith what was read (`report.read`: transfers, period, USD in and out).\nAn empty `paths` means \"no transfers\" only when `report.read.transfers`\nis 0.\n\nOpening a report is paid from the account's plan or its credits. When\nopening would spend a credit and `confirm` is not true, nothing is\nopened or spent: the answer carries `needs_confirmation: true`, the\n`price` and its `price_line`. Tell the user the price, and call again\nwith confirm=true only once they agree. A report already opened is read\nagain at no charge.\n\nExamples:\n  crypto_wallet_report(\"01JD8Q7T6XK3M5N9P2R4S6V8W0\")\n  crypto_wallet_report(\"01JD8Q7T6XK3M5N9P2R4S6V8W0\", confirm=True)","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"check_id","type":"string","required":true,"description":"The check_id returned by crypto_wallet_screen."},{"name":"confirm","type":"boolean","required":false,"description":"Set true only after the user has agreed to the price this tool stated for opening the report. Default false: nothing is spent."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":423},{"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","inputs":[{"name":"eccn","type":"string","required":true,"description":"Export Control Classification Number, e.g. \"5A001\", \"3A001\", \"1C351\". Case-insensitive."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":176},{"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?'","inputs":[{"name":"country_code","type":"string","required":true,"description":"ISO 3166-1 alpha-2 country code, e.g. \"RU\", \"CN\", \"DE\"."},{"name":"jurisdiction","type":"string","required":false,"description":"Optional filter by jurisdiction, e.g. \"US\", \"EU\". Omit it for every jurisdiction."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":304},{"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?'","inputs":[{"name":"destination_country","type":"string","required":true,"description":"Destination country, ISO 3166-1 alpha-2 country code (e.g. \"RU\", \"CN\")."},{"name":"eccn","type":"string","required":false,"description":"Export Control Classification Number, e.g. \"3A001\". Give at least one of eccn, hs_code, goods_description."},{"name":"goods_description","type":"string","required":false,"description":"Free-text goods description, English or Russian. A fallback for when no eccn or hs_code is known; see the description."},{"name":"hs_code","type":"string","required":false,"description":"Harmonized System code, 4-8 digits (e.g. \"854231\"). Give at least one of eccn, hs_code, goods_description."},{"name":"jurisdiction","type":"string","required":false,"description":"\"US\" (default), \"EU\", \"UK\", \"JP\", \"ITAR\", or \"ALL\"."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":599},{"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?'","inputs":[{"name":"hs_code","type":"string","required":true,"description":"HS code, 4-6 digits (e.g. \"854231\", \"8411\"). Dots and spaces are fine."},{"name":"jurisdiction","type":"string","required":false,"description":"Optional filter: \"US\", \"EU\", \"UK\" or \"JP\"."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":301},{"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?'","inputs":[{"name":"description","type":"string","required":true,"description":"Goods description, at least 2 characters (e.g. \"uranium centrifuge\", \"центрифуга для урана\")."},{"name":"hs_code","type":"string","required":false,"description":"Optional known HS code (4 or 6 digits) for a direct lookup."},{"name":"language","type":"string","required":false,"description":"Optional hint: \"en\" or \"ru\" (auto-detected if omitted)."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":401},{"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?'","inputs":[{"name":"agency","type":"string","required":false,"description":"Optional: \"BIS\" (Bureau of Industry and Security) or \"OFAC\" (Office of Foreign Assets Control). Omit it for both."},{"name":"category","type":"string","required":false,"description":"Optional: \"entity_list\", \"rule_change\", \"country_policy\" or \"sanctions\". Omit it for every category."},{"name":"days","type":"integer","required":false,"description":"Days to look back, 1-365 (default 30). A value outside the range is refused."},{"name":"limit","type":"integer","required":false,"description":"Maximum number of changes to return (default 50)."},{"name":"severity","type":"string","required":false,"description":"Optional: \"critical\", \"high\", \"medium\" or \"low\". Omit it for every level."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":248},{"name":"track_payment","title":"Track a Cross-Border Payment","description":"Track a SWIFT payment by UETR or reference number.\n\nBasic SWIFT payment tracking enriched by data from certain banks in\nthe correspondent chain. Returns the overall payment status and,\nwhen available, per-bank details showing which banks reported\ninformation about this payment.\n\nIMPORTANT — every trace needs four things:\n  amount, currency, date, and an identifier (uetr, or reference when\n  there is no UETR). amount, currency and date are required\n  parameters, on the UETR path too: there is no UETR-only lookup, so\n  never tell the user the UETR alone is enough to run one. Ask for\n  whatever is missing before calling, and never guess a value.\n\nIMPORTANT — UETR vs Reference:\n  The UETR (Unique End-to-End Transaction Reference) is a UUID\n  assigned to every SWIFT gpi payment. Tracking by UETR succeeds\n  ~80% of the time. Tracking by reference number alone succeeds\n  less than 1% of the time because most banks only index by UETR.\n\n  → Always provide the UETR if available.\n  → The reference number is Field 20 of the MT103 (or the\n    equivalent <InstrId>/<EndToEndId> in pacs.008). It is the\n    sender's transaction reference. Still valuable — provide it\n    alongside the UETR when you have both.\n\nWHEN THE USER HAS ONLY A REFERENCE AND NO UETR\n(\"how do I find / trace my payment?\", \"I have a reference number\nbut no UETR, where is it?\"):\n  This is exactly the scenario this tool can attempt — do NOT answer\n  from general knowledge. A reference-based trace cannot be run from\n  the reference alone; you MUST first collect three things from the user:\n    1. amount   — the exact amount as sent\n    2. currency — ISO 4217 (e.g. \"USD\")\n    3. date     — the send date (within the last 90 days)\n  Then call track_payment(reference=..., amount=..., currency=...,\n  date=...). State the expectation up front: reference-only tracing\n  succeeds less than 1% of the time.\n  In parallel, tell the user how to recover the UETR for a reliable\n  (~80%) trace: ask the SENDING bank for the MT103 co…","inputs":[{"name":"amount","type":"number","required":true,"description":"Transaction amount as sent (e.g. 15000.00). Must match the original payment amount: even a small difference may stop tracking from finding the payment, so ask the user for the exact figure rather tha…"},{"name":"api_key","type":null,"required":false,"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."},{"name":"currency","type":"string","required":true,"description":"ISO 4217 code of the currency the payment was SENT in (e.g. \"USD\", \"EUR\", \"GBP\"). Ask if you do not know it; do not assume the sender's or the beneficiary's home currency."},{"name":"date","type":"string","required":true,"description":"Transaction date. Preferred format YYYY-MM-DD (ISO 8601); DD.MM.YYYY and DD-MM-YYYY are also accepted, slash-separated dates are not. Must be within the last 90 days."},{"name":"reference","type":null,"required":false,"description":"Sender's bank reference number (MT103 field 20 / pacs.008 InstrId). Useful beside the UETR for cross-referencing, but alone it rarely produces results. Required only if uetr is not provided."},{"name":"uetr","type":null,"required":false,"description":"UETR, UUID v4 (e.g. \"eb6305c8-0710-4e41-84ad-f58db3083e82\"). Strongly recommended: tracking without a UETR rarely returns results. It is the Unique End-to-End Transaction Reference every gpi payment…"}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":1595},{"name":"tracking_history","title":"Payment Tracking History","description":"Show how a SWIFT payment's tracking results changed over time.\n\nReturns the DISTINCT tracking results recorded for a payment (by UETR or\nreference), deduplicated so ten identical re-tracks collapse to one entry\nwhile any change — a new last-update, a status change, or new bank data —\nappears as its own entry. Each entry includes what was ENTERED when the\nsearch was run (amount, currency, date) alongside the banks that reported\ndata and their confirmed amount / value date.\n\nWHEN TO USE THIS:\n  - The user says the page shows different data than you see, or asks why a\n    bank line (e.g. JP Morgan) \"disappeared\" or a value date differs.\n  - You need to reconcile an amount or date discrepancy. JP Morgan returns\n    its line only when the entered date and amount are close to its own\n    record (seen: value dates up to 3 days apart, amounts mostly within 1%),\n    so a search run with a wrong date or amount can silently drop its line.\n    When it does answer, `amount_exact_match` is false if its value date OR\n    its amount differs from what was entered, despite the name, and\n    `amount_exact_match_detail` names which. Comparing entries here — same\n    UETR, different entered dates or amounts, different bank data — is how\n    you spot which entry was the problem.\n  - Before concluding \"the record was consolidated\" or \"the bank stopped\n    reporting\", check the history: the earlier result you're being asked\n    about is usually still here, under a different entered amount.\n\nEach bank entry's `source` names the tracking SOURCE that reported it (e.g.\n\"Standard Chartered\"), not the bank at a step of the payment; track_payment\nnames the same data by the bank at each step, so the two names differ.\n\nOnly results for the current user (plus system tracks with no owner) are\nreturned; other users' searches of the same UETR are never shown.\n\nRequires an API key with an active FI subscription.","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"reference","type":null,"required":false,"description":"Sender's reference (MT103 field 20), used when there is no UETR."},{"name":"uetr","type":null,"required":false,"description":"UETR (UUID v4) of the payment. Strongly preferred."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":533},{"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).","inputs":[{"name":"api_key","type":null,"required":false,"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."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":287},{"name":"ssi_lookup","title":"Settlement Instructions (SSI) Lookup","description":"Look up correspondent banking / settlement instructions (SSI) for a bank.\n\nReturns the correspondent banks (nostro accounts) that a given bank\nuses to settle payments in a specific currency, including account\nnumbers (when available) and intermediary chains. Essential for\npayment routing and pre-validation.\n\nEach correspondent is annotated with a clearing_note indicating\nwhether it can clear the currency directly (located in a home\ncountry for that currency) or needs its own correspondent.\nIf the note suggests a further lookup, call ssi_lookup on the\ncorrespondent's SWIFT code to find the full clearing chain.\n\nIMPORTANT — known data gaps to respect:\n- Account numbers may be empty for some/all correspondents. The\n  response surfaces an `account_availability_note` in those cases.\n  Do NOT invent account numbers. Use swift_lookup() to find the\n  bank's own published correspondent banks page when accounts\n  are missing.\n- WHICH CORRESPONDENT: read `correspondent_selection`, not the array order.\n  It gives the COMPLETE set of BICs for each flow (customer MT103 vs\n  interbank MT202) and for whether the correspondent clears the currency\n  itself, each with a count. The correspondents are returned in STORAGE\n  order, which is not a ranking. Naming a subset (\"principally X and Y\",\n  \"route via X\") invents a preference this feed does not hold. Name every\n  BIC in the matching set, or give its count: which one is used is the\n  SENDING bank's choice among the ones it can already reach, not the\n  beneficiary bank's, and not ours to guess from bank size or reputation.\n  `is_preferred` is `null` on almost every row because the flag is\n  genuinely unrecorded (11 rows in the entire corpus carry it); where it IS\n  set, `correspondent_selection.bank_flagged_preference` names it and you\n  should lead with that.\n- `intermediaries` is `null` — not `[]` — when this correspondent's onward\n  chain is not recorded, which is 98% of rows. `null` means NOT ESTABLISHED,\n  never zero hops: do no…","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"currency","type":"string","required":true,"description":"ISO 4217 currency code (e.g. \"USD\", \"EUR\", \"GBP\")."},{"name":"swift","type":"string","required":true,"description":"BIC of the bank, 8 or 11 characters (e.g. \"DEUTDEFF\")."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":1225},{"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\")","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"correspondent_swift","type":"string","required":true,"description":"BIC of the correspondent bank, 8 or 11 characters (e.g. \"IRVTUS3N\")."},{"name":"country","type":"string","required":true,"description":"ISO 3166-1 alpha-2 country code of the client banks (e.g. \"AE\")."},{"name":"currency","type":"string","required":true,"description":"ISO 4217 currency code (e.g. \"USD\")."},{"name":"name_prefix","type":null,"required":false,"description":"Optional prefix on the client bank's name (e.g. \"AL\")."},{"name":"page","type":"integer","required":false,"description":"Result page, 1-4 (default 1). Any other value is refused."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":364},{"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\"])","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"include_inactive_roles","type":"boolean","required":false,"description":"Include resigned and ceased roles (default true)."},{"name":"include_sanctions_check","type":"boolean","required":false,"description":"Screen every person and company found against sanctions lists (default true)."},{"name":"jurisdictions","type":"array","required":true,"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."},{"name":"name","type":"string","required":true,"description":"Person name to search for."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":451},{"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)","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"include_officers","type":"boolean","required":false,"description":"Include directors and officers (default true)."},{"name":"include_only_active","type":"boolean","required":false,"description":"Return active companies only (default false)."},{"name":"include_sanctions_check","type":"boolean","required":false,"description":"Screen every company and person found against sanctions lists (default true)."},{"name":"include_shareholders","type":"boolean","required":false,"description":"Include PSC / beneficial owners (default true)."},{"name":"jurisdictions","type":"array","required":true,"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."},{"name":"name","type":"string","required":true,"description":"Company name to search for."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":542},{"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\")","inputs":[{"name":"api_key","type":null,"required":false,"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."},{"name":"search_id","type":"string","required":true,"description":"The search_id returned by a previous company_search_person or company_search_company call."}],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":135},{"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()","inputs":[],"outputs":[],"hasOutputSchema":true,"hasExamples":false,"tokenEstimate":142}],"toolsTruncatedAtCapture":false,"diagnostics":{"capturedAt":"2026-11-21T04:15:56.000Z","track":"remote","endpoint":"https://mcp.ohmyfin.ai/mcp?from=registry-sanctions","declaredUrl":null,"truncated":false,"tls":{"outcome":"valid","label":"Valid","version":"TLS 1.3","cipherSuite":"TLS_AES_128_GCM_SHA256","chainError":null,"certificates":[{"subject":"CN=mcp.ohmyfin.ai","issuer":"CN=YE2,O=Let's Encrypt,C=US","notBefore":"2026-11-07T14:42:10Z","notAfter":"2027-02-05T14:42:09Z","keyType":"ECDSA","keyBits":256,"isCa":false},{"subject":"CN=YE2,O=Let's Encrypt,C=US","issuer":"CN=Root YE,O=ISRG,C=US","notBefore":"2025-09-03T00:00:00Z","notAfter":"2028-09-02T23:59:59Z","keyType":"ECDSA","keyBits":384,"isCa":true},{"subject":"CN=Root YE,O=ISRG,C=US","issuer":"CN=ISRG Root X2,O=Internet Security Research Group,C=US","notBefore":"2026-05-13T00:00:00Z","notAfter":"2032-09-02T23:59:59Z","keyType":"ECDSA","keyBits":384,"isCa":true},{"subject":"CN=ISRG Root X2,O=Internet Security Research Group,C=US","issuer":"CN=ISRG Root X1,O=Internet Security Research Group,C=US","notBefore":"2026-05-13T00:00:00Z","notAfter":"2032-09-02T23:59:59Z","keyType":"ECDSA","keyBits":384,"isCa":true}]},"dnssec":{"result":"insecure","label":"Not signed","name":"mcp.ohmyfin.ai.","steps":[{"zone":".","outcome":"verified","label":"Verified"},{"zone":"ai.","outcome":"verified","label":"Verified"},{"zone":"ohmyfin.ai.","outcome":"insecure_proven","label":"Unsigned (proven)"}]},"auth":{"outcome":"none","label":"No authorisation required","gate":null,"gateLabel":null,"status":200,"authorizationServers":[]},"httpsRedirect":{"outcome":"https_enforced","label":"HTTPS enforced","status":301},"transports":[{"transport":"streamable-http","outcome":"verified","label":"Verified","status":200,"followed":false}],"provenance":null,"installScripts":[],"installScriptsTotal":null,"vulnerabilities":[],"vulnerabilitiesTotal":null,"dependencies":null},"mismatches":[],"changelog":{"trackingSince":"2026-11-06","recent":[{"id":"chg_01a1fc51-6b60-7c6b-ab78-71703ec4777a","kind":"tool.description_changed","summary":"Tool “crypto_wallet_screen” rewrote its description, which is the text the model reads","materiality":"security","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-21","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1fc51-6b60-7c6b-ab78-71703ec4777a"},{"id":"chg_01a1fc51-6b61-7c2d-a996-440322a2b2b6","kind":"param.added_optional","summary":"“swift_lookup” added an optional parameter “details_section_page”","materiality":"cosmetic","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-21","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1fc51-6b61-7c2d-a996-440322a2b2b6"},{"id":"chg_01a1fc51-6b62-726a-b322-200ca93bed09","kind":"score.total_changed","summary":"Trust score (66 → 67)","materiality":"functional","direction":"improvement","scoreDelta":1,"occurredOn":"2026-11-21","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1fc51-6b62-726a-b322-200ca93bed09"},{"id":"chg_01a1f72a-9457-7e94-8700-655f1b552920","kind":"param.added_optional","summary":"“country_payment_codes” added an optional parameter “page”","materiality":"cosmetic","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-20","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f72a-9457-7e94-8700-655f1b552920"},{"id":"chg_01a1f72a-9458-7c2c-8a5e-343a55ccb84f","kind":"param.added_optional","summary":"“payment_cutoff_times” added an optional parameter “page”","materiality":"cosmetic","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-20","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f72a-9458-7c2c-8a5e-343a55ccb84f"},{"id":"chg_01a1f72a-9459-74ab-b58f-313b91df6052","kind":"param.added_optional","summary":"“swift_lookup” added an optional parameter “details_section”","materiality":"cosmetic","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-20","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f72a-9459-74ab-b58f-313b91df6052"},{"id":"chg_01a1f72a-9459-7b9d-9b8f-88a92536bc97","kind":"param.added_optional","summary":"“swift_lookup” added an optional parameter “page”","materiality":"cosmetic","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-20","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f72a-9459-7b9d-9b8f-88a92536bc97"},{"id":"chg_01a1f1fd-24fa-7352-a401-90fba7491f0a","kind":"tool.description_changed","summary":"Tool “sanctions_screen” rewrote its description, which is the text the model reads","materiality":"security","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-19","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f1fd-24fa-7352-a401-90fba7491f0a"},{"id":"chg_01a1f1fd-24fb-717d-ab76-a470af4cce7b","kind":"tool.added","summary":"New tool “crypto_wallet_report”","materiality":"functional","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-19","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f1fd-24fb-717d-ab76-a470af4cce7b"},{"id":"chg_01a1f1fd-24fb-7688-a14b-1f145a3794c4","kind":"tool.added","summary":"New tool “crypto_wallet_result”","materiality":"functional","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-19","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f1fd-24fb-7688-a14b-1f145a3794c4"},{"id":"chg_01a1f1fd-24fb-7c16-891e-f687f1bde29b","kind":"tool.added","summary":"New tool “crypto_wallet_screen”","materiality":"functional","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-19","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f1fd-24fb-7c16-891e-f687f1bde29b"},{"id":"chg_01a1f1fd-24fc-709d-93ba-13d0e8144e2e","kind":"score.total_changed","summary":"Trust score (65 → 66)","materiality":"functional","direction":"improvement","scoreDelta":1,"occurredOn":"2026-11-19","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1f1fd-24fc-709d-93ba-13d0e8144e2e"},{"id":"chg_01a1e7ae-06e2-7ac5-884c-db28d60d86d1","kind":"score.total_changed","summary":"Trust score (64 → 65)","materiality":"functional","direction":"improvement","scoreDelta":1,"occurredOn":"2026-11-17","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1e7ae-06e2-7ac5-884c-db28d60d86d1"},{"id":"chg_01a1e287-323a-7e14-98dd-c506cd63864f","kind":"tool.description_changed","summary":"Tool “sanctions_screen” rewrote its description, which is the text the model reads","materiality":"security","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-16","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1e287-323a-7e14-98dd-c506cd63864f"},{"id":"chg_01a1e287-323b-7ad8-aff4-54303b791c4f","kind":"param.description_changed","summary":"“settlement_eta” reworded the description of “currency”","materiality":"cosmetic","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-16","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1e287-323b-7ad8-aff4-54303b791c4f"},{"id":"chg_01a1e287-323c-70e6-9a59-96d88fd92ecd","kind":"tool.description_changed","summary":"Tool “ssi_lookup” rewrote its description, which is the text the model reads","materiality":"security","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-16","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1e287-323c-70e6-9a59-96d88fd92ecd"},{"id":"chg_01a1dd63-a2e8-71ed-9681-e9229273d496","kind":"score.total_changed","summary":"Trust score (63 → 64)","materiality":"functional","direction":"improvement","scoreDelta":1,"occurredOn":"2026-11-15","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1dd63-a2e8-71ed-9681-e9229273d496"},{"id":"chg_01a1d314-f541-7aa3-81d7-b239858e6585","kind":"check.reason","summary":"MCP protocol (Implements a current MCP spec version (2026-07-28).)","materiality":"functional","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-13","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1d314-f541-7aa3-81d7-b239858e6585"},{"id":"chg_01a1d314-f543-7313-ab66-db7726f7ea85","kind":"protocol.version_changed","summary":"MCP protocol version (2025-11-25 → 2026-07-28)","materiality":"functional","direction":"neutral","scoreDelta":null,"occurredOn":"2026-11-13","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1d314-f543-7313-ab66-db7726f7ea85"},{"id":"chg_01a1d314-f543-78a1-835b-71e2173b52c2","kind":"score.total_changed","summary":"Trust score (62 → 63)","materiality":"functional","direction":"improvement","scoreDelta":1,"occurredOn":"2026-11-13","url":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp#chg-chg_01a1d314-f543-78a1-835b-71e2173b52c2"}],"truncated":true,"feedUrl":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp/changelog.json"},"links":{"html":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp","markdown":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp.md","changelogJson":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp/changelog.json","changelogRss":"https://verifymcp.io/servers/ai-ohmyfin-sanctions/mcp.xml","external":[{"label":"Remote endpoint","href":"https://mcp.ohmyfin.ai/mcp?from=registry-sanctions"},{"label":"Website","href":"https://ohmyfin.ai/sanctions"}]}}