Back to MCP servers

iPayX FX Audit — Hidden Bank Fee Detector

https://ipayx-fx-audit--ybolduc.run.tools
● healthy

uptime_30d 1.0%; p95 350.9ms; conformance: fail

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 764 ms, 95th percentile 1,574 ms.

When we called tools/list it returned 4 tools, including check_fx_mid_market_rate, audit_fx_transaction, full_forensic_fx_report, over MCP protocol revision 2025-03-26.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 5% and higher on readiness than 38%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

Tools (4)

As returned by the server's own tools/list when we called it.

check_fx_mid_market_rate
Fetch live mid-market FX rate for a currency pair. Returns BOTH directions (pair + inverted_pair) so AI clients can detect quote direction. Optional bank_rate t…
audit_fx_transaction
Performs a forensic FX audit on a currency transaction. Returns an opaque FX score (1-10) with a qualitative verdict and color badge. Raw spread percentages, mi…
full_forensic_fx_report
Generate a full forensic FX audit report with detailed breakdown, partner routing, and recommendations. Requires a valid Bearer API token from the iPayX dashboa…
compare_fx_sources
Compare FX rates across multiple sources side-by-side: mid-market (Twelve Data), Stripe FX Quotes API (if api key provided), and the user's bank rate. Returns e…
Transport
—
Auth
—
Cost
—
Protocol revision
2025-03-26
negotiated, not declared

MCP readiness

B · 78/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 73.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (1296 ms).
Protocol revision 5/10 Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 4 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 0/5 not seen in a source for over 30 days.
Auth declaration 0/5 How to authenticate is not stated.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (1296 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-12.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness
Higher than 38% of peers
This listing 78 · peer median 81
Latency
Faster than 5% of peers
This listing 1,296 ms · peer median 349 ms

Where it loses the most points, and how to win them back

  • Protocol revision −5 — Support the current protocol revision.
    Now: Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28.
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
  • Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
    Now: not seen in a source for over 30 days.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://ipayx-fx-audit--ybolduc.run.tools
JSON-RPC initialize probe
curl -X POST https://ipayx-fx-audit--ybolduc.run.tools \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://ipayx-fx-audit--ybolduc.run.tools
Listed at (chiark)
https://chiark.ai/agents/431f9f8d-c2d0-44ad-83d1-894520a21f15