Skip to content

Crypto Support Desk (zh/en) MCP server

dev.workers.agent-arena-base.crypto-support-kit/support-deskcrypto-support-kit.agent-arena-base.workers.devstreamable-httpv1.1.1Scanned

Bilingual zh/en crypto support replies + free address checks. Full kit: one $5 USDC/USDT transfer.

6 tools: 2 do something that can't be undone, 1 change things and 3 only read.

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

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.
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 Crypto Support Desk (zh/en) MCP server can do

The Crypto Support Desk (zh/en) MCP server is published by crypto-support-kit.agent-arena-base.workers.dev, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (payment_options and check_crypto_address) and create or change data (1 tool: check_address_poisoning), but cannot delete data. 3 tools only read.

1 tool reads private data (get_support_reply); 1 tool brings in text other people can write (get_support_reply); 1 tool can send data out of your system (check_crypto_address). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.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.

6 tools

Can't be undone 2Claude Code: ask
  • check_crypto_addressFREE, offline.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.recipient): 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

    • outboundThe input takes a destination (input.recipient): what the tool writes goes there.

    Findings

    • Warn

      The server marks "check_crypto_address" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.recipient): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    FREE, offline. Before a user sends or a support agent confirms a deposit address: detects the address family (EVM, TRON, Bitcoin, Solana, TON, XRP, ...), validates checksum and format, cross-checks it against the intended network, flags missing memo/tag for exchange deposits and known token-contract addresses. Verdict: ok, caution, do_not_send or incomplete. Cannot see balances or sanctions lists.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • payment_optionsFREE.1 finding

    Why it is in this group

    • The name "payment_options" says "payment": a word that usually means money moves, which cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "payment_options" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "payment_options" says "payment": a word that usually means money moves, which cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    FREE. Price ($5.00), receiving addresses and the exact USDC/USDT contracts accepted on each chain, and how to redeem with pay_tx. Plain transfer from any wallet or exchange withdrawal; no x402 client and no account needed.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Changes things 1Claude Code: ask
  • check_address_poisoningFREE, offline.No 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.
    Description, as the server wrote it
    FREE, offline. Compares a destination address with addresses the user already trusts (address book, past counterparties) and flags look-alikes that share the first and last characters but differ in the middle: the address-poisoning scam pattern.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_support_replyReturns the ready-to-send reply for one scenario: what to ask the user first, the reply in Chinese and in English, and an internal note for the agent.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_support_reply" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "get_support_reply" says "get" and "reply": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "return" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    Returns the ready-to-send reply for one scenario: what to ask the user first, the reply in Chinese and in English, and an internal note for the agent. Scenarios 01, 04, 11, 12, 22 are FREE. Others return a preview plus payment instructions until you pass pay_tx: one plain transfer of >= $5.00 USDC/USDT (Base, Arbitrum, OP, Polygon, BSC, Ethereum or Solana; not x402) unlocks all scenarios, and scenario="all" returns the whole kit.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_support_scenariosFREE.No findings

    Why it is in this group

    • The name "list_support_scenarios" says "list": a word for reading.
    Description, as the server wrote it
    FREE. All 25 bilingual support scenarios (id, title, free or paid). Scenarios 01, 04, 11, 12, 22 are free; the rest unlock with one $5.00 USDC/USDT transfer.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_support_scenariosFREE.No findings

    Why it is in this group

    • The name "search_support_scenarios" says "search": a word for reading.
    Description, as the server wrote it
    FREE. Find the right support scenario for a user's problem, in English or Chinese (e.g. "sent USDT on the wrong network", "忘填memo", "fake support DM", "seed phrase leaked"). Returns up to 5 scenario ids with titles and whether each is free.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__support-desk__check_crypto_address"
    ]
  }
}

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:24 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
3
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 3 tools that change things (2 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://crypto-support-kit.agent-arena-base.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including payment_options (irreversible), check_crypto_address (irreversible), check_address_poisoning (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "payment_options" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "payment_options" says "payment": a word that usually means money moves, which cannot be taken back.

    What this check looks for
  • The server marks "check_crypto_address" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.recipient): what it sends cannot be taken back.

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

claude mcp add --transport http support-desk https://crypto-support-kit.agent-arena-base.workers.dev/mcp
claude mcp add --transport http support-desk https://crypto-support-kit.agent-arena-base.workers.dev/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__support-desk__search_support_scenarios",
      "mcp__support-desk__list_support_scenarios",
      "mcp__support-desk__get_support_reply"
    ],
    "ask": [
      "mcp__support-desk__payment_options",
      "mcp__support-desk__check_crypto_address",
      "mcp__support-desk__check_address_poisoning"
    ],
    "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 support-desk. Review it before you use it.

Capability tags behind 2 rules
  • mcp__support-desk__get_support_reply private-data, untrusted-input
  • mcp__support-desk__check_crypto_address 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/dev.workers.agent-arena-base.crypto-support-kit/support-desk/verify?hash=34258df66a31a41dc8010175a339ab2cf578d2980b8eebc6348b503b8ad4c7c2" | jq -e '.changed == false'

Pinned hash 34258df66a31, from Nov 21, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.agent-arena-base.crypto-support-kit/support-desk/changes.xml

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

Badge

Anlyon Radar badge for dev.workers.agent-arena-base.crypto-support-kit/support-desk
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.agent-arena-base.crypto-support-kit/support-desk.svg)](https://radar.anlyon.com/servers/dev.workers.agent-arena-base.crypto-support-kit/support-desk)

Source: MCP Registry. Synced Nov 21, 2026, 08:17 UTC.

Crypto Support Desk (zh/en) MCP server: questions and answers

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

Is the Crypto Support Desk (zh/en) MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 2 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 Crypto Support Desk (zh/en) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Crypto Support Desk (zh/en) MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: payment_options and check_crypto_address.

What tools does the Crypto Support Desk (zh/en) MCP server have?

6 tools: 2 irreversible, 1 write, 3 read. payment_options, check_crypto_address, check_address_poisoning, search_support_scenarios, list_support_scenarios and get_support_reply.

Does the Crypto Support Desk (zh/en) MCP server need sign-in or OAuth?

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

Does the Crypto Support Desk (zh/en) 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): check_crypto_address.

Has the Crypto Support Desk (zh/en) MCP server changed its tools?

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