Remote MCP · Endpoint

CrossFin MCP server

No. CrossFin answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://crossfin.dev/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.bubilife1202/crossfin
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
556 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
AI agent access to Asian crypto markets. Korean exchange routing and x402 paid APIs.
Listing
From the official MCP registry (active).
Recent checks of CrossFin
CheckedResultHandshake
1 hour agoHandshake completed556 ms
2 days agoHandshake completed1.75 s
4 days agoHandshake completed1.44 s
5 days agoHandshake completed1.48 s
7 days agoHandshake completed1.65 s
8 days agoHandshake completed2.34 s
9 days agoHandshake completed1.54 s
12 days agoHandshake completed1.47 s
13 days agoHandshake completed1.57 s
15 days agoHandshake completed1.46 s
16 days agoHandshake completed1.61 s
18 days agoHandshake completed1.35 s
19 days agoHandshake completed1.46 s
20 days agoHandshake completed1.43 s
20 days agoHandshake completed291 ms
21 days agoHandshake completed1.53 s
22 days agoHandshake completed2.09 s

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

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