send21 MCP server
io.github.send21io/mcpsend21iostreamable-httpv1.7.0Scanned
Crypto pay links and API for people and AI agents. BTC, Lightning, USDC, USDT, EURC, SOL, ETH.
14 tools: 1 do something that can't be undone, 4 change things and 9 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 0
- No 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 send21 MCP server can do
The send21 MCP server is published by the GitHub account send21io. It has 14 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_payment_request) and create or change data (4 tools: propose_receiving_address, submit_lightning_proof, create_account and create_draft), but cannot delete data. 9 tools only read.
1 tool reads private data (get_account_status); 3 tools bring in text other people can write (get_account_status, create_account and get_draft_status).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.7.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.
14 tools
Can't be undone 1Claude Code: ask
create_payment_requestCreate a payment request / checkout pay link (you are the RECEIVER asking to get paid).No findings
Why it is in this group
- The name "create_payment_request" says "create": a word for a change.
- The name "create_payment_request" also says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Create a payment request / checkout pay link (you are the RECEIVER asking to get paid). Price in any of 161 fiat currencies; the payer opens the returned payPath, picks one of the offered currencies (rate locks then), and pays a single QR-scannable transfer straight to your address. On accounts with the policy ApprovedOnly (see get_account_status) every address must be one of the owner's approved receiving addresses; otherwise the answer is 422 address_not_approved and nothing is created (propose it with propose_receiving_address). Requires scope drafts:write.
Annotations the server declares
- title: Create pay link
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
Changes things 4Claude Code: ask
create_accountCreate a send21 account for your human owner, without a key.Reads text others writeNo findings
Why it is in this group
- The name "create_account" 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.
Description, as the server wrote it Create a send21 account for your human owner, without a key. The owner gets an email with a link to take the account over; until they do, nothing can be created. Returns a bootstrap API key ONCE (save it and send it as Authorization: Bearer on every later call; reconnect this MCP client with it). The key can read, propose addresses and check get_account_status; it can create pay links only after the owner took the account over and approved a receiving address you proposed. Agents onboard themselves; humans approve where the money lands. If the email already has an account, ask the owner for an API key instead.
Annotations the server declares
- title: Create send21 account for owner
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
- readOnlyHint: false
create_draftCreate a non-custodial payment draft (you are the SENDER paying a receiver address).No findings
Why it is in this group
- The name "create_draft" says "create": a word for a change.
Description, as the server wrote it Create a non-custodial payment draft (you are the SENDER paying a receiver address). Amount is either exact base units (sats for BTC, micro-units for stablecoins, lamports for SOL, gwei for ETH) via amountBaseUnits, or fiat-pegged via fiatCurrency+fiatAmount with the exchange rate locked at creation. Returns the draft incl. id, amounts, fee, and status. Funds move only when the sender signs in their own wallet. send21 never holds keys. On accounts with the policy ApprovedOnly the receiver must be an address the owner approved (422 address_not_approved otherwise). Requires scope drafts:write.
Annotations the server declares
- title: Create payment draft
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
propose_receiving_addressPropose an address for the owner to approve: one of the owner's own receiving addresses (for pay links) or the address of someone the owner pays (for drafts).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.
Description, as the server wrote it Propose an address for the owner to approve: one of the owner's own receiving addresses (for pay links) or the address of someone the owner pays (for drafts). It is saved unapproved and the owner gets an email. On accounts with the policy ApprovedOnly, API keys can only use approved addresses, and only the owner can approve one, signed in to the send21 app with a passkey or authenticator code. No key can approve an address. Requires scope addressbook:write.
Annotations the server declares
- title: Propose receiving address
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
- readOnlyHint: false
submit_lightning_proofConfirm a paid Lightning draft with its proof of payment: the 64-character preimage the paying wallet shows after a Lightning payment.No findings
Why it is in this group
- The name "submit_lightning_proof" says "submit": a word for a change.
Description, as the server wrote it Confirm a paid Lightning draft with its proof of payment: the 64-character preimage the paying wallet shows after a Lightning payment. Needed for drafts with a pasted bolt11 invoice, and for Lightning addresses whose provider does not report payments. send21 checks that SHA-256 of the preimage equals the invoice's payment hash; the draft then confirms within about 30 seconds. Requires scope drafts:write.
Annotations the server declares
- title: Submit Lightning payment proof
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: false
Only reads 9Show 9 read-only tools
get_account_statusWhat stands between you and a live pay link: whether the owner's email is confirmed, the receiving-address policy, how many addresses are approved or waiting for approval, unsettle…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_account_status" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it What stands between you and a live pay link: whether the owner's email is confirmed, the receiving-address policy, how many addresses are approved or waiting for approval, unsettled fees, your key's scopes, and the next steps. Requires scope drafts:read.
Annotations the server declares
- title: Get account status
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_draftGet a payment draft by id, including amounts, fee, quote, and status.No findings
Why it is in this group
- The name "get_draft" says "get": a word for reading.
Description, as the server wrote it Get a payment draft by id, including amounts, fee, quote, and status. Requires scope drafts:read.
Annotations the server declares
- title: Get payment draft
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_draft_statusLightweight status snapshot of a draft: status (AwaitingPayment/Seen/Confirmed/Expired/Cancelled), paying txid, confirmations, and reviewState when a transfer with a different amou…Reads text others writeNo findings
Why it is in this group
- The name "get_draft_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it Lightweight status snapshot of a draft: status (AwaitingPayment/Seen/Confirmed/Expired/Cancelled), paying txid, confirmations, and reviewState when a transfer with a different amount arrived (pending = needs the receiver's decision and the draft is not paid; accepted; rejected; unresolved = the draft expired while undecided, the money is with the receiver). Cheap to poll. Requires scope drafts:read.
Annotations the server declares
- title: Get draft status
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_fee_scheduleGet the public send21 fee schedule: tiered percent by payment size in USD, min/max fee, and dust limit.No findings
Why it is in this group
- The name "get_fee_schedule" says "get": a word for reading.
Description, as the server wrote it Get the public send21 fee schedule: tiered percent by payment size in USD, min/max fee, and dust limit. No authentication needed.
Annotations the server declares
- title: Get fee schedule
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_payment_requestGet a payment request by id: status (Open/Completed/Cancelled/Expired), pay path, offered currencies, and the underlying draft once the payer committed.No findings
Why it is in this group
- The name "get_payment_request" says "get": a word for reading.
Description, as the server wrote it Get a payment request by id: status (Open/Completed/Cancelled/Expired), pay path, offered currencies, and the underlying draft once the payer committed. Includes changeSignals and changeNotes: what is unusual compared with the account's paid payments (new_address, new_asset, unusual_amount), the same lines the payer sees on the pay page; empty when nothing is unusual. Requires scope drafts:read.
Annotations the server declares
- title: Get pay link
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_rateGet the current exchange rate for an asset in a fiat currency (rate = fiat units per 1 whole asset unit, with source provenance).No findings
Why it is in this group
- The name "get_rate" says "get": a word for reading.
Description, as the server wrote it Get the current exchange rate for an asset in a fiat currency (rate = fiat units per 1 whole asset unit, with source provenance). Assets: Btc, Usdc, Usdt, Eurc, Sol, Eth. 161 ISO 4217 fiat currencies are supported. Requires an API key.
Annotations the server declares
- title: Get exchange rate
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
get_transaction_templateGet the transaction template for an on-chain draft: every output to pay, plus walletcreatefundedpsbt arguments and a pay-to-many CSV on Bitcoin, or payment URIs (and calldata on EV…No findings
Why it is in this group
- The name "get_transaction_template" says "get": a word for reading.
Description, as the server wrote it Get the transaction template for an on-chain draft: every output to pay, plus walletcreatefundedpsbt arguments and a pay-to-many CSV on Bitcoin, or payment URIs (and calldata on EVM chains) on Solana, Ethereum, Base, Arbitrum and Polygon. The sender's own wallet funds, reviews and signs it; send21 contains no signing code. Not for Lightning drafts (pay their invoice). Requires scope drafts:read.
Annotations the server declares
- title: Get wallet payment instructions
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
list_address_bookList the account's saved addresses (label, address, network, direction: Sending = recipients the owner pays, Receiving = the owner's own addresses).No findings
Why it is in this group
- The name "list_address_book" says "list": a word for reading.
Description, as the server wrote it List the account's saved addresses (label, address, network, direction: Sending = recipients the owner pays, Receiving = the owner's own addresses). Requires scope addressbook:read.
Annotations the server declares
- title: List address book
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: true
list_draft_quotesList every quote (rate lock) of a fiat-priced draft, oldest first.No findings
Why it is in this group
- The name "list_draft_quotes" says "list": a word for reading.
Description, as the server wrote it List every quote (rate lock) of a fiat-priced draft, oldest first. Quotes never change; a re-quote adds a new one with its own id. Each has a sha256 (RFC 8785 JCS + SHA-256). Requires scope drafts:read.
Annotations the server declares
- title: List draft quotes
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- readOnlyHint: 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 outbound.
- Reads private data1
- 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 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.
Looked at Nov 20, 2026, 19:10 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
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://send21.io/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://send21.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://send21.io/mcp: tools/list returned 14 tools to an anonymous client, including create_payment_request (irreversible), propose_receiving_address (write), submit_lightning_proof (write), create_account (write), create_draft (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools14 changed.~14 changedView diff
- Changed:create_accountChanges thingstitleannotations
- Changed:create_draftChanges thingstitleannotations
- Changed:create_payment_requestCan't be undonetitleannotations
- Changed:get_account_statusOnly readstitleannotations
- Changed:get_draftOnly readstitleannotations
- Changed:get_draft_statusOnly readstitleannotations
- Changed:get_fee_scheduleOnly readstitleannotations
- Changed:get_payment_requestOnly readstitleannotations
- Changed:get_rateOnly readstitleannotations
- Changed:get_transaction_templateOnly readstitleannotations
- Changed:list_address_bookOnly readstitleannotations
- Changed:list_draft_quotesOnly readstitleannotations
- Changed:propose_receiving_addressChanges thingstitleannotations
- Changed:submit_lightning_proofChanges thingstitleannotations
Install
Pinned to version 1.7.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http send21io https://send21.io/mcpclaude mcp add --transport http send21io https://send21.io/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__send21io__get_transaction_template",
"mcp__send21io__get_fee_schedule",
"mcp__send21io__get_account_status",
"mcp__send21io__list_address_book",
"mcp__send21io__get_draft",
"mcp__send21io__get_payment_request",
"mcp__send21io__get_rate",
"mcp__send21io__list_draft_quotes",
"mcp__send21io__get_draft_status"
],
"ask": [
"mcp__send21io__create_payment_request",
"mcp__send21io__propose_receiving_address",
"mcp__send21io__submit_lightning_proof",
"mcp__send21io__create_account",
"mcp__send21io__create_draft"
],
"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 send21io. Review it before you use it.
Capability tags behind 3 rules
- mcp__send21io__get_account_status private-data, untrusted-input
- mcp__send21io__create_account untrusted-input
- mcp__send21io__get_draft_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.send21io/mcp/verify?hash=79c702fef3d60ccc52ba44db3e51a08fac7616bc9adea4fc6260812af5ff8c81" | jq -e '.changed == false'Pinned hash 79c702fef3d6, from Nov 8, 2026, 15: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.send21io/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.send21io/mcp)Source: MCP Registry. Synced Oct 22, 2026, 15:17 UTC.
send21 MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the send21 MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 5 of which can change, send or delete something, and 0 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 send21 MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the send21 MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: create_payment_request.
What tools does the send21 MCP server have?
- 14 tools: 1 irreversible, 4 write, 9 read. create_payment_request, propose_receiving_address, submit_lightning_proof, create_account, create_draft, get_transaction_template, get_fee_schedule, get_account_status and 6 more.
Does the send21 MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the send21 MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the send21 MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 22, 2026. Every change is on this page and in its Atom feed.