RAVN MCP server
exchange.ravn/ravnravn.exchangestreamable-httpv1.0.3Scanned
Cross-chain swap API for native Bitcoin, Solana and EVM chains. No API key, no custody.
10 tools: 1 do something that can't be undone, 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 10
- Can send data out · 1
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RAVN MCP server can do
The RAVN MCP server is published by ravn.exchange, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (ravn_btc_prepare_send) and create or change data (6 tools: ravn_execute, ravn_submit_signature, ravn_health, ravn_tokens and 2 more), but cannot delete data. 3 tools only read.
10 tools bring in text other people can write (ravn_quote, ravn_execute, ravn_submit_signature and 7 more); 1 tool can send data out of your system (ravn_btc_prepare_send).
The fixed checks matched 3 findings (base64-blob and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.0.3.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Can't be undone 1Claude Code: ask
ravn_btc_prepare_sendTurns 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.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "ravn_btc_prepare_send" says "send": a word for sending, and what is sent cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "ravn_btc_prepare_send" says "send": it sends or publishes something to other people.
Findings
- Warn
The server marks "ravn_btc_prepare_send" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "ravn_btc_prepare_send" says "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it 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).
Annotations the server declares
- title: Prepare a signable Bitcoin transaction for a RAVN DEPOSIT
- readOnlyHint: true
- openWorldHint: true
Changes things 6Claude Code: ask
ravn_btc_coverageFor a swap where native BTC is the source: how many BTC venues list each of ravn_tokens's tokens on `chainId`.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: How many BTC venues list each token
- readOnlyHint: true
- openWorldHint: true
ravn_chainsEvery chain RAVN lists a token registry for (see ravn_tokens).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List every chain RAVN supports
- readOnlyHint: true
- openWorldHint: true
ravn_executeTurn a quoteToken from ravn_quote into an execution payload.Reads text others writeNo findings
Why it is in this group
- The name "ravn_execute" says "execute": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Execute a RAVN swap quote
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
ravn_healthLiveness check across every venue RAVN routes through — call before a swap if you want to know whether a route is degraded ahead of time.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check RAVN venue health
- readOnlyHint: true
- openWorldHint: true
ravn_submit_signatureFor a SIGNATURE-type ravn_execute result only: submit the signature(s) you collected (over typedData, and approvalData if present) to actually place the order.Reads text others writeNo findings
Why it is in this group
- The name "ravn_submit_signature" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Submit a signed RAVN order
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
ravn_tokensRAVN's own listed token registry for one chain — populate a token picker without hardcoding one.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List RAVN's token registry for a chain
- readOnlyHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
ravn_quoteGet a swap quote from RAVN — same-chain or cross-chain, across 19 chains including native (non-wrapped) Bitcoin and Solana as source or destination.Reads text others write2 findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The input schema at properties.inputToken.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.inputToken.description: "...ontract address, or 0xEeeeeEeeeEeEeeEeEeEeeeEEeeeeEeeeeeeeEEeE for the chain's nat..."
- Warn
The input schema at properties.outputToken.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.outputToken.description: "...ontract address, or 0xEeeeeEeeeEeEeeEeEeEeeeEEeeeeEeeeeeeeEEeE for the chain's nat..."
Description, as the server wrote it Get a swap quote from RAVN — same-chain or cross-chain, across 19 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.
Annotations the server declares
- title: Get a RAVN swap quote
- readOnlyHint: true
- openWorldHint: true
ravn_statusPoll the status of a swap by its quoteToken and ref from ravn_execute (statusRef, deposit address, or origin tx hash).Reads text others writeNo findings
Why it is in this group
- The name "ravn_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check RAVN swap status
- readOnlyHint: true
- openWorldHint: true
ravn_tokens_resolveResolve 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 l…Reads text others writeNo findings
Why it is in this group
- The name "ravn_tokens_resolve" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Resolve a token address to its metadata
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write10
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.ravn.exchange/api/mcp: tools/list returned 10 tools to an anonymous client, including ravn_btc_prepare_send (irreversible), ravn_execute (write), ravn_submit_signature (write), ravn_health (write), ravn_tokens (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
- Warnravn_quote
The input schema at properties.inputToken.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.inputToken.description: "...ontract address, or 0xEeeeeEeeeEeEeeEeEeEeeeEEeeeeEeeeeeeeEEeE for the chain's nat..."
- Warnravn_quote
The input schema at properties.outputToken.description contains a 42-character base64 string.
What this check looks forMatched text
inputSchema.properties.outputToken.description: "...ontract address, or 0xEeeeeEeeeEeEeeEeEeEeeeEEeeeeEeeeeeeeEEeE for the chain's nat..."
The server marks "ravn_btc_prepare_send" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "ravn_btc_prepare_send" says "send": a word for sending, and what is sent cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:ravn_quoteOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:ravn_btc_coverageChanges thingstitledescriptionannotations
- Changed:ravn_quoteOnly readsdescriptioninputSchema
Install
Pinned to version 1.0.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http ravn https://app.ravn.exchange/api/mcpclaude mcp add --transport http ravn https://app.ravn.exchange/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ravn__ravn_quote",
"mcp__ravn__ravn_status",
"mcp__ravn__ravn_tokens_resolve"
],
"ask": [
"mcp__ravn__ravn_execute",
"mcp__ravn__ravn_submit_signature",
"mcp__ravn__ravn_health",
"mcp__ravn__ravn_tokens",
"mcp__ravn__ravn_btc_coverage",
"mcp__ravn__ravn_chains",
"mcp__ravn__ravn_btc_prepare_send"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ravn. Review it before you use it.
Capability tags behind 10 rules
- mcp__ravn__ravn_quote untrusted-input
- mcp__ravn__ravn_execute untrusted-input
- mcp__ravn__ravn_submit_signature untrusted-input
- mcp__ravn__ravn_status untrusted-input
- mcp__ravn__ravn_health untrusted-input
- mcp__ravn__ravn_tokens untrusted-input
- mcp__ravn__ravn_tokens_resolve untrusted-input
- mcp__ravn__ravn_btc_coverage untrusted-input
- mcp__ravn__ravn_chains untrusted-input
- mcp__ravn__ravn_btc_prepare_send untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/exchange.ravn/ravn/verify?hash=e8abcbcbe5f1fbbab403c33ae5dc5f94e0fbbfe2f64924702908c342282dace2" | jq -e '.changed == false'Pinned hash e8abcbcbe5f1, from Nov 11, 2026, 12:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/exchange.ravn/ravn/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/exchange.ravn/ravn)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.
RAVN MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RAVN MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 7 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RAVN MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the RAVN MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: ravn_btc_prepare_send.
What tools does the RAVN MCP server have?
- 10 tools: 1 irreversible, 6 write, 3 read. ravn_btc_prepare_send, ravn_execute, ravn_submit_signature, ravn_health, ravn_tokens, ravn_btc_coverage, ravn_chains, ravn_quote and 2 more.
Does the RAVN MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RAVN MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ravn_btc_prepare_send.
Has the RAVN MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.