Skip to content

MCP servers › ai.ohmyfin › invoice

MCP server · registry snapshot 2026-11-07 · last tested 2026-11-07

invoice MCP server

Registry name ai.ohmyfin/invoice

by ohmyfin.ai · domain (the registry's namespace rule)Website ↗

Cross-border invoices for AI agents: parties screened, VAT ID checked, EN 16931 e-invoice in PDF. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-07version 1.0.0streamable HTTP34 tools

Summary

ai.ohmyfin/invoice is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain ohmyfin.ai. On 2026-11-07 ProtocolProbe connected to it in read-only mode and read its inventory: 34 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
34
Last tested
2026-11-07

Tool list size

35,026 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (34 tools). Counted with Anthropic's token counter on 2026-11-09, from the tool list we read on 2026-11-07. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-07 (mcp.ohmyfin.ai), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-07
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-11-06 (registry, as of the 2026-11-07 snapshot)
First listed version
2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-07
Package and repository
checked 2026-11-07
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-06, listed on 2026-11-07 with version 1.0.0 (published 2026-11-06).

Source: the official MCP Registry list on 2026-11-06 and on 2026-11-07.

What it is

What does this server offer?

Observed inventory
34tools
0resources
0prompts

None of its 34 tools are described as changing anything. For 34 the reading was uncertain, so no mark is shown.

  • swift_lookupon 2 other servers

    “Search banks and financial institutions by name, SWIFT/BIC code, or country.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • querystringrequired“Bank name, BIC, or bank name plus city ("Commerzbank Frankfurt").”
    • countrystring or null“Optional country filter: an ISO 3166-1 alpha-2 code ("ID", "DE") or a full English name ("Indonesia", "Germany").”
    • limitinteger“Maximum number of banks to return, 1-100 (default 20).”
  • iban_validateon 20 other servers

    “Validate an IBAN and identify the institution that holds the account.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • ibanstringrequired“The IBAN to check, e.g.”
  • country_banking_ruleson 2 other servers

    “Get banking rules and requirements for a country.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • country_codestringrequired“ISO 3166-1 alpha-2 country code, e.g.”
  • country_payment_codeson 2 other servers

    “Look up country-specific payment codes (KNP, purpose codes, etc.).”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • country_codestringrequired“ISO 3166-1 alpha-2 country code, e.g.”
    • code_typestringrequired“Which code table to search, as named in country_banking_rules payment_requirements.required_fields[].code_type (e.g.”
    • searchstring or null“Optional keyword filter (e.g.”
  • “Get the latest available reference (mid-market) exchange rate for a pair.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 2 required
    • basestringrequired“Base currency, ISO 4217 (e.g.”
    • targetstringrequired“Target currency, ISO 4217 (e.g.”
  • fx_rate_historyon 2 other servers

    “Get the historical reference exchange-rate series for a currency pair.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • basestringrequired“Base currency, ISO 4217 (e.g.”
    • targetstringrequired“Target currency, ISO 4217 (e.g.”
    • daysinteger“Lookback window in calendar days, 1-365 (default 90).”
  • gpi_status_codeson 2 other servers

    “Explain SWIFT GPI tracking status codes and provide stuck-payment investigation guidance.”

    Publisher declares: read-only yes · open-world no

    1 input
    • codestring or null“Optional ISO 20022 status code (ACSP, ACCC, PDNG, RJCT, RTRN, BLCK) or reason code (e.g.”
  • swift_message_referenceon 2 other servers

    “Look up SWIFT message types — MT (FIN) and MX (ISO 20022).”

    Publisher declares: read-only yes · open-world no

    1 input
    • message_typestring or null“Optional message type, e.g.”
  • payment_cutoff_timeson 2 other servers

    “Get payment system cutoff times for major clearing systems.”

    Publisher declares: read-only yes · open-world no

    2 inputs
    • systemstring or null“Optional clearing system code or name, e.g.”
    • currencystring or null“Optional ISO 4217 code to filter by (e.g.”
  • fx_volatilityon 2 other servers

    “Get realized FX volatility for a currency pair, and size the FX risk on an exposure held to a future date.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • basestringrequired“Base currency, ISO 4217 (e.g.”
    • targetstringrequired“Target currency, ISO 4217 (e.g.”
    • horizon_daysinteger or null“Optional.”
  • fx_timing_advisoron 2 other servers

    “Get FX trading windows for FX execution timing and spread / rate optimization.”

    Publisher declares: read-only yes · open-world no

    1 input
    • currencystring or null“Optional ISO 4217 code (e.g.”
  • payment_method_compareon 2 other servers

    “Compare payment methods and investigate fee deductions for a country pair.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 2 required
    • source_countrystringrequired“Sending country, ISO 3166-1 alpha-2 country code (e.g.”
    • dest_countrystringrequired“Receiving country, ISO 3166-1 alpha-2 country code (e.g.”
Show 22 more tools
  • bank_holidayson 5 other servers

    “Get bank/public holidays for a country with payment impact analysis.”

    Publisher declares: read-only yes · open-world yes

    2 inputs, 1 required
    • country_codestringrequired“ISO 3166-1 alpha-2 country code, e.g.”
    • yearinteger or null“Calendar year, 2020-2030 (default: the current year).”
  • is_business_day_checkon 2 other servers

    “Check if a specific date is a business day in a country.”

    Publisher declares: read-only yes · open-world yes

    2 inputs, 2 required
    • country_codestringrequired“ISO 3166-1 alpha-2 country code, e.g.”
    • check_datestringrequired“The date to check, YYYY-MM-DD (ISO 8601).”
  • “Calculate the value/settlement date for a payment.”

    Publisher declares: read-only yes · open-world yes

    6 inputs, 2 required
    • source_countrystringrequired“Sender's country, ISO 3166-1 alpha-2 country code (e.g.”
    • dest_countrystringrequired“Receiver's country, ISO 3166-1 alpha-2 country code (e.g.”
    • settlement_typestring“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_currencystring or null“Base currency for FX, ISO 4217 (e.g.”
    • target_currencystring or null“Target currency for FX, ISO 4217 (e.g.”
    • from_datestring or null“Start date, YYYY-MM-DD (default: today).”
  • settlement_etaon 2 other servers

    “BETA.”

    Publisher declares: read-only yes · open-world no

    12 inputs
    • uetrstring or null“UETR of a tracked payment, UUID v4 (e.g.”
    • currencystring or null“3-letter ISO 4217 currency, for the pre-trade path.”
    • sender_bicstring or null“Sending bank's BIC (8 or 11 characters) or bank name, for the pre-trade path.”
    • receiver_bicstring or null“Receiving bank's BIC (8 or 11 characters) or bank name, for the pre-trade path.”
    • intermediary_bicstring or null“Optional BIC of a known intermediary bank.”
    • current_statusstring or null“Status code such as ACSP, for the path without a uetr only.”
    • elapsed_business_daysnumber or null“Business days already in flight, for the path without a uetr only.”
    • amountnumber or string or null“Payment amount; it improves the delay-risk assessment.”
    • sender_countrystring or null“Optional ISO 3166-1 alpha-2 country code of the sending bank.”
    • receiver_countrystring or null“Optional ISO 3166-1 alpha-2 country code of the receiving bank.”
    • arrive_by_datestring or null“YYYY-MM-DD; switches to reverse send-by mode.”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • transfer_coston 2 other servers

    “BETA.”

    Publisher declares: read-only yes · open-world no

    10 inputs, 3 required
    • bank_swiftstringrequired“Sending bank's BIC, 8 or 11 characters.”
    • amountnumberrequired“Transfer amount in `currency`, greater than zero.”
    • currencystringrequired“3-letter ISO 4217 transfer currency.”
    • charge_typestring“SHA (default), OUR or BEN.”
    • beneficiary_bicstring or null“Receiving bank's BIC (8 or 11 characters); needed for a total.”
    • channelstring or null“Sending channel: online | branch | mobile_app | any.”
    • customer_segmentstring or null“Who is SENDING: individual | business | financial_institution.”
    • beneficiary_segmentstring or null“Who is being PAID: individual | business | financial_institution.”
    • customer_sub_segmentstring or null“The sender's tier at their bank: standard | premium | private_banking | vip.”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • mcp_registeron 2 other servers

    “Register for an Ohmyfin API key to use paid tools.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 3 required
    • emailstringrequired“Your email address.”
    • organization_namestringrequired“Your company or project name.”
    • accept_termsbooleanrequired“Must be true.”
  • “Verify your email and receive your API key.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 2 required
    • emailstringrequired“The email address you registered with.”
    • codestringrequired“The 6-digit verification code from that email.”
  • sanctions_screenon 28 other servers

    “Screen a name against global sanctions and watchlists.”

    Publisher declares: read-only yes · open-world no

    4 inputs, 1 required
    • namestringrequired“The person or entity name to screen.”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
    • thresholdinteger“Minimum match score, 0-100 (default 85).”
    • subject_typestring“What is being screened: "bank" for a financial institution, "party" for a company or individual, or "auto" (default).”
  • “Look up an Export Control Classification Number (ECCN).”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • eccnstringrequired“Export Control Classification Number, e.g.”
  • country_export_controlson 2 other servers

    “Look up export control restrictions for a specific country.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • country_codestringrequired“ISO 3166-1 alpha-2 country code, e.g.”
    • jurisdictionstring“Optional filter by jurisdiction, e.g.”
  • export_controls_screenon 2 other servers

    “Screen goods for export-control restrictions to a destination country.”

    Publisher declares: read-only yes · open-world no

    5 inputs, 1 required
    • destination_countrystringrequired“Destination country, ISO 3166-1 alpha-2 country code (e.g.”
    • eccnstring“Export Control Classification Number, e.g.”
    • hs_codestring“Harmonized System code, 4-8 digits (e.g.”
    • goods_descriptionstring“Free-text goods description, English or Russian.”
    • jurisdictionstring“"US" (default), "EU", "UK", "JP", "ITAR", or "ALL".”
  • hs_code_lookupon 3 other servers

    “Reverse-lookup an HS code → mapped export-control classifications (ECCNs).”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • hs_codestringrequired“HS code, 4-6 digits (e.g.”
    • jurisdictionstring“Optional filter: "US", "EU", "UK" or "JP".”
  • goods_classifyon 2 other servers

    “Classify goods for export control from a description (or HS code).”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • descriptionstringrequired“Goods description, at least 2 characters (e.g.”
    • hs_codestring“Optional known HS code (4 or 6 digits) for a direct lookup.”
    • languagestring“Optional hint: "en" or "ru" (auto-detected if omitted).”
  • federal_register_changeson 2 other servers

    “Get recent US regulatory changes from BIS and OFAC.”

    Publisher declares: read-only yes · open-world no

    5 inputs
    • agencystring“Optional: "BIS" (Bureau of Industry and Security) or "OFAC" (Office of Foreign Assets Control).”
    • categorystring“Optional: "entity_list", "rule_change", "country_policy" or "sanctions".”
    • severitystring“Optional: "critical", "high", "medium" or "low".”
    • daysinteger“Days to look back, 1-365 (default 30).”
    • limitinteger“Maximum number of changes to return (default 50).”
  • track_paymenton 3 other servers

    “Track a SWIFT payment by UETR or reference number.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    6 inputs, 3 required
    • amountnumberrequired“Transaction amount as sent (e.g.”
    • currencystringrequired“ISO 4217 code of the currency the payment was SENT in (e.g.”
    • datestringrequired“Transaction date.”
    • uetrstring or null“UETR, UUID v4 (e.g.”
    • referencestring or null“Sender's bank reference number (MT103 field 20 / pacs.008 InstrId).”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • tracking_historyon 2 other servers

    “Show how a SWIFT payment's tracking results changed over time.”

    Publisher declares: read-only yes · open-world no

    3 inputs
    • uetrstring or null“UETR (UUID v4) of the payment.”
    • referencestring or null“Sender's reference (MT103 field 20), used when there is no UETR.”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • “Look up correspondent banking / settlement instructions (SSI) for a bank.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 2 required
    • swiftstringrequired“BIC of the bank, 8 or 11 characters (e.g.”
    • currencystringrequired“ISO 4217 currency code (e.g.”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • banks_using_correspondenton 2 other servers

    “Reverse SSI lookup — find banks that use a given correspondent for a currency.”

    Publisher declares: read-only yes · open-world no

    6 inputs, 3 required
    • correspondent_swiftstringrequired“BIC of the correspondent bank, 8 or 11 characters (e.g.”
    • currencystringrequired“ISO 4217 currency code (e.g.”
    • countrystringrequired“ISO 3166-1 alpha-2 country code of the client banks (e.g.”
    • name_prefixstring or null“Optional prefix on the client bank's name (e.g.”
    • pageinteger“Result page, 1-4 (default 1).”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • company_search_personon 2 other servers

    “EXPERIMENTAL — Search company registries for a person's directorships, officer roles, and shareholdings.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs, 2 required
    • namestringrequired“Person name to search for.”
    • jurisdictionsarrayrequired“Registry codes to search, at least one (e.g.”
    • include_sanctions_checkboolean“Screen every person and company found against sanctions lists (default true).”
    • include_inactive_rolesboolean“Include resigned and ceased roles (default true).”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • company_search_companyon 2 other servers

    “EXPERIMENTAL — Search company registries for a company with its officers and shareholders.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    7 inputs, 2 required
    • namestringrequired“Company name to search for.”
    • jurisdictionsarrayrequired“Registry codes to search, at least one (e.g.”
    • include_sanctions_checkboolean“Screen every company and person found against sanctions lists (default true).”
    • include_officersboolean“Include directors and officers (default true).”
    • include_shareholdersboolean“Include PSC / beneficial owners (default true).”
    • include_only_activeboolean“Return active companies only (default false).”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • company_search_resulton 2 other servers

    “EXPERIMENTAL — Retrieve cached company search results by search ID.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • search_idstringrequired“The search_id returned by a previous company_search_person or company_search_company call.”
    • api_keystring or null“Your Ohmyfin API key (prod-...).”
  • company_registrieson 2 other servers

    “EXPERIMENTAL — List available company registries and supported jurisdictions.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-07; remote servers are read the day they appear and again about every 30 days; package servers at the monthly refresh.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 114
Tools with a description
100% of 34
Typical description length
1,760 characters

The tool set

Counted from the listing

Tools
34
Size of the list
about 23,654 tokens for an agent to load (characters ÷ 4)
Naming
34 of 34 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 34 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-07 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.ohmyfin.ai/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "invoice": {
      "url": "https://mcp.ohmyfin.ai/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "invoice": {
      "type": "http",
      "url": "https://mcp.ohmyfin.ai/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"invoice","type":"http","url":"https://mcp.ohmyfin.ai/mcp"}'
Claude Code
claude mcp add --transport http invoice https://mcp.ohmyfin.ai/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "invoice": {
      "type": "streamableHttp",
      "url": "https://mcp.ohmyfin.ai/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "invoice": {
      "httpUrl": "https://mcp.ohmyfin.ai/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.invoice]
url = "https://mcp.ohmyfin.ai/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "invoice": {
      "url": "https://mcp.ohmyfin.ai/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.ohmyfin.ai/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.ohmyfin.ai/mcpSession openedmatchesour test · 2026-11-07
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-07

Same tools as other registry entries

Tool lists read · names compared

Its 34 tools have exactly the same names as the tools of 2 other registry entries (all published under the same registry namespace). Their tool descriptions differ in places.

This can be one publisher's family of servers or one template reused under many names. It is a fact about the published tool lists, not a judgement of the publisher and not a safety finding; we compared tool names, not code.

Shared tool names (12 of 34 shown):

bank_holidaysbanks_using_correspondentcompany_registriescompany_search_companycompany_search_personcompany_search_resultcountry_banking_rulescountry_export_controlscountry_payment_codeseccn_lookupexport_controls_screenfederal_register_changes

The other entries

All groups of servers with identical tool lists

Source: our read-only reads of each server's tool list · 2026-10-13 to 2026-11-07. No tool was called.

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-07. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about ai.ohmyfin/invoice

Answered from the data above

Who publishes ai.ohmyfin/invoice?

The registry ties the namespace ai.ohmyfin to the domain ohmyfin.ai; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does ai.ohmyfin/invoice need an API key or sign-in?

It opened a session without any credential on 2026-11-07. The registry entry declares no required credential; no declaration is not a guarantee.

Has ai.ohmyfin/invoice been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-07
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-07, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,413 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 34 tools, 0 resources, 0 prompts.
  4. 5,347 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why. How often each is read again: methodology.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-07; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-07 · read from the registry entry; changes when a new version is listed
MCP capability
experimental, prompts, resources, tools, extensions
our test · 2026-11-07
Transport
streamable HTTP
registry · 2026-11-07 · read from the registry entry; changes when a new version is listed
Required credentials
none declared
registry · 2026-11-07 · no declaration is not a guarantee · read from the registry entry; changes when a new version is listed
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-07
Lifecycle status
registry · 2026-11-07 · status read from the registry every day
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-07 · read from the registry entry; changes when a new version is listed

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “ai.ohmyfin/invoice: MCP server record.” Data checked 2026-11-07. https://protocolprobe.com/mcp/servers/ai.ohmyfin/invoice

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/ai.ohmyfin/invoice)](https://protocolprobe.com/mcp/servers/ai.ohmyfin/invoice)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology