Remote MCP · Endpoint

Chord MCP server

No. Chord answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://api.getchord.xyz/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.getchordlabs/chord
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
784 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Swap quotes + unsigned txs on 8 EVM chains, plus Solana data: boards, candles, wallet PnL. No key.
Listing
From the official MCP registry (active).
Recent checks of Chord
CheckedResultHandshake
12 minutes agoHandshake completed784 ms
9 days agoHandshake completed801 ms
9 days agoHandshake completed783 ms
11 days agoHandshake completed900 ms
12 days agoHandshake completed926 ms
13 days agoHandshake completed788 ms
14 days agoHandshake completed818 ms
14 days agoHandshake completed313 ms
16 days agoHandshake completed928 ms
19 days agoHandshake completed819 ms
21 days agoHandshake completed322 ms
24 days agoHandshake completed884 ms
26 days agoHandshake completed823 ms
28 days agoHandshake completed816 ms

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

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