Remote MCP · Endpoint

Thai FX Compare MCP server

No. Thai FX Compare answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://fxratetracker.njtools.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.codekraiwa/thai-fx-compare
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
481 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free Thai bank FX MCP: current TT rates, best bank, bank list, and historical observations.
Listing
From the official MCP registry (active).
Recent checks of Thai FX Compare
CheckedResultHandshake
2 hours agoHandshake completed481 ms
1 day agoHandshake completed689 ms
4 days agoHandshake completed144 ms
6 days agoHandshake completed210 ms
9 days agoHandshake completed459 ms
11 days agoHandshake completed188 ms
13 days agoHandshake completed254 ms
15 days agoHandshake completed294 ms
17 days agoHandshake completed219 ms
19 days agoHandshake completed130 ms
20 days agoHandshake completed240 ms
22 days agoHandshake completed180 ms
23 days agoHandshake completed321 ms

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

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 Thai FX Compare and makes no claim about it beyond what these checks measured.