Name: Invoice
Author: ohmyfin

Invoice MCP

Cross-border invoices for AI agents: parties screened, VAT ID checked, EN 16931 e-invoice in PDF.

Tool-list grade A Remote · Streamable HTTP No auth needed 34 tools v1.0.0

No reviews yet by ohmyfin The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Cross-border invoices for AI agents: parties screened, VAT ID checked, EN 16931 e-invoice in PDF.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http ohmyfin-invoice-mcp 'https://mcp.ohmyfin.ai/mcp?from=registry-invoice'

# 2 — ask your agent for something these tools do
#   swift_lookup, iban_validate, country_banking_rules and 31 more

Invoice costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

ohmyfin1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Search banks and financial institutions by name, SWIFT/BIC code, or country. Covers both SWIFT-connected banks and non-SWIFT financial institutions (e-money issuers, payment processors, MFOs, brokerages, VASPs, etc.). Returns: SWIFT/BIC code (if any), name, city, country, institution type, GPI membership, a coarse sanctions FLAG across 7 hard-sanctions watchlists (OFAC SDN, EU, UK, CA, CH, AU, N

Parameter	Type	Required	Notes
query	string	yes	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 an
country		no	Optional country filter: an ISO 3166-1 alpha-2 code ("ID", "DE") or a full English name ("Indonesia", "Germany"). Names are resolved automatically.
limit	integer	no	Maximum number of banks to return, 1-100 (default 20). Values outside the range are clamped.

Validate an IBAN and identify the institution that holds the account. Performs format check, country-specific length check, and ISO 7064 mod-97 checksum verification. Also returns COUNTRY-level banking rules for the IBAN's country prefix (national currency, SEPA status, expected format). CROSS-CHECKS THE BENEFICIARY BANK. Where the country's IBAN registry mask defines the bank identifier as four

Parameter	Type	Required	Notes
iban	string	yes	The IBAN to check, e.g. "DE89370400440532013000". Spaces and hyphens are ignored and letters are upper-cased.

Get banking rules and requirements for a country. Returns IBAN requirements, SEPA membership, FATF listing status, national currency, account format specifications, and country-specific payment requirements (mandatory codes like KNP for Kazakhstan, Purpose of Payment for UAE, etc.). The fatf_listing block is the authoritative answer to "is this country grey-listed / black-listed / under FATF i

Parameter	Type	Required	Notes
country_code	string	yes	ISO 3166-1 alpha-2 country code, e.g. "DE", "US", "KZ".

Look up country-specific payment codes (KNP, purpose codes, etc.). Use country_banking_rules first to see which code types a country requires (in the payment_requirements block), then use this tool to find the right code value. Examples: country_payment_codes("KZ", "knp", "transport") country_payment_codes("KZ", "knp", "insurance") country_payment_codes("AE", "purpose_code", "trade") cou

Parameter	Type	Required	Notes
country_code	string	yes	ISO 3166-1 alpha-2 country code, e.g. "KZ", "AE".
code_type	string	yes	Which code table to search, as named in country_banking_rules payment_requirements.required_fields[].code_type (e.g. "knp", "purpose_code"). Case-insensitive.
search		no	Optional keyword filter (e.g. "transport", "trade", "insurance"). Omit it to list every code in the table, which is a large response.

Get the latest available reference (mid-market) exchange rate for a pair. Rates are the official ECB euro foreign-exchange reference rates where the ECB publishes the currency; pairs whose currency the ECB does not cover (e.g. VND, NGN, PKR, KZT, MAD) fall back to a market data feed. ALWAYS check the source field before describing provenance: "ecb" = official ECB reference rate; "market" = indi

Parameter	Type	Required	Notes
base	string	yes	Base currency, ISO 4217 (e.g. "USD"). The rate is quoted as units of target per 1 base.
target	string	yes	Target currency, ISO 4217 (e.g. "VND").

Get the historical reference exchange-rate series for a currency pair. Returns series (the daily rates) plus the metadata needed to describe it honestly. READ series_coverage BEFORE CHARACTERISING THE PERIOD. days is the window we look back over, NOT a promise of how much history exists: our series start at different dates per currency, so a 365-day request routinely returns five months. `s

Parameter	Type	Required	Notes
base	string	yes	Base currency, ISO 4217 (e.g. "EUR"). Rates are quoted as units of target per 1 base.
target	string	yes	Target currency, ISO 4217 (e.g. "USD").
days	integer	no	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.

Explain SWIFT GPI tracking status codes and provide stuck-payment investigation guidance. USE THIS TOOL FIRST whenever the user reports a payment that is stuck, delayed, not arriving, held, pending, rejected, or otherwise not behaving as expected. It is the primary diagnostic entrypoint for payment investigation — calling with a specific code returns a full investigation playbook (common delay ca

Parameter	Type	Required	Notes
code		no	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.

Look up SWIFT message types — MT (FIN) and MX (ISO 20022). Pass a specific type to get full details, or omit to list all types. Covers customer payments (MT103, pacs.008), FI transfers (MT202, pacs.009), trade finance (MT700, MT760), cash management (MT940, camt.053), and payment status (pacs.002). Also use this tool to answer questions about where specific payment fields live — e.g., where the

Parameter	Type	Required	Notes
message_type		no	Optional message type, e.g. "MT103", "pacs.008", "MT940". Case-insensitive. Omit it to list every type.

Get payment system cutoff times for major clearing systems. Covers RTGS (T2 — formerly TARGET2, CHAPS, Fedwire, BOJ-NET, SIC), net settlement (CHIPS, BACS), SEPA schemes (SCT, SCT Inst, OCT Inst, SDD Core, SDD B2B), FX settlement (CLS, FXYCS), and other systems (CIPS, SPEI, FAST). For same-day EUR guidance: filter by currency="EUR" to retrieve all SEPA schemes plus T2 in one call — the scheme-le

Parameter	Type	Required	Notes
system		no	Optional clearing system code or name, e.g. "T2", "FEDWIRE", "CHAPS". Case-insensitive; "TARGET2" resolves to T2, its name since March 2023. Omit it to list every system or to filter by currency.
currency		no	Optional ISO 4217 code to filter by (e.g. "USD", "EUR").

Get realized FX volatility for a currency pair, and size the FX risk on an exposure held to a future date. Computes 30-day and 90-day annualized volatility from historical ECB reference rates (standard deviation of daily log returns, annualized by sqrt(252)). Returns a qualitative bucket: LOW (<5%), MEDIUM (5-15%), HIGH (15-25%), VERY_HIGH (>25%), PEGGED (currency peg — near-zero volatility, e.g.

Parameter	Type	Required	Notes
base	string	yes	Base currency, ISO 4217 (e.g. "EUR").
target	string	yes	Target currency, ISO 4217 (e.g. "TRY").
horizon_days		no	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.

Get FX trading windows for FX execution timing and spread / rate optimization. Returns market sessions and liquidity windows for a currency. Use this to understand: - Rate optimization (primary, reliable use): higher liquidity means tighter spreads and better rates. Execute during peak windows to minimize conversion costs. - Delay diagnosis (use with care): the FX market session is wh

Parameter	Type	Required	Notes
currency		no	Optional ISO 4217 code (e.g. "EUR", "JPY"). Omit it to get every session and overlap.

Compare payment methods and investigate fee deductions for a country pair. Evaluates SEPA vs SWIFT vs domestic options. Also explains SWIFT charge options (OUR/SHA/BEN) and fee investigation — use this when the beneficiary received less than expected to understand where the money went and which MT103 fields reveal each deduction. Returns cost, speed, requirements, charge options, and step-by-step

Parameter	Type	Required	Notes
source_country	string	yes	Sending country, ISO 3166-1 alpha-2 country code (e.g. "DE", "US").
dest_country	string	yes	Receiving country, ISO 3166-1 alpha-2 country code (e.g. "GB", "TR").

Get bank/public holidays for a country with payment impact analysis. Returns all public holidays plus a 'payment_impact' section that shows: - Whether today is a business day or holiday in this country - Upcoming holidays in the next 14 days - Recent holidays in the last 14 days — for diagnosing a payment that is ALREADY stuck ("in progress for N days", "sent X days ago"). A recent holiday on

Parameter	Type	Required	Notes
country_code	string	yes	ISO 3166-1 alpha-2 country code, e.g. "US", "DE", "GB".
year		no	Calendar year, 2020-2030 (default: the current year). Values outside the range are clamped.

Check if a specific date is a business day in a country. Accounts for weekends (country-specific) and public holidays. Returns whether the date is a business day, and if not, why (weekend or specific holiday name) and the next business day. The response carries a today block with the server's real current date. Resolve any relative date in the user's question ("the 20th", "next Friday") agains

Parameter	Type	Required	Notes
country_code	string	yes	ISO 3166-1 alpha-2 country code, e.g. "US", "DE".
check_date	string	yes	The date to check, YYYY-MM-DD (ISO 8601).

Calculate the value/settlement date for a payment. Determines when a payment will settle based on: - Source and destination country holiday calendars - Weekend conventions (Sat/Sun or Fri/Sat) - Currency center holidays (if FX conversion involved) - Settlement convention (T+0, T+1, T+2) Examples: value_date("US", "DE") value_date("US", "DE", "fx_spot", "USD", "EUR") value_date("DE", "FR",

Parameter	Type	Required	Notes
source_country	string	yes	Sender's country, ISO 3166-1 alpha-2 country code (e.g. "US").
dest_country	string	yes	Receiver's country, ISO 3166-1 alpha-2 country code (e.g. "DE").
settlement_type	string	no	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).
base_currency		no	Base currency for FX, ISO 4217 (e.g. "USD"). Required when settlement_type is "fx_spot".
target_currency		no	Target currency for FX, ISO 4217 (e.g. "EUR"). Required when settlement_type is "fx_spot".
from_date		no	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-

BETA. Estimate when a SWIFT payment will arrive: a corpus-grounded arrival window with an honest tail, computed from real completed payments we have tracked, projected onto the currency's banking calendar. This estimator is in BETA and still calibrating. Say so when you present a number: call it an estimate or a typical window, never a commitment, and never let a user plan an irreversible decisio

Parameter	Required	Notes
uetr	no	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.
currency	no	3-letter ISO 4217 currency, for the pre-trade path. Ignored when the uetr resolves.
sender_bic	no	Sending bank's BIC (8 or 11 characters) or bank name, for the pre-trade path.
receiver_bic	no	Receiving bank's BIC (8 or 11 characters) or bank name, for the pre-trade path.
intermediary_bic	no	Optional BIC of a known intermediary bank.
current_status	no	Status code such as ACSP, for the path without a uetr only.
elapsed_business_days	no	Business days already in flight, for the path without a uetr only.
amount	no	Payment amount; it improves the delay-risk assessment. A plain number is fine: 50000 and "50,000.00" are both accepted.
sender_country	no	Optional ISO 3166-1 alpha-2 country code of the sending bank.
receiver_country	no	Optional ISO 3166-1 alpha-2 country code of the receiving bank.
arrive_by_date	no	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 / val
api_key	no	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.

BETA. Estimate what a cross-border payment will COST, split by WHO PAYS: the sending bank's published fee (the sender's side), what correspondents deduct in transit and what the beneficiary's own bank charges to credit it (the beneficiary's side), and what actually lands. This estimator is in BETA. Present every number as a typical case and a high case, never as a quote, and never let a user comm

Parameter	Type	Required	Notes
bank_swift	string	yes	Sending bank's BIC, 8 or 11 characters.
amount	number	yes	Transfer amount in currency, greater than zero.
currency	string	yes	3-letter ISO 4217 transfer currency.
charge_type	string	no	SHA (default), OUR or BEN. Ask the user rather than guessing.
beneficiary_bic		no	Receiving bank's BIC (8 or 11 characters); needed for a total.
channel		no	Sending channel: online \| branch \| mobile_app \| any.
customer_segment		no	Who is SENDING: individual \| business \| financial_institution.
beneficiary_segment		no	Who is being PAID: individual \| business \| financial_institution. Omitted, it mirrors customer_segment.
customer_sub_segment		no	The sender's tier at their bank: standard \| premium \| private_banking \| vip.
api_key		no	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.

Register for an Ohmyfin API key to use paid tools. Creates an account and sends a 6-digit verification code to your email. After receiving the code, call mcp_verify to complete registration and get your API key. By setting accept_terms to true, you confirm acceptance of the Ohmyfin Terms & Conditions (https://ohmyfin.ai/terms) on behalf of your operator, including the API/MCP access terms (Secti

Parameter	Type	Required	Notes
email	string	yes	Your email address. The verification code is sent to it.
organization_name	string	yes	Your company or project name.
accept_terms	boolean	yes	Must be true. Confirms acceptance of the Ohmyfin Terms & Conditions at https://ohmyfin.ai/terms.

Verify your email and receive your API key. After calling mcp_register, check your email for the 6-digit code and pass it here. On success, returns your production and test API keys. You must subscribe at ohmyfin.ai/subscription to activate paid tools. Examples: mcp_verify("agent@example.com", "123456")

Parameter	Type	Required	Notes
email	string	yes	The email address you registered with.
code	string	yes	The 6-digit verification code from that email.

Screen a name against global sanctions and watchlists. Checks the name against 300+ sanctions, designation and watchlists worldwide, including US OFAC (SDN and non-SDN), EU, UK OFSI, Canada, Switzerland, Australia, New Zealand, Japan, Israel and national lists. Returns matching entities with similarity scores. The response says how many lists were actually searched (lists_searched); report THAT,

Parameter	Type	Required	Notes
name	string	yes	The person or entity name to screen.
api_key		no	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.
threshold	integer	no	Minimum match score, 0-100 (default 85). Values above 95 are treated as 95.
subject_type	string	no	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

Look up an Export Control Classification Number (ECCN). Pure reference tool — returns classification details, controlled jurisdictions, and license requirements for the given ECCN. ECCNs are alphanumeric codes (e.g. "5A001") used under export control regimes (US EAR, EU Dual-Use Regulation, Wassenaar Arrangement) to classify items that may require an export license. Examples: eccn_lookup("5A0

Parameter	Type	Required	Notes
eccn	string	yes	Export Control Classification Number, e.g. "5A001", "3A001", "1C351". Case-insensitive.

Look up export control restrictions for a specific country. Returns embargo status, sanctioned programs, control reasons, and restriction details across jurisdictions (US EAR, EU, UN, etc.) for the given country. Response also includes a payment_jurisdiction_note explaining when each listed restriction actually applies to a payment (US controls only bind when there's a US nexus, etc.). IMPORTANT

Parameter	Type	Required	Notes
country_code	string	yes	ISO 3166-1 alpha-2 country code, e.g. "RU", "CN", "DE".
jurisdiction	string	no	Optional filter by jurisdiction, e.g. "US", "EU". Omit it for every jurisdiction.

Screen goods for export-control restrictions to a destination country. Combines the goods classification with the destination's restriction status and returns whether a license is required, the risk level, applicable license policies (e.g. presumption of denial), control reasons (NS, MT, NP, CB, AT), and proliferation/dual-use flags. Identify the goods by ANY of: ECCN, HS code, or a free-text des

Parameter	Type	Required	Notes
destination_country	string	yes	Destination country, ISO 3166-1 alpha-2 country code (e.g. "RU", "CN").
eccn	string	no	Export Control Classification Number, e.g. "3A001". Give at least one of eccn, hs_code, goods_description.
hs_code	string	no	Harmonized System code, 4-8 digits (e.g. "854231"). Give at least one of eccn, hs_code, goods_description.
goods_description	string	no	Free-text goods description, English or Russian. A fallback for when no eccn or hs_code is known; see the description.
jurisdiction	string	no	"US" (default), "EU", "UK", "JP", "ITAR", or "ALL".

Reverse-lookup an HS code → mapped export-control classifications (ECCNs). For customs brokers / shippers who have an HS (Harmonized System) code and need to know which export-control classifications may apply. Returns the mapped ECCNs with confidence levels, control reasons, sensitivity, and the governing international regime (Wassenaar, MTCR, NSG, etc.). A 4-digit HS heading is accepted, but m

Parameter	Type	Required	Notes
hs_code	string	yes	HS code, 4-6 digits (e.g. "854231", "8411"). Dots and spaces are fine.
jurisdiction	string	no	Optional filter: "US", "EU", "UK" or "JP".

Classify goods for export control from a description (or HS code). Bilingual (English / Russian, auto-detected) goods classifier. Returns the best-matching HS code (with EN+RU descriptions), related ECCNs, control reasons (NS, MT, NP, CB, AT...), an export-control level (high/medium/low/ none), a confidence score, and alternative matches for review. This is destination-agnostic — it identifies W

Parameter	Type	Required	Notes
description	string	yes	Goods description, at least 2 characters (e.g. "uranium centrifuge", "центрифуга для урана").
hs_code	string	no	Optional known HS code (4 or 6 digits) for a direct lookup.
language	string	no	Optional hint: "en" or "ru" (auto-detected if omitted).

Get recent US regulatory changes from BIS and OFAC. Returns Federal Register publications including entity list updates, rule changes, country policy shifts, and new sanctions programs. Examples: federal_register_changes() # Last 30 days, all federal_register_changes(agency="OFAC", days=7) # OFAC changes this week federal_register_changes(category="entity_list"

Parameter	Type	Required	Notes
agency	string	no	Optional: "BIS" (Bureau of Industry and Security) or "OFAC" (Office of Foreign Assets Control). Omit it for both.
category	string	no	Optional: "entity_list", "rule_change", "country_policy" or "sanctions". Omit it for every category.
severity	string	no	Optional: "critical", "high", "medium" or "low". Omit it for every level.
days	integer	no	Days to look back, 1-365 (default 30). A value outside the range is refused.
limit	integer	no	Maximum number of changes to return (default 50).

Track a SWIFT payment by UETR or reference number. Basic SWIFT payment tracking enriched by data from certain banks in the correspondent chain. Returns the overall payment status and, when available, per-bank details showing which banks reported information about this payment. IMPORTANT — every trace needs four things: amount, currency, date, and an identifier (uetr, or reference when there

Parameter	Type	Required	Notes
amount	number	yes	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 than
currency	string	yes	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.
date	string	yes	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.
uetr		no	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 c
reference		no	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.
api_key		no	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.

Show how a SWIFT payment's tracking results changed over time. Returns the DISTINCT tracking results recorded for a payment (by UETR or reference), deduplicated so ten identical re-tracks collapse to one entry while any change — a new last-update, a status change, or new bank data — appears as its own entry. Each entry includes what was ENTERED when the search was run (amount, currency, date) alo

Parameter	Required	Notes
uetr	no	UETR (UUID v4) of the payment. Strongly preferred.
reference	no	Sender's reference (MT103 field 20), used when there is no UETR.
api_key	no	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.

Look up correspondent banking / settlement instructions (SSI) for a bank. Returns the correspondent banks (nostro accounts) that a given bank uses to settle payments in a specific currency, including account numbers (when available) and intermediary chains. Essential for payment routing and pre-validation. Each correspondent is annotated with a clearing_note indicating whether it can clear the c

Parameter	Type	Required	Notes
swift	string	yes	BIC of the bank, 8 or 11 characters (e.g. "DEUTDEFF").
currency	string	yes	ISO 4217 currency code (e.g. "USD", "EUR", "GBP").
api_key		no	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.

Reverse SSI lookup — find banks that use a given correspondent for a currency. Given a correspondent BIC, currency, and origin country, returns the banks in that country that have a declared nostro at the correspondent for that currency. Inverse of ssi_lookup. Returns only swift + name per bank — to retrieve the account number, intermediary chain, or other SSI details for a specific bank from th

Parameter	Type	Required	Notes
correspondent_swift	string	yes	BIC of the correspondent bank, 8 or 11 characters (e.g. "IRVTUS3N").
currency	string	yes	ISO 4217 currency code (e.g. "USD").
country	string	yes	ISO 3166-1 alpha-2 country code of the client banks (e.g. "AE").
name_prefix		no	Optional prefix on the client bank's name (e.g. "AL").
page	integer	no	Result page, 1-4 (default 1). Any other value is refused.
api_key		no	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.

EXPERIMENTAL — Search company registries for a person's directorships, officer roles, and shareholdings. Searches worldwide company registries to find where a person holds director, officer, or shareholder positions. Every person and company found is automatically screened against sanctions lists. You MUST specify at least one jurisdiction. "ALL" is not supported. Available jurisdictions: AM, AT

Parameter	Type	Required	Notes
name	string	yes	Person name to search for.
jurisdictions	array	yes	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.
include_sanctions_check	boolean	no	Screen every person and company found against sanctions lists (default true).
include_inactive_roles	boolean	no	Include resigned and ceased roles (default true).
api_key		no	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.

EXPERIMENTAL — Search company registries for a company with its officers and shareholders. Find company registrations across worldwide registries, including directors, officers, and beneficial owners (PSC/shareholders). Every entity found is automatically screened against sanctions lists. You MUST specify at least one jurisdiction. "ALL" is not supported. Available jurisdictions: AM, AT, AU, BR,

Parameter	Type	Required	Notes
name	string	yes	Company name to search for.
jurisdictions	array	yes	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.
include_sanctions_check	boolean	no	Screen every company and person found against sanctions lists (default true).
include_officers	boolean	no	Include directors and officers (default true).
include_shareholders	boolean	no	Include PSC / beneficial owners (default true).
include_only_active	boolean	no	Return active companies only (default false).
api_key		no	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.

EXPERIMENTAL — Retrieve cached company search results by search ID. Every company_search_person and company_search_company call returns a search_id. Use this tool to retrieve those results again without re-running the search. Examples: company_search_result("abc123-def456")

Parameter	Type	Required	Notes
search_id	string	yes	The search_id returned by a previous company_search_person or company_search_company call.
api_key		no	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.

EXPERIMENTAL — List available company registries and supported jurisdictions. Returns the list of company registries that can be searched, along with the jurisdiction codes you can use in company_search_person and company_search_company. This is the LIVE list and outranks the codes named in those two tools' descriptions. Any country code not returned here has no registry behind it: a search nami

No parameter schema on file.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Invoice or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.0.0 · scanned 7 Nov 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score93

Findings0 threat · 1 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digest81093e8a6e4bc9e555f02803c11039c1a5b1a7eefbb0475f55411bc106002309

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
swift_lookup	no tags
iban_validate	no tags
country_banking_rules	no tags
country_payment_codes	no tags
fx_rate	no tags
fx_rate_history	no tags
gpi_status_codes	no tags
swift_message_reference	no tags
payment_cutoff_times	no tags
fx_volatility	no tags
fx_timing_advisor	no tags
payment_method_compare	no tags
bank_holidays	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
is_business_day_check	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
value_date	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
settlement_eta	no tags
transfer_cost	no tags
mcp_register	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
mcp_verify	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
sanctions_screen	no tags
eccn_lookup	no tags
country_export_controls	no tags
export_controls_screen	no tags
hs_code_lookup	no tags
goods_classify	no tags
federal_register_changes	no tags
track_payment	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
tracking_history	no tags
ssi_lookup	no tags
banks_using_correspondent	no tags
company_search_person	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
company_search_company	external-sink	external-sink: declares readOnlyHint: false, openWorldHint: true
company_search_result	no tags
company_registries	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digest81093e8a6e4bc9e5

Scanned2026-11-07

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

Where are you running it?

Tool surface

Release history

Invoice MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also