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.

RAVN

REMOTE · APP.RAVN.EXCHANGE

Cross-chain swap API for native Bitcoin, Solana and EVM chains. No API key, no custody.

0 this week 78 Trust /100

Last scanned (23 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 4 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 Security63
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3446 tokens (~344/item across 10 items; 10 tools + 0 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 Safety88
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ravn_btc_prepare_send" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 10 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
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.

  • 30 Oct 26 0
    • Tool “ravn_btc_coverage” rewrote its description, which is the text the model reads security
    • Tool “ravn_btc_coverage” changed its title: Which tokens actually route from native Bitcoin → How many BTC venues list each token cosmetic
  • 27 Oct 26 0
    • Server version: 1.0.2 → 1.0.3 functional
  • 22 Oct 26 0
    • Tool “ravn_quote” rewrote its description, which is the text the model reads security
    • “ravn_quote” reworded the description of “confidential” cosmetic
  • 19 Oct 26 0
    • “ravn_quote” reworded the description of “excludeVenues” cosmetic
    • “ravn_quote” reworded the description of “onlyVenues” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 18 Oct 26 0
    • Tool “ravn_execute” rewrote its description, which is the text the model reads security
    • “ravn_quote” added an optional parameter “timeoutMs” cosmetic
  • 17 Oct 26 0
    • “ravn_quote” added an optional parameter “onlyVenues” cosmetic
    • “ravn_status” reworded the description of “txHash” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 16 Oct 26 0
    • “ravn_quote” reworded the description of “refundAddress” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

  • 15 Oct 26 0
    • Tool “ravn_btc_prepare_send” rewrote its description, which is the text the model reads security
    • Schema quality: 265 → 293 ▼ functional
    • “ravn_btc_prepare_send” added an optional parameter “feeAddress” cosmetic
    • “ravn_btc_prepare_send” added an optional parameter “feeAmountSats” cosmetic
    • “ravn_btc_prepare_send” reworded the description of “amountSats” cosmetic
    • “ravn_btc_prepare_send” reworded the description of “toAddress” cosmetic
    • “ravn_status” reworded the description of “txHash” cosmetic
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 4 Nov 2026 · Probed https://app.ravn.exchange/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.ravn.exchange CN=YR1,O=Let's Encrypt,C=US 4 Sept 2026 3 Dec 2026 RSA 2048 SHA256-RSA 571e3c2ba0c3644e0b73e5d6207f4ff7f85
SANs: app.ravn.exchange
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.ravn.exchange. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
exchange. present 5011 8 Verified
ravn.exchange. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.ravn.exchange/api/mcp Verified 200
http (plaintext) http://app.ravn.exchange/api/mcp HTTPS enforced 308 https://app.ravn.exchange/api/mcp
MCP tools · 10 exposed · ~3,446 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
ravn_btc_coverage ~128

For a swap where native BTC is the source: how many BTC venues list each of ravn_tokens's tokens on `chainId`. A ranking hint (a token more venues list is more likely to keep routing through one venue's outage), not a gate: ravn_quote decides, and tokens off RAVN's list route from BTC too. BTC-as-source only.

NameTypeReqDescription
apiKeystring–Your RAVN API key, if you have one — raises your rate limit
chainIdintegeryesThe destination chain to check BTC-source coverage on

Structured output declared, but exposes no named fields.

No examples provided.

ravn_btc_prepare_send ~422

Turns a DEPOSIT-type ravn_execute result (deposit.address + deposit.amount) into a ready-to-sign PSBT, so you don't have to write your own UTXO selection and fee-estimation code. If that result also has a `fee` (an integrator fee RAVN collects beside the deposit), pass its fee.address as feeAddress and fee.amount as feeAmountSats: the PSBT then pays it as a second output of the same transaction, which is the only place RAVN looks for it. Fetches your UTXOs and the current network fee rate from mempool.space (public, no auth). RAVN never sees or touches a private key — sign the returned PSBT with your own wallet and broadcast it yourself. Only one signer is ever needed (unlike PSBT flows that require coordinating signatures across multiple UTXO-holding wallets), because every RAVN BTC-source venue resolves to a plain payment to the deposit address (plus RAVN's fee output, when there is one).

NameTypeReqDescription
amountSatsstringyesdeposit.amount from the ravn_execute DEPOSIT result, in satoshis
feeAddressstring–fee.address from the ravn_execute DEPOSIT result — REQUIRED whenever that result has a `fee`. RAVN's fee is paid as an extra output of this same transaction; leave it out and the fee is never paid
feeAmountSatsstring–fee.amount from the ravn_execute DEPOSIT result, in satoshis — pass together with feeAddress
feeRateSatsPerVbnumber–Omit to use mempool.space's current halfHourFee estimate
fromAddressstringyesYour Bitcoin address holding the UTXOs to spend — native SegWit (bc1q…) or Taproot (bc1p…) only
networkstring–Defaults to mainnet
toAddressstringyesdeposit.address from the ravn_execute DEPOSIT result

Structured output declared, but exposes no named fields.

No examples provided.

ravn_chains ~68

Every chain RAVN lists a token registry for (see ravn_tokens). Static, doesn't change per request, safe to cache instead of hardcoding a chain table.

NameTypeReqDescription
apiKeystring–Your RAVN API key, if you have one — raises your rate limit

Structured output declared, but exposes no named fields.

No examples provided.

ravn_execute ~471

Turn a quoteToken from ravn_quote into an execution payload. Returns one of three shapes (executionType): TRANSACTION (sign and broadcast yourself), SIGNATURE (sign, RAVN submits), or DEPOSIT (send the input asset to a given address). RAVN never takes custody of funds — you always sign or send from your own wallet. TRANSACTION and SIGNATURE may also include an `approval` — an ERC-20 approve() you must broadcast and wait to be MINED before the transaction/signature, or it fails (reverts on TRANSACTION; on SIGNATURE the order is accepted and silently never fills). Only present when the sold token needs it — omitted for native-coin sells and already-approved tokens. An `approval.reset` (Ethereum USDT holding a partial allowance) goes first, mined, then the approval. A result with `sandbox: true` is a test: send nothing from it.

NameTypeReqDescription
apiKeystring–Your RAVN API key, if you have one — raises your rate limit
destinationAddressstring–Late-bound output recipient, honoured by venues that bind at execution time (Chainflip, Garden, Layerswap, Mayan, NEAR Intents, Rift, RAVN two-hop routes). Every other venue fixes the recipient when…
quoteTokenstringyesThe quoteToken returned by ravn_quote
refundAddressstring–Late-bound refund recipient if the swap fails, honoured by venues that read one at execution time (Chainflip, Garden, NEAR Intents, Rift). Every other venue, Mayan, Layerswap and RAVN two-hop routes…

Structured output declared, but exposes no named fields.

No examples provided.

ravn_health ~39

Liveness check across every venue RAVN routes through — call before a swap if you want to know whether a route is degraded ahead of time.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

ravn_quote ~1,501

Get a swap quote from RAVN — same-chain or cross-chain, across 18 chains including native (non-wrapped) Bitcoin and Solana as source or destination. Free, no API key or payment required. Returns a quoteToken; pass it to ravn_execute to get a signable/broadcastable execution payload.

NameTypeReqDescription
allowNoMinimumboolean–Let venues that enforce no minimum (today Rift) race even though slippageBps is set. Their quotes carry slippage.noMinimum true and fill at the venue's own rate: slippageBps does not protect them
apiKeystring–Your RAVN API key, if you have one — raises your rate limit
confidentialboolean–Settle privately via NEAR Intents' Confidential Intents so the deposit and payout can't be linked on-chain. Through this MCP server only NEAR quotes it (NO_LIQUIDITY if it can't, never a public fallb…
destinationAddressstring–Where output should land, if different from userAddress. Required here, at quote time, to get an executable quote from Relay (Bitcoin as the source), THORChain (Bitcoin either direction), Across (a S…
excludeVenuesarray–Drop specific venues, e.g. a risk objection to one of them or ravn_health showing it degraded. An excluded venue is used nowhere in the route, including the steps of RAVN's multi-step routes (compose…
inputAmountstringyesPositive integer string, in the input token's smallest unit (no decimals)
inputChainIdintegeryesNumeric chain id, e.g. 1=Ethereum, 8453=Base, -1=Bitcoin, -2=Solana — see ravn_chains for the full list, or ravn_health for live venue status
inputTokenstringyesToken contract address, or 0xEeeeeEeeeEeEeeEeEeEeeeEEeeeeEeeeeeeeEEeE for the chain's native coin
onlyVenuesarray–Race only these venues, e.g. ["bebop"] for an RFQ-only race. Every other venue is left out (including ones RAVN adds later); excludeVenues still applies on top. It covers every venue RAVN routes your…
outputChainIdintegeryesNumeric chain id, e.g. 1=Ethereum, 8453=Base, -1=Bitcoin, -2=Solana — see ravn_chains for the full list, or ravn_health for live venue status
outputTokenstringyesToken contract address, or 0xEeeeeEeeeEeEeeEeEeEeeeEEeeeeEeeeeeeeEEeE for the chain's native coin
rankingModestring–best_output (default) picks the highest net output; fastest picks the quickest-settling quote within slippageBps
refundAddressstring–Where to refund the input asset if the swap fails. Selling native Bitcoin with userAddress set to a Bitcoin address and no refundAddress refunds to userAddress. Well-known sample addresses (e.g. bc1q…
slippageBpsinteger–Max acceptable slippage in basis points. Setting it drops venues that enforce no minimum (today Rift) from the race unless allowNoMinimum is true
timeoutMsinteger–The race's time limit in milliseconds, counted from its start: once it has passed and some venue has priced the swap, slower venues are left out (with none priced yet, the first price ends the wait;…
userAddressstringyesAddress the input asset will be sent from

Structured output declared, but exposes no named fields.

No examples provided.

ravn_status ~355

Poll the status of a swap by its quoteToken and ref from ravn_execute (statusRef, deposit address, or origin tx hash). Use the quoteToken execute returned — compose rebinds hop 1 onto hop 2's deposit. Status is authoritative where the venue exposes it; a swap the venue can't track reports 'unknown' rather than a guess.

NameTypeReqDescription
apiKeystring–Your RAVN API key, if you have one — raises your rate limit
quoteTokenstringyesThe quoteToken from ravn_quote — the venue is decoded from it
refstringyesstatusRef from ravn_execute when it returned one (always for DEPOSIT and SIGNATURE venues — it is the venue's own tracking key, which is not always the deposit address); otherwise the origin tx hash
txHashstring–The transaction that paid a fee the swap carries, where RAVN can't find it otherwise: a two-hop route's hop-1 tx, or the on-chain transaction that carried an execution's fee.transaction (Rift and pri…

Structured output declared, but exposes no named fields.

No examples provided.

ravn_submit_signature ~175

For a SIGNATURE-type ravn_execute result only: submit the signature(s) you collected (over typedData, and approvalData if present) to actually place the order. RAVN decodes the venue from quoteToken and routes to the right venue-specific submit path — you never touch a per-venue endpoint. Returns a statusRef — pass it to ravn_status as `ref` to poll this swap.

NameTypeReqDescription
apiKeystring–Your RAVN API key, if you have one — raises your rate limit
approvalSignaturestring–0x Gasless only: signature over approvalData, when ravn_execute returned one
quoteTokenstringyesThe quoteToken from ravn_quote
signaturestringyesSignature over the typedData from ravn_execute

Structured output declared, but exposes no named fields.

No examples provided.

ravn_tokens ~143

RAVN's own listed token registry for one chain — populate a token picker without hardcoding one. This is "what RAVN knows about and might route", not a per-pair routability guarantee for any specific pair; call ravn_quote to check that.

NameTypeReqDescription
apiKeystring–Your RAVN API key, if you have one — raises your rate limit
chainIdintegeryesNumeric chain id, e.g. 1=Ethereum, 8453=Base, -1=Bitcoin, -2=Solana — see ravn_chains for the full list, or ravn_health for live venue status

Structured output declared, but exposes no named fields.

No examples provided.

ravn_tokens_resolve ~144

Resolve an arbitrary token address to its metadata (symbol, name, decimals) via an on-chain read — for a paste-any-address flow, when the token isn't necessarily on ravn_tokens's list.

NameTypeReqDescription
addressstringyesToken contract address / mint to resolve
apiKeystring–Your RAVN API key, if you have one — raises your rate limit
chainIdintegeryesNumeric chain id, e.g. 1=Ethereum, 8453=Base, -1=Bitcoin, -2=Solana — see ravn_chains for the full list, or ravn_health for live venue status

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the RAVN MCP server?

RAVN is a hosted endpoint at https://app.ravn.exchange/api/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 · app.ravn.exchange

# add to Claude Code
claude mcp add --transport http exchange-ravn-ravn 'https://app.ravn.exchange/api/mcp'
Common questions

What is the RAVN MCP server?

RAVN is an MCP server listed in the public MCP registry as exchange.ravn/ravn. Cross-chain swap API for native Bitcoin, Solana and EVM chains. No API key, no custody. This page covers its hosted endpoint (https://app.ravn.exchange/api/mcp).

Is the RAVN MCP server safe to use?

RAVN scores 78 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 RAVN MCP server expose?

RAVN exposes 10 tools: ravn_quote, ravn_execute, ravn_submit_signature, ravn_status, ravn_health, and 5 more. Their descriptions and schemas cost roughly 3,446 tokens of context every time the server is loaded.

Does the RAVN MCP server require authentication?

No. We connected to RAVN without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RAVN MCP server still maintained?

RAVN is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.