U.CASH Pay MCP server
cash.u/ucash-payu.cashstreamable-httpv0.10.0Scanned
Pay x402 resources on U.CASH from your own wallet: view the price, pay on-chain, settle by hash.
14 tools: 1 can delete or cancel things, 1 do something that can't be undone, 2 change things and 10 only read.
- Reads private data · 2
- Reads text others write · 4
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does 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 U.CASH Pay MCP server can do
The U.CASH Pay MCP server is published by u.cash, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (1 tool: uxc_cancel_checkout), do things that cannot be undone, such as sending, paying or publishing (uxc_verify_payment) and create or change data (2 tools: uxc_create_checkout and uxc_complete_checkout). 10 tools only read.
2 tools read private data (uxc_get_services and uxc_discover_servers); 4 tools bring in text other people can write (uxc_view_door, uxc_get_market, uxc_get_services and 1 more).
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.10.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
Deletes or cancels 1Claude Code: deny
uxc_cancel_checkoutCancel a UCP checkout session.No findings
Why it is in this group
- The name "uxc_cancel_checkout" says "cancel": a word for removing or ending something.
Description, as the server wrote it Cancel a UCP checkout session. No key; pass cloud for a hosted merchant.
Can't be undone 1Claude Code: ask
uxc_verify_paymentBUYER-SIDE.No findings
Why it is in this group
- The name "uxc_verify_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it BUYER-SIDE. After paying a resource (from uxc_view_door) on-chain from your own wallet, submit the transaction hash to settle it. Pass the challengeId from the accepts[] entry you paid and the on-chain transaction hash. Returns settled (confirmed) or pending (awaiting confirmations). No seller key needed - the challengeId identifies the resource, and settlement is gated by on-chain confirmation.
Changes things 2Claude Code: ask
uxc_complete_checkoutMint payment challenges for a checkout session -> ready_for_complete.No findings
Why it is in this group
- The name "uxc_complete_checkout" says "checkout": a word for a change.
Description, as the server wrote it Mint payment challenges for a checkout session -> ready_for_complete. Optional ap2 (AP2 checkout mandate). No key; pass cloud for a hosted merchant.
uxc_create_checkoutCreate a UCP checkout session (multi-item, mixed-currency cart) for a merchant catalog.No findings
Why it is in this group
- The name "uxc_create_checkout" says "create": a word for a change.
Description, as the server wrote it Create a UCP checkout session (multi-item, mixed-currency cart) for a merchant catalog. No key. Returns {id, status, currency, line_items, totals, ap2}.
Only reads 10Show 10 read-only tools
uxc_discover_serversList every u.cash MCP server in the fleet (buyer, seller, prime, legacy): product surface, auth model, transports with install coordinates, docs URL.Reads private dataReads text others write1 finding
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...t to each server directly with your own credentials; no call is ever proxied."
Description, as the server wrote it List every u.cash MCP server in the fleet (buyer, seller, prime, legacy): product surface, auth model, transports with install coordinates, docs URL. Optional q filters by name/product/summary. Discovery only - connect to each server directly with your own credentials; no call is ever proxied.
uxc_discover_toolsSearch tools across every u.cash MCP server by name or description (case-insensitive substring), optionally scoped to one server.No findings
Why it is in this group
- The description's first verb is "search": a word for reading.
Description, as the server wrote it Search tools across every u.cash MCP server by name or description (case-insensitive substring), optionally scoped to one server. Returns the tool, a one-liner, its server, and how to connect. Discovery only - connect to that server directly; no call is ever proxied.
uxc_get_checkoutFetch a UCP checkout session by id (status: incomplete -> ready_for_complete -> completed).No findings
Why it is in this group
- The name "uxc_get_checkout" says "get": a word for reading.
Description, as the server wrote it Fetch a UCP checkout session by id (status: incomplete -> ready_for_complete -> completed). No key; pass cloud for a hosted merchant.
uxc_get_marketThe PUBLIC cross-merchant market catalog: every published checkout across merchants (id, title, price, currency, merchant, domain, payable url).Reads text others writeNo findings
Why it is in this group
- The name "uxc_get_market" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it The PUBLIC cross-merchant market catalog: every published checkout across merchants (id, title, price, currency, merchant, domain, payable url). No key. q filters by title/merchant/description.
uxc_get_orderView a UCP checkout session as an order (per-item fulfillment status + fulfillment events).No findings
Why it is in this group
- The name "uxc_get_order" says "get": a word for reading.
Description, as the server wrote it View a UCP checkout session as an order (per-item fulfillment status + fulfillment events). No key; pass cloud for a hosted merchant.
uxc_get_productFetch a single catalog product by id.No findings
Why it is in this group
- The name "uxc_get_product" says "get": a word for reading.
Description, as the server wrote it Fetch a single catalog product by id. Public (no key); pair with uxc_search_catalog to find ids.
uxc_get_servicesThe PUBLIC cross-provider services catalog (eSend rail: each row carries the provider contact email, a sendable asset code and a price).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "uxc_get_services" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it The PUBLIC cross-provider services catalog (eSend rail: each row carries the provider contact email, a sendable asset code and a price). No key.
uxc_lookup_productsBatch catalog lookup by ids.No findings
Why it is in this group
- The name "uxc_lookup_products" says "lookup": a word for reading.
Description, as the server wrote it Batch catalog lookup by ids. Public (no key).
uxc_search_catalogSearch a merchant catalog (text query + price filters + pagination).No findings
Why it is in this group
- The name "uxc_search_catalog" says "search": a word for reading.
Description, as the server wrote it Search a merchant catalog (text query + price filters + pagination). The merchant is resolved from a cloud token (the "cloud" argument) or the platform default. No key.
uxc_view_doorFetch the public 402 payment door for a resource (what a buyer sees at https://agents.u.cash/r/{res_id}): the price + the multi-coin accepts[] (each asset, the seller receive addre…Reads text others writeNo findings
Why it is in this group
- The name "uxc_view_door" says "view": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch the public 402 payment door for a resource (what a buyer sees at https://agents.u.cash/r/{res_id}): the price + the multi-coin accepts[] (each asset, the seller receive address, and the exact amount to pay). No key. Use as a BUYER to see what to pay, then uxc_verify_payment after paying. status=true polls settlement without minting a new challenge.
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 data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- 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, 18:31 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
- 4
- 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 4 tools that change things (1 destructive, 1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.u.cash/: tools/list returned 14 tools to an anonymous client, including uxc_cancel_checkout (destructive), uxc_verify_payment (irreversible), uxc_create_checkout (write), uxc_complete_checkout (write)
Findings
Matches of fixed checks, with the text they matched.
The description mentions "credentials".
What this check looks forMatched text
description: "...t to each server directly with your own credentials; no call is ever proxied."
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.10.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ucash-pay https://mcp.u.cash/claude mcp add --transport http ucash-pay https://mcp.u.cash/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.
{
"permissions": {
"allow": [
"mcp__ucash-pay__uxc_view_door",
"mcp__ucash-pay__uxc_get_market",
"mcp__ucash-pay__uxc_get_services",
"mcp__ucash-pay__uxc_search_catalog",
"mcp__ucash-pay__uxc_get_product",
"mcp__ucash-pay__uxc_lookup_products",
"mcp__ucash-pay__uxc_get_checkout",
"mcp__ucash-pay__uxc_get_order",
"mcp__ucash-pay__uxc_discover_servers",
"mcp__ucash-pay__uxc_discover_tools"
],
"ask": [
"mcp__ucash-pay__uxc_verify_payment",
"mcp__ucash-pay__uxc_create_checkout",
"mcp__ucash-pay__uxc_complete_checkout"
],
"deny": [
"mcp__ucash-pay__uxc_cancel_checkout"
]
}
}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 ucash-pay. Review it before you use it.
Capability tags behind 4 rules
- mcp__ucash-pay__uxc_view_door untrusted-input
- mcp__ucash-pay__uxc_get_market untrusted-input
- mcp__ucash-pay__uxc_get_services private-data, untrusted-input
- mcp__ucash-pay__uxc_discover_servers private-data, 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/cash.u/ucash-pay/verify?hash=97363c19cb260b48a2e49ae59890f0247a5cbc760a99eb913d77c356e7fcdbe5" | jq -e '.changed == false'Pinned hash 97363c19cb26, from Nov 10, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/cash.u/ucash-pay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/cash.u/ucash-pay)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:46 UTC.
U.CASH Pay MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the U.CASH Pay MCP server safe?
- No scan can promise that. What its definitions show: 14 tools, 4 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 U.CASH Pay MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: uxc_cancel_checkout.
Can the U.CASH Pay MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: uxc_verify_payment.
What tools does the U.CASH Pay MCP server have?
- 14 tools: 1 destructive, 1 irreversible, 2 write, 10 read. uxc_cancel_checkout, uxc_verify_payment, uxc_create_checkout, uxc_complete_checkout, uxc_view_door, uxc_get_market, uxc_get_services, uxc_search_catalog and 6 more.
Does the U.CASH Pay MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the U.CASH Pay MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the U.CASH Pay MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.