Remote MCP · Endpoint

FX Reference Rates MCP server

No. FX Reference Rates answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://fx-reference-rates.regnotes.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.regnotes.fx-reference-rates/fx-reference-rates
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
652 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
ECB FX rates, cloud GPU and LLM API prices, World Bank country macro data; pay per call via x402
Listing
From the official MCP registry (active).
Recent checks of FX Reference Rates
CheckedResultHandshake
34 minutes agoHandshake completed652 ms
3 days agoHandshake completed347 ms
13 days agoHandshake completed568 ms
13 days agoHandshake completed609 ms
15 days agoHandshake completed773 ms
16 days agoHandshake completed895 ms
17 days agoHandshake completed660 ms
18 days agoHandshake completed670 ms
18 days agoHandshake completed971 ms
20 days agoHandshake completed1.00 s
22 days agoHandshake completed1.09 s
25 days agoHandshake completed60 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with FX Reference Rates and makes no claim about it beyond what these checks measured.