Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ChangeNOW

REMOTE · MCP.CHANGENOW.IO

Quote, create and track cross-chain crypto swaps. Non-custodial exchange, no account, no KYC.

Available components

0 this week 86 Trust /100

Last scanned (14 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 2 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 21 Nov 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 13 Nov 2026 11 Feb 2027 ECDSA 256 ECDSA-SHA256 b07b753c8725f22913bf6178697ea321
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. DS published 38690 8 Verified
changenow.io. No DS 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
MCP tools · 7 exposed · ~1,654 tokens

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 →

Tool Tokens
check_swap_status ~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.

NameTypeReqDescription
idstringyesOrder id returned by create_swap.
sub_idstring–Sub order id, for an order the provider split in two.
NameTypeReqDescription
amount_fromstring|nullyes–
amount_tostring|nullyes–
created_atstring|nullyes–
deposit_received_atstring|nullyes–
expected_amount_fromstring|nullyes–
expected_amount_tostring|nullyes–
fromstringyes–
idstringyes–
payin_addressstringyes–
payin_extra_idstring|nullyes–
payin_hashstring|nullyes–
payout_addressstringyes–
payout_extra_idstring|nullyes–
payout_hashstring|nullyes–
providerstringyes–
refund_addressstring|nullyes–
refund_amountstring|nullyes–
refund_hashstring|nullyes–
refund_memostring|nullyes–
stage_explanationstringyes–
statusstringyes–
tostringyes–
track_urlstringyes–
updated_atstring|nullyes–
valid_untilstring|nullyes–

No examples provided.

create_swap ~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.

NameTypeReqDescription
addressstringyesAddress that receives the swapped asset. Check it with validate_address first; a wrong network here loses the funds.
amount_fromstring–Amount the user sends. Pass this or amount_to, never both.
amount_tostring–Amount the user wants to receive. Requires rate_id from quote_swap.
contact_emailstring–Optional email for status notifications about this order.
fromstringyesAsset the user sends, canonical id, for example "eth.eth".
memostring–Memo or destination tag for the recipient address, when the asset needs one.
promo_codestring–Promo code to apply, if the user has one.
rate_idstring–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_addressstring–Where the deposit returns if the swap cannot complete. Strongly recommended: without it a failed swap needs support.
refund_memostring–Memo for the refund address.
tostringyesAsset the user receives, canonical id, for example "usdt.trx".
NameTypeReqDescription
amount_fromstring|nullyes–
amount_tostring|nullyes–
created_atstring|nullyes–
fromstringyes–
idstringyes–
payin_addressstringyes–
payin_extra_idstring|nullyes–
payout_addressstringyes–
payout_extra_idstring|nullyes–
providerstringyes–
rate_typestringyes–
refund_addressstring|nullyes–
refund_memostring|nullyes–
statusstring|nullyes–
tostringyes–
track_urlstringyes–
valid_untilstring|nullyes–
warningsarrayyes–

No examples provided.

get_asset ~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.

NameTypeReqDescription
assetstringyesCanonical id "usdt.trx". A legacy ticker "usdttrc20" or a page slug "tether-trc20" is also accepted.
NameTypeReqDescription
address_regexstring|nullyes–
assetstringyes–
decimalsnumber|nullyes–
explorer_address_urlstring|nullyes–
explorer_tx_urlstring|nullyes–
fixed_ratebooleanyes–
kindstringyes–
memobooleanyes–
memo_namestring|nullyes–
memo_regexstring|nullyes–
namestringyes–
networkstringyes–
price_usdnumber|nullyes–
slugstring|nullyes–
tickerstringyes–
token_contractstring|nullyes–
warning_receivestring|nullyes–
warning_sendstring|nullyes–

No examples provided.

list_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.

NameTypeReqDescription
cursorstring–Cursor from next_cursor of the previous page. Only needed when has_more is true.
fixed_rateboolean–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.
kindstring–crypto for swappable coins and tokens, fiat for currencies that can only start a purchase, all for both.
limitinteger–How many assets to return. Default 50, maximum 500.
networkstring–Keep only assets on this network, for example "eth", "trx", "sol".
popularboolean–Return the short curated list. Use this to answer "what can I swap" without paging.
qstring–Substring search over canonical id, legacy ticker, name and network. Case insensitive. Example: "usdt", "bitcoin", "tron".
NameTypeReqDescription
assetsarrayyes–
catalogue_versionstringyes–
has_morebooleanyes–
next_cursorstring|nullyes–
returnednumberyes–
totalnumberyes–

No examples provided.

quote_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.

NameTypeReqDescription
amount_fromstring–Amount the user sends, as a decimal string. Pass this or amount_to, never both.
amount_tostring–Amount the user wants to receive, as a decimal string. The answer then says how much to send.
fromstringyesAsset the user sends, canonical id, for example "btc.btc".
promo_codestring–Promo code to apply, if the user has one.
rate_typestring–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…
tostringyesAsset the user receives, canonical id, for example "usdt.trx".
NameTypeReqDescription
amount_fromstring|nullyes–
amount_tostring|nullyes–
fromstringyes–
from_namestringyes–
high_network_feebooleanyes–
limits_instringyes–
max_amountstring|nullyes–
min_amountstring|nullyes–
providerstringyes–
quote_idstring|nullyes–
ratestring|nullyes–
rate_idstring|nullyes–
rate_typestringyes–
speed_forecast_minutesstring|nullyes–
tostringyes–
to_namestringyes–
valid_untilstring|nullyes–
warningsarrayyes–

No examples provided.

swap_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.

NameTypeReqDescription
addressstring–Recipient address to prefill. The user can still change it on the page.
amount_fromstring–Amount to prefill as the amount sent.
amount_tostring–Amount to prefill as the amount received. Implies a fixed rate on the page.
fromstringyesAsset the user sends, canonical id.
localestring–Two letter locale for the page, for example "es". English needs no locale.
memostring–Memo or destination tag to prefill.
rate_typestring–Which rate the page opens with.
refund_addressstring–Refund address to prefill.
tostringyesAsset the user receives, canonical id.
NameTypeReqDescription
creates_orderbooleanyes–
notesarrayyes–
prefilledarrayyes–
urlstringyes–

No examples provided.

validate_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.

NameTypeReqDescription
addressstringyesRecipient address to check.
assetstringyesAsset that will be received at this address, canonical id.
memostring–Memo or destination tag, when the asset needs one.
NameTypeReqDescription
assetstringyes–
format_checkedbooleanyes–
memo_namestring|nullyes–
memo_requiredbooleanyes–
memo_validboolean|nullyes–
networkstringyes–
network_hintstring|nullyes–
reasonstring|nullyes–
validbooleanyes–
warningstring|nullyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http io-changenow-crypto-swap 'https://mcp.changenow.io/mcp'
Common questions

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 86 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ChangeNOW MCP server?

VerifyMCP ran 13 checks on ChangeNOW, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.