Should my agent depend on the MCP server ai.ohmyfin/banking-intelligence?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

banking intelligence

ai.ohmyfin/banking-intelligence

Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.

— the operator's own registry description reported

Publisher ai.ohmyfin · first seen 2026-08-12 · endpoint https://mcp.ohmyfin.ai/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.705 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency452 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools33

vs populationhigh

capabilities5

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_9b2a4778619634c5fa4900cc · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

bank_holidays banks_using_correspondent company_registries company_search_company company_search_person company_search_result country_banking_rules country_export_controls country_payment_codes eccn_lookup export_controls_screen federal_register_changes fx_rate fx_rate_history fx_timing_advisor fx_volatility goods_classify gpi_status_codes hs_code_lookup iban_validate is_business_day_check mcp_register mcp_verify payment_cutoff_times payment_method_compare sanctions_screen settlement_eta ssi_lookup swift_lookup swift_message_reference track_payment tracking_history value_date

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	33/33	✓
has a description	33/33	✓
description is substantive	33/33	✓
parameters are typed	33/33	✓
parameters are described	1/33	1/33

33 of 33 tools graded · 33 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

3.1.0

server version Ohmyfin Banking Intelligence

Capabilities: experimental extensions prompts resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:37Z	ok_tools	200	452	2025-06-18
2026-08-12T05:32:55Z	ok_tools	200	471	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/ai.ohmyfin/banking-intelligence.svg)](https://robinsaige.com/s/ai.ohmyfin/banking-intelligence)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview