ChangeNOW
REMOTE · MCP.CHANGENOW.IO · SCANNED SEP 29
Quote, create and track cross-chain crypto swaps. Non-custodial exchange, no account, no KYC.
Available components
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2366 tokens (~197/item across 12 items; 7 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "never tell the user", at byte 2167 of that field. See how to fix → Fail
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the ChangeNOW MCP server?
ChangeNOW is a hosted endpoint at https://mcp.changenow.io/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 · mcp.changenow.io
claude mcp add --transport http io-changenow-crypto-swap 'https://mcp.changenow.io/mcp'
{
"mcpServers": {
"io-changenow-crypto-swap": {
"url": "https://mcp.changenow.io/mcp"
}
}
} {
"servers": {
"io-changenow-crypto-swap": {
"type": "http",
"url": "https://mcp.changenow.io/mcp"
}
}
} [mcp_servers.io-changenow-crypto-swap] url = "https://mcp.changenow.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-changenow-crypto-swap": {
"type": "remote",
"url": "https://mcp.changenow.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-changenow-crypto-swap --url 'https://mcp.changenow.io/mcp' --transport streamable-http
mcp_servers:
io-changenow-crypto-swap:
url: "https://mcp.changenow.io/mcp" {
"McpServers": {
"io-changenow-crypto-swap": {
"Transport": "http",
"Url": "https://mcp.changenow.io/mcp"
}
}
} assistant mcp add io-changenow-crypto-swap -t streamable-http -u 'https://mcp.changenow.io/mcp'
{
"mcpServers": {
"io-changenow-crypto-swap": {
"type": "http",
"url": "https://mcp.changenow.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
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 29 Sept 2026 · Probed https://mcp.changenow.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=changenow.io | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 764357567b8fffbd130b64d015530e35 |
| SANs: changenow.io, *.changenow.io | ||||||
| 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 mcp.changenow.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| changenow.io. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.changenow.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.changenow.io/mcp | HTTPS enforced | 301 | https://mcp.changenow.io/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 →
check_swap_status Check a swap order ~101
Follow an existing order by id: where it stands, what the deposit and payout amounts turned out to be, the transaction hashes, and a plain-language explanation of what the current stage means and what happens next. Use it after create_swap, and again whenever the user asks where their swap is.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Order id returned by create_swap. |
| sub_id | string | – | Sub order id, for an order the provider split in two. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | string|null | yes | – |
| amount_to | string|null | yes | – |
| created_at | string|null | yes | – |
| deposit_received_at | string|null | yes | – |
| expected_amount_from | string|null | yes | – |
| expected_amount_to | string|null | yes | – |
| from | string | yes | – |
| id | string | yes | – |
| payin_address | string | yes | – |
| payin_extra_id | string|null | yes | – |
| payin_hash | string|null | yes | – |
| payout_address | string | yes | – |
| payout_extra_id | string|null | yes | – |
| payout_hash | string|null | yes | – |
| provider | string | yes | – |
| refund_address | string|null | yes | – |
| refund_amount | string|null | yes | – |
| refund_hash | string|null | yes | – |
| refund_memo | string|null | yes | – |
| stage_explanation | string | yes | – |
| status | string | yes | – |
| to | string | yes | – |
| track_url | string | yes | – |
| updated_at | string|null | yes | – |
| valid_until | string|null | yes | – |
No examples provided.
create_swap Create a swap order ~390
Create a real swap order and return the deposit address the user has to send funds to. This call moves no money by itself, but the order is real: it exists in support, it can expire, and a fixed rate is locked against it. Quote the swap first, validate the recipient address, and confirm the amount and the address with the user before calling this. If the user has not explicitly approved both, use swap_link instead and let them confirm on the page. The answer names who executes the order, and that has to be relayed: some orders are routed to a partner aggregator rather than ChangeNOW.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address that receives the swapped asset. Check it with validate_address first; a wrong network here loses the funds. |
| amount_from | string | – | Amount the user sends. Pass this or amount_to, never both. |
| amount_to | string | – | Amount the user wants to receive. Requires rate_id from quote_swap. |
| contact_email | string | – | Optional email for status notifications about this order. |
| from | string | yes | Asset the user sends, canonical id, for example "eth.eth". |
| memo | string | – | Memo or destination tag for the recipient address, when the asset needs one. |
| promo_code | string | – | Promo code to apply, if the user has one. |
| rate_id | string | – | The rate_id from quote_swap with rate_type "fixed". Required for a fixed rate order. It holds for about two minutes, so quote again right before this call if the user needed time to decide. |
| refund_address | string | – | Where the deposit returns if the swap cannot complete. Strongly recommended: without it a failed swap needs support. |
| refund_memo | string | – | Memo for the refund address. |
| to | string | yes | Asset the user receives, canonical id, for example "usdt.trx". |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | string|null | yes | – |
| amount_to | string|null | yes | – |
| created_at | string|null | yes | – |
| from | string | yes | – |
| id | string | yes | – |
| payin_address | string | yes | – |
| payin_extra_id | string|null | yes | – |
| payout_address | string | yes | – |
| payout_extra_id | string|null | yes | – |
| provider | string | yes | – |
| rate_type | string | yes | – |
| refund_address | string|null | yes | – |
| refund_memo | string|null | yes | – |
| status | string|null | yes | – |
| to | string | yes | – |
| track_url | string | yes | – |
| valid_until | string|null | yes | – |
| warnings | array | yes | – |
No examples provided.
get_asset Asset details ~126
Everything needed to build a swap for one asset: the canonical id, the legacy ticker used in website links, decimals, whether a memo is required and what the receiving side calls it, the address format, the token contract and the warnings to relay to the user. Minimum and maximum amounts are not here because they belong to the pair, not to the asset: get them from quote_swap.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | Canonical id "usdt.trx". A legacy ticker "usdttrc20" or a page slug "tether-trc20" is also accepted. |
| Name | Type | Req | Description |
|---|---|---|---|
| address_regex | string|null | yes | – |
| asset | string | yes | – |
| decimals | number|null | yes | – |
| explorer_address_url | string|null | yes | – |
| explorer_tx_url | string|null | yes | – |
| fixed_rate | boolean | yes | – |
| kind | string | yes | – |
| memo | boolean | yes | – |
| memo_name | string|null | yes | – |
| memo_regex | string|null | yes | – |
| name | string | yes | – |
| network | string | yes | – |
| price_usd | number|null | yes | – |
| slug | string|null | yes | – |
| ticker | string | yes | – |
| token_contract | string|null | yes | – |
| warning_receive | string|null | yes | – |
| warning_send | string|null | yes | – |
No examples provided.
list_assets List exchangeable assets ~299
Find the assets ChangeNOW can exchange and turn what the user said into a canonical asset id. Search by ticker, name or network, filter by network, by fiat or crypto, and by whether a fixed rate is possible. Always call this before quoting: the same ticker exists on several networks and only the canonical id "ticker.network" identifies one of them. When has_more is false the response is the complete answer and no paging is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor from next_cursor of the previous page. Only needed when has_more is true. |
| fixed_rate | boolean | – | Keep only assets the catalogue flags as fixed rate capable. The flag is a hint: a pair flagged false can still get a fixed rate, so confirm with quote_swap rather than filtering a user out. |
| kind | string | – | crypto for swappable coins and tokens, fiat for currencies that can only start a purchase, all for both. |
| limit | integer | – | How many assets to return. Default 50, maximum 500. |
| network | string | – | Keep only assets on this network, for example "eth", "trx", "sol". |
| popular | boolean | – | Return the short curated list. Use this to answer "what can I swap" without paging. |
| q | string | – | Substring search over canonical id, legacy ticker, name and network. Case insensitive. Example: "usdt", "bitcoin", "tron". |
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | yes | – |
| catalogue_version | string | yes | – |
| has_more | boolean | yes | – |
| next_cursor | string|null | yes | – |
| returned | number | yes | – |
| total | number | yes | – |
No examples provided.
quote_swap Quote a swap ~319
Ask what a swap would give, in either direction: pass amount_from to learn what the user receives, or amount_to to learn what the user must send. Returns the rate, the pair minimum and maximum, who would execute the order, and the warnings to relay. With rate_type "fixed" it also returns the rate_id that create_swap needs; that lock lasts about two minutes, so quote again right before creating the order. A fixed rate is not offered on every pair and the tool says so rather than quietly falling back to a float rate. Nothing is created and no funds move.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | string | – | Amount the user sends, as a decimal string. Pass this or amount_to, never both. |
| amount_to | string | – | Amount the user wants to receive, as a decimal string. The answer then says how much to send. |
| from | string | yes | Asset the user sends, canonical id, for example "btc.btc". |
| promo_code | string | – | Promo code to apply, if the user has one. |
| rate_type | string | – | float: the rate is settled when the deposit arrives. fixed: the rate is held until valid_until, about two minutes, and returns the rate_id create_swap needs, usually at a slightly worse rate. Ask for… |
| to | string | yes | Asset the user receives, canonical id, for example "usdt.trx". |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_from | string|null | yes | – |
| amount_to | string|null | yes | – |
| from | string | yes | – |
| from_name | string | yes | – |
| high_network_fee | boolean | yes | – |
| limits_in | string | yes | – |
| max_amount | string|null | yes | – |
| min_amount | string|null | yes | – |
| provider | string | yes | – |
| quote_id | string|null | yes | – |
| rate | string|null | yes | – |
| rate_id | string|null | yes | – |
| rate_type | string | yes | – |
| speed_forecast_minutes | string|null | yes | – |
| to | string | yes | – |
| to_name | string | yes | – |
| valid_until | string|null | yes | – |
| warnings | array | yes | – |
No examples provided.
swap_link Build a confirmation link ~260
Build a changenow.io link with the pair, the amount, the recipient address and the memo already filled in, so the user checks the numbers on the real page and presses Confirm themselves. Opening the link creates nothing. This is the recommended way to finish a swap: the user sees the rate and the address with their own eyes, which no amount of care in a chat transcript can replace. Use create_swap instead only when the user has explicitly approved this exact amount and address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Recipient address to prefill. The user can still change it on the page. |
| amount_from | string | – | Amount to prefill as the amount sent. |
| amount_to | string | – | Amount to prefill as the amount received. Implies a fixed rate on the page. |
| from | string | yes | Asset the user sends, canonical id. |
| locale | string | – | Two letter locale for the page, for example "es". English needs no locale. |
| memo | string | – | Memo or destination tag to prefill. |
| rate_type | string | – | Which rate the page opens with. |
| refund_address | string | – | Refund address to prefill. |
| to | string | yes | Asset the user receives, canonical id. |
| Name | Type | Req | Description |
|---|---|---|---|
| creates_order | boolean | yes | – |
| notes | array | yes | – |
| prefilled | array | yes | – |
| url | string | yes | – |
No examples provided.
validate_address Validate a recipient address ~159
Check a recipient address, and its memo when the asset needs one, against the format the network requires, before any order exists. Call this on every address the user gives. A valid-looking address on the wrong network is the one mistake in a swap that destroys the funds with no way back, so when the address belongs to another network the answer names that network instead of just refusing. A few assets carry no address format in the catalogue; for those the answer says the address could not be checked rather than calling it valid.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Recipient address to check. |
| asset | string | yes | Asset that will be received at this address, canonical id. |
| memo | string | – | Memo or destination tag, when the asset needs one. |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| format_checked | boolean | yes | – |
| memo_name | string|null | yes | – |
| memo_required | boolean | yes | – |
| memo_valid | boolean|null | yes | – |
| network | string | yes | – |
| network_hint | string|null | yes | – |
| reason | string|null | yes | – |
| valid | boolean | yes | – |
| warning | string|null | yes | – |
No examples provided.
What is the ChangeNOW MCP server?
ChangeNOW is an MCP server listed in the public MCP registry as io.changenow/crypto-swap. Quote, create and track cross-chain crypto swaps. Non-custodial exchange, no account, no KYC. This page covers its hosted endpoint (https://mcp.changenow.io/mcp).
Is the ChangeNOW MCP server safe to use?
ChangeNOW scores 84 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 ChangeNOW MCP server expose?
ChangeNOW exposes 7 tools: list_assets, get_asset, quote_swap, validate_address, swap_link, and 2 more. Their descriptions and schemas cost roughly 1,654 tokens of context every time the server is loaded.
Does the ChangeNOW MCP server require authentication?
No. We connected to ChangeNOW without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ChangeNOW MCP server still maintained?
ChangeNOW is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.