Chord
REMOTE · API.GETCHORD.XYZ
Swap quotes + unsigned txs on 8 EVM chains, plus Solana data: boards, candles, wallet PnL. No key.
Available components
Last scanned (7 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1642 tokens (~96/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 0
- “chord_quote” reworded the description of “chain” cosmetic
- “chord_swap_tx” reworded the description of “chain” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 16 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.2.0 functional
- 15 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://api.getchord.xyz/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getchord.xyz | CN=WE1,O=Google Trust Services,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ea57719855f82bb50ed68fa497173f0a |
| SANs: getchord.xyz, *.getchord.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.getchord.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| getchord.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.getchord.xyz/v1/mcp | Verified | 200 | |
| http (plaintext) | http://api.getchord.xyz/v1/mcp | HTTPS enforced | 308 | https://api.getchord.xyz/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
chord_ask Ask Chord ~80
Ask Chord's analyst a question in plain language (markets, tokens, wallets, perps, macro). Uses many data sources and takes 10 to 60 seconds. Needs an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Up to 1,000 characters. |
| wallet | string | – | Optional: lets 'my PnL' resolve. |
No output schema declared.
No examples provided.
chord_candles Token candles ~99
OHLCV candles of a token from Chord's own index.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| limit | integer | – | Rows to return (default 200). |
| tf | string | – | Candle size (default 1h). |
No output schema declared.
No examples provided.
chord_chains Chains and capabilities ~62
The chains Chord serves, with their native asset, anchors and which capabilities each one has (overview, tokens, trades, candles, wallet PnL, smart money, holders, LP, quote, swap). Call this first when unsure what a chain supports.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chord_holders Token holders ~87
Holder ledger of a token (balances by address) on the chains that keep one.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| limit | integer | – | Rows to return (default 25). |
No output schema declared.
No examples provided.
chord_lp_pools LP pools ~61
Pools ranked for a liquidity provider: volume, fees, TVL, fee/TVL.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| limit | integer | – | Rows to return (default 25). |
No output schema declared.
No examples provided.
chord_lp_positions LP positions ~72
A wallet's liquidity positions on one chain: range, value, fees, in or out of range.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| wallet | string | yes | Wallet address: 0x… on EVM chains, base58 on Solana. |
No output schema declared.
No examples provided.
chord_overview Chain overview (24h) ~51
A chain's last 24 hours on the venues Chord indexes: volume, swaps, venue share, hourly buckets.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
No output schema declared.
No examples provided.
chord_quote Swap quote ~208
Best swap quote on an EVM chain. Chord's own router answers first; another aggregator only when Chord cannot route. Amounts are integer strings in the token's smallest unit; the zero address is the native asset. Returns a quoteId valid for 2 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Input amount in the smallest unit, digits only. |
| chain | string | yes | EVM chain key. Solana swaps are REST only: GET /v1/sol/trade/quote. |
| slippageBps | integer | – | Default 50. |
| taker | string | – | Optional: the wallet that will sign. With it the answer includes the transaction and a simulation. |
| tokenIn | string | yes | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
| tokenOut | string | yes | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
No output schema declared.
No examples provided.
chord_search Search tokens ~67
Find a token on one chain by symbol, name or address. Returns candidates with their addresses; similar tickers are common, so compare addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| query | string | yes | Symbol, name or address. |
No output schema declared.
No examples provided.
chord_smart_money Smart money board ~100
Wallets ranked by profit on one chain, bots removed. Not every chain has this board.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| days | integer | – | Window in days (default 7). Solana has 1, 3, 7; EVM boards have 1, 7, 30. |
| limit | integer | – | Rows to return (default 25). |
No output schema declared.
No examples provided.
chord_status Chain status ~33
Live health of every chain: routing engine state, how old the newest indexed trade is, and the public status page link.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chord_swap_tx Build swap transaction ~185
The UNSIGNED transaction for a swap, plus the approval it needs and a simulation run as the taker. Nothing is sent: the taker's own wallet signs and broadcasts. Pass a quoteId from chord_quote, or the full parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | – | – |
| chain | string | – | EVM chain key. Solana swaps are REST only: GET /v1/sol/trade/quote. |
| quoteId | string | – | – |
| slippageBps | integer | – | – |
| taker | string | yes | The wallet that signs and receives. |
| tokenIn | string | – | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
| tokenOut | string | – | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
No output schema declared.
No examples provided.
chord_token Token details ~82
One token on one chain: price, 24h volume and trades, pools or venues, and what the index knows about it.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
No output schema declared.
No examples provided.
chord_tokens Token board ~91
The chain's 24h token board: price, volume, trades, change. Sort names differ by chain; a wrong one is answered with the allowed list.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| limit | integer | – | Rows to return (default 50). |
| sort | string | – | Board order, e.g. volume, trades, change. |
No output schema declared.
No examples provided.
chord_trades Token trades ~95
The newest swaps of a token, with side, size in USD, price, venue and the wallet where it is known.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token address: 0x… on EVM chains, the base58 mint on Solana (case-sensitive). |
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| limit | integer | – | Rows to return (default 30). |
No output schema declared.
No examples provided.
chord_wallet Wallet PnL ~79
A wallet's trading result on one chain: realised and open PnL per token. Windows differ by chain and are stated in the answer.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| wallet | string | yes | Wallet address: 0x… on EVM chains, base58 on Solana. |
No output schema declared.
No examples provided.
chord_wallet_trades Wallet trades ~73
A wallet's recent swaps on one chain. Not every chain has this; chord_chains says which.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | Chain key. chord_chains lists what each chain supports. |
| wallet | string | yes | Wallet address: 0x… on EVM chains, base58 on Solana. |
No output schema declared.
No examples provided.
How do I install the Chord MCP server?
Chord is a hosted endpoint at https://api.getchord.xyz/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.getchord.xyz
claude mcp add --transport http getchordlabs-chord 'https://api.getchord.xyz/v1/mcp'
What is the Chord MCP server?
Chord is an MCP server listed in the public MCP registry as io.github.getchordlabs/chord. Swap quotes + unsigned txs on 8 EVM chains, plus Solana data: boards, candles, wallet PnL. No key. This page covers its hosted endpoint (https://api.getchord.xyz/v1/mcp).
Is the Chord MCP server safe to use?
Chord scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Chord MCP server expose?
Chord exposes 17 tools: chord_chains, chord_status, chord_overview, chord_tokens, chord_search, and 12 more. Their descriptions and schemas cost roughly 1,525 tokens of context every time the server is loaded.
Does the Chord MCP server require authentication?
No. We connected to Chord without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Chord MCP server still maintained?
Chord is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.