Botgraph Swap MCP server
io.github.Dcroyalty/botgraph-swapDcroyaltystreamable-httpv1.0.0Scanned
Swap XRP to Bitcoin, Ethereum and USDC from any agent. Non-custodial, unsigned txs, OFAC-screened.
3 tools: 2 do something that can't be undone and 1 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- 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 Botgraph Swap MCP server can do
The Botgraph Swap MCP server is published by the GitHub account Dcroyalty. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (quote_swap and build_swap_tx), but cannot delete data. 1 tool only reads.
3 tools bring in text other people can write (quote_swap, build_swap_tx and swap_status); 2 tools can send data out of your system (quote_swap and build_swap_tx).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
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.
3 tools
Can't be undone 2Claude Code: ask
build_swap_txRe-quotes and returns ONE unsigned XRP Ledger Payment to THORChain that the caller signs and submits with its own wallet.Reads text others writeCan send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it Re-quotes and returns ONE unsigned XRP Ledger Payment to THORChain that the caller signs and submits with its own wallet. Same checks as swap.botgraph.org: OFAC screen on both addresses, minimum enforced, memo in MemoData only, no DestinationTag, LastLedgerSequence before the quote expiry. We never sign, submit or hold funds.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
quote_swapLive THORChain quote for swapping XRP to BTC, ETH or USDC: expected amount out, every fee (ours is 0.5%), minimum size and expiry.Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends 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 input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "quote_swap" 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 input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Live THORChain quote for swapping XRP to BTC, ETH or USDC: expected amount out, every fee (ours is 0.5%), minimum size and expiry. Screens the destination against the OFAC list. Read-only; builds nothing.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
swap_statusOutcome of a swap by its XRP Ledger transaction hash: XRP payment validated, THORChain observed it, swapping, coins sent (with outbound hashes), or refunded.Reads text others writeNo findings
Why it is in this group
- The name "swap_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 Outcome of a swap by its XRP Ledger transaction hash: XRP payment validated, THORChain observed it, swapping, coins sent (with outbound hashes), or refunded.
Annotations the server declares
- 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 write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- 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 15, 2026, 13:19 UTC, unchanged since Nov 15, 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
- 2
- 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 2 tools that change things (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://swap.botgraph.org/mcp: tools/list returned 3 tools to an anonymous client, including quote_swap (irreversible), build_swap_tx (irreversible)
Findings
Matches of fixed checks, with the text they matched.
- Warnquote_swap
The server marks "quote_swap" 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 input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http botgraph-swap https://swap.botgraph.org/mcpclaude mcp add --transport http botgraph-swap https://swap.botgraph.org/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__botgraph-swap__swap_status"
],
"ask": [
"mcp__botgraph-swap__quote_swap",
"mcp__botgraph-swap__build_swap_tx"
],
"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 botgraph-swap. Review it before you use it.
Capability tags behind 3 rules
- mcp__botgraph-swap__quote_swap untrusted-input, outbound
- mcp__botgraph-swap__build_swap_tx untrusted-input, outbound
- mcp__botgraph-swap__swap_status untrusted-input
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/io.github.Dcroyalty/botgraph-swap/verify?hash=4f3dbc882c5de80b449cfb299e93a7eca5bc87b4ac35948b385351756fddd015" | jq -e '.changed == false'Pinned hash 4f3dbc882c5d, from Nov 14, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Dcroyalty/botgraph-swap/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Dcroyalty/botgraph-swap)Source: MCP Registry. Synced Nov 14, 2026, 21:17 UTC.
Botgraph Swap MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Botgraph Swap MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Botgraph Swap MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Botgraph Swap MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: quote_swap and build_swap_tx.
What tools does the Botgraph Swap MCP server have?
- 3 tools: 2 irreversible, 1 read. quote_swap, build_swap_tx and swap_status.
Does the Botgraph Swap MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Botgraph Swap MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): quote_swap and build_swap_tx.
Has the Botgraph Swap MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.