Skip to content

swap-mcp server

io.github.ShieldZCash/swap-mcpShieldZCashstreamable-httpv0.1.1Scanned

Non-custodial cross-chain swaps for AI agents: live route quotes and deposit swaps on 40+ chains.

5 tools: 2 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 2 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 swap-mcp server can do

The swap-mcp server is published by the GitHub account ShieldZCash. It has 5 tools. It can create or change data (2 tools: create_swap and report_deposit), but cannot delete data. 3 tools only read.

5 tools bring in text other people can write (list_assets, get_quote, create_swap and 2 more).

The fixed checks matched 4 findings (base64-blob). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 0.1.1.

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.

5 tools

Changes things 2Claude Code: ask
  • create_swapOpen a non-custodial swap and return a one-time deposit address.Reads text others write2 findings

    Why it is in this group

    • The name "create_swap" says "create": 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.

    Findings

    • Warn

      The input schema at properties.from_asset.description contains a 42-character base64 string.

      Matched text

      inputSchema.properties.from_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

      What this check looks for
    • Warn

      The input schema at properties.to_asset.description contains a 42-character base64 string.

      Matched text

      inputSchema.properties.to_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

      What this check looks for
    Description, as the server wrote it
    Open a non-custodial swap and return a one-time deposit address. Use it only after the user has seen a quote, agreed to the amount and route, and given you both addresses. from_asset, to_asset and amount mean the same as in get_quote: pass the values the user agreed to. destination_address must be on to_asset's chain and refund_address on from_asset's chain, usually the sending wallet; BTC to ZEC, for example, needs a Zcash payout address and a Bitcoin refund address. NEVER invent, guess or reuse addresses from elsewhere in the conversation. Set protocol only to keep the route the user picked from get_quote's alternatives. The tool re-quotes with the real addresses, sets the minimum output from that quote and returns an error rather than a deposit if the amounts changed. Nothing moves until the user sends exactly send_exactly from their own wallet before expires_at; the server never holds keys or signs. If the swap cannot complete, funds go back to refund_address. Each call creates a new deposit address, so do not call it again to "retry" a swap the user already funded. Rate-limited per caller (about 6 swaps in a burst, then one every 20 seconds).

    Annotations the server declares

    • title: Create a swap (deposit address)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • report_depositTell the router the hash of the deposit transaction the user just sent, so the swap is detected immediately instead of on the next scan.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.

    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
    Tell the router the hash of the deposit transaction the user just sent, so the swap is detected immediately instead of on the next scan. Optional: swaps are detected without it, and it never moves funds. swap_id is the id create_swap returned for this swap. tx_hash is the hash of the transaction that sent funds to that swap's deposit_address on the source chain (0x-prefixed on EVM chains); never pass a payout hash or another swap's id. An unknown swap_id returns an error. Use it once, right after the user shares their tx hash, then follow up with get_swap_status. Calling it again with the same hash is harmless.

    Annotations the server declares

    • title: Report a deposit transaction
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • get_quoteGet live prices for swapping one asset into another, across chains, by racing NEAR Intents, Chainflip, Relay, MAYAChain, BOB Gateway and Garden.Reads text others write2 findings

    Why it is in this group

    • The name "get_quote" says "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.from_asset.description contains a 42-character base64 string.

      Matched text

      inputSchema.properties.from_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

      What this check looks for
    • Warn

      The input schema at properties.to_asset.description contains a 42-character base64 string.

      Matched text

      inputSchema.properties.to_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

      What this check looks for
    Description, as the server wrote it
    Get live prices for swapping one asset into another, across chains, by racing NEAR Intents, Chainflip, Relay, MAYAChain, BOB Gateway and Garden. Returns the best route and the alternatives, with output after fees, guaranteed minimum, all-in cost % and ETA. Use it to answer "how much X do I get for Y" and to show the user the numbers before create_swap. It creates nothing and needs no addresses. from_asset is what the user sends and to_asset what they receive; they may sit on different chains. Give each as an exact asset id or CHAIN.SYMBOL; when a shorthand is ambiguous (bridged USDC, for example) the error lists the matching ids, and list_assets finds ids by name or chain. amount is how much from_asset the user sends, in from_asset's own units, never in to_asset or USD. Quotes move with the market, so do not reuse one after a few minutes; create_swap re-quotes on its own. Shieldz charges a flat 0.15% (already in amount_out). Errors explain unsupported pairs or minimum and maximum amounts. Rate-limited per caller (roughly 20 quotes in a burst, then one every 2 seconds).

    Annotations the server declares

    • title: Quote a cross-chain swap
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • get_swap_statusLook up a swap made with create_swap by its swap_id and explain where it is: PENDING (no deposit seen yet), PROCESSING, SUCCESS, FAILED, REFUNDED, INCOMPLETE_DEPOSIT (less than req…Reads text others writeNo findings

    Why it is in this group

    • The name "get_swap_status" says "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.
    Description, as the server wrote it
    Look up a swap made with create_swap by its swap_id and explain where it is: PENDING (no deposit seen yet), PROCESSING, SUCCESS, FAILED, REFUNDED, INCOMPLETE_DEPOSIT (less than required arrived) or EXPIRED (address closed, never send to it). swap_id is the protocol-prefixed id create_swap returned, such as near:<deposit address> or chainflip:<block>-<network>-<channel>; pass it unchanged, prefix included. Returns amounts in normal units and the deposit, payout and refund transaction links. A malformed id is rejected before any request, an unknown one returns "No swap with that id", and a router outage returns an error to retry later. Use it when the user asks whether their swap arrived. Read-only and safe to repeat; poll every 30 seconds or more, not in a tight loop.

    Annotations the server declares

    • title: Check swap status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_assetsSearch the 340+ assets on 40+ chains that Shieldz Swap can route and return their exact asset ids.Reads text others writeNo findings

    Why it is in this group

    • The name "list_assets" says "list": 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
    Search the 340+ assets on 40+ chains that Shieldz Swap can route and return their exact asset ids. Use it when you are unsure of an id or which chains support a token (e.g. every chain that has USDC). Skip it for common native coins: get_quote and create_swap already accept shorthand like ZEC.ZEC or BTC.BTC. With no filters it also returns the list of chain codes. Read-only; the list is cached for 60 seconds.

    Annotations the server declares

    • title: List swappable assets
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: 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 or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:19 UTC, unchanged since Nov 21, 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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://swap.shieldz.cash/mcp: tools/list returned 5 tools to an anonymous client, including create_swap (write), report_deposit (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

4 warn
  • The input schema at properties.from_asset.description contains a 42-character base64 string.

    Matched text

    inputSchema.properties.from_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

    What this check looks for
  • The input schema at properties.to_asset.description contains a 42-character base64 string.

    Matched text

    inputSchema.properties.to_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

    What this check looks for
  • The input schema at properties.from_asset.description contains a 42-character base64 string.

    Matched text

    inputSchema.properties.from_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

    What this check looks for
  • The input schema at properties.to_asset.description contains a 42-character base64 string.

    Matched text

    inputSchema.properties.to_asset.description: "..._assets ("BASE.USDC-0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913") or CHAIN.SYMBOL s..."

    What this check looks for

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 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http swap https://swap.shieldz.cash/mcp
claude mcp add --transport http swap https://swap.shieldz.cash/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__swap__list_assets",
      "mcp__swap__get_quote",
      "mcp__swap__get_swap_status"
    ],
    "ask": [
      "mcp__swap__create_swap",
      "mcp__swap__report_deposit"
    ],
    "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 swap. Review it before you use it.

Capability tags behind 5 rules
  • mcp__swap__list_assets untrusted-input
  • mcp__swap__get_quote untrusted-input
  • mcp__swap__create_swap untrusted-input
  • mcp__swap__get_swap_status untrusted-input
  • mcp__swap__report_deposit 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.ShieldZCash/swap-mcp/verify?hash=6ef0021cbb4b19097a4a45aa1098c7a33ab93553ad374da6cecfca09ef941400" | jq -e '.changed == false'

Pinned hash 6ef0021cbb4b, from Nov 21, 2026, 14: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.ShieldZCash/swap-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ShieldZCash/swap-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ShieldZCash/swap-mcp.svg)](https://radar.anlyon.com/servers/io.github.ShieldZCash/swap-mcp)

Source: MCP Registry · repository. Synced Nov 21, 2026, 14:18 UTC.

swap-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the swap-mcp server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 4 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 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 swap-mcp server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the swap-mcp server have?

5 tools: 2 write, 3 read. create_swap, report_deposit, list_assets, get_quote and get_swap_status.

Does the swap-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the swap-mcp server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the swap-mcp server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.