U.CASH Pay
REMOTE · MCP.U.CASH
Pay x402 resources on U.CASH from your own wallet: view the price, pay on-chain, settle by hash.
Available components
Last scanned (18 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1318 tokens (~94/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 33% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.u.cash/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=u.cash | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1eb0a7256160bfcc13ac98551aac5d2c |
| SANs: u.cash, *.u.cash | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.u.cash. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cash. | present | 61724 | 8 | Verified |
| u.cash. | present | 2371 | 13 | Verified |
| mcp.u.cash. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.u.cash/ | Verified | 200 | |
| http (plaintext) | http://mcp.u.cash/ | HTTPS enforced | 301 | https://mcp.u.cash/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
uxc_cancel_checkout ~41
Cancel a UCP checkout session. No key; pass cloud for a hosted merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
uxc_complete_checkout ~68
Mint payment challenges for a checkout session -> ready_for_complete. Optional ap2 (AP2 checkout mandate). No key; pass cloud for a hosted merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| ap2 | string | – | optional AP2 checkout mandate |
| cloud | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
uxc_create_checkout ~105
Create a UCP checkout session (multi-item, mixed-currency cart) for a merchant catalog. No key. Returns {id, status, currency, line_items, totals, ap2}.
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | – | – |
| cloud | string | – | merchant token when buying from a hosted merchant |
| context | string | – | – |
| currency | string | – | optional cart display currency |
| line_items | array | yes | each: {item:{id}, quantity} |
No output schema declared.
No examples provided.
uxc_discover_servers ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | case-insensitive substring over name/product/summary |
No output schema declared.
No examples provided.
uxc_discover_tools ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | – | substring matched over tool name + description |
| server | string | – | optional: restrict to one fleet server name |
No output schema declared.
No examples provided.
uxc_get_checkout ~53
Fetch a UCP checkout session by id (status: incomplete -> ready_for_complete -> completed). No key; pass cloud for a hosted merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
uxc_get_market ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional response projection: dot paths to keep, e.g. ["items.title","items.price"] or row-level ["title","price"]. Envelope/meta keys (ok, success, total, count, pagination) are always kept; unknown… |
| limit | integer | – | – |
| q | string | – | filter by title/merchant/description |
No output schema declared.
No examples provided.
uxc_get_order ~52
View a UCP checkout session as an order (per-item fulfillment status + fulfillment events). No key; pass cloud for a hosted merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
uxc_get_product ~47
Fetch a single catalog product by id. Public (no key); pair with uxc_search_catalog to find ids.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
uxc_get_services ~112
The PUBLIC cross-provider services catalog (eSend rail: each row carries the provider contact email, a sendable asset code and a price). No key.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional response projection: dot paths to keep, e.g. ["items.asset","items.price"] or row-level ["asset","price"]. Envelope/meta keys (ok, success, total, count, pagination) are always kept; unknown… |
| limit | integer | – | – |
No output schema declared.
No examples provided.
uxc_lookup_products ~93
Batch catalog lookup by ids. Public (no key).
| Name | Type | Req | Description |
|---|---|---|---|
| cloud | string | – | – |
| fields | array | – | Optional response projection: dot paths to keep, e.g. row-level ["id","title","price"]. Envelope/meta keys (ok, success, total, count, pagination) are always kept; unknown paths are ignored; empty/ab… |
| ids | array | yes | – |
No output schema declared.
No examples provided.
uxc_search_catalog ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cloud | string | – | – |
| filters | string | – | – |
| pagination | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
uxc_verify_payment ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| challengeId | string | yes | – |
| hash | string | yes | – |
No output schema declared.
No examples provided.
uxc_view_door ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| res_id | string | yes | – |
| status | boolean | – | poll mode: GET /r/{id}?status=1 - no-mint settlement check |
No output schema declared.
No examples provided.
How do I install the U.CASH Pay MCP server?
U.CASH Pay is a hosted endpoint at https://mcp.u.cash/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.u.cash
claude mcp add --transport http cash-u-ucash-pay 'https://mcp.u.cash/'
What is the U.CASH Pay MCP server?
U.CASH Pay is an MCP server listed in the public MCP registry as cash.u/ucash-pay. Pay x402 resources on U.CASH from your own wallet: view the price, pay on-chain, settle by hash. This page covers its hosted endpoint (https://mcp.u.cash/).
Is the U.CASH Pay MCP server safe to use?
U.CASH Pay scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the U.CASH Pay MCP server expose?
U.CASH Pay exposes 14 tools: uxc_view_door, uxc_verify_payment, uxc_get_market, uxc_get_services, uxc_search_catalog, and 9 more. Their descriptions and schemas cost roughly 1,210 tokens of context every time the server is loaded.
Does the U.CASH Pay MCP server require authentication?
No. We connected to U.CASH Pay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the U.CASH Pay MCP server still maintained?
U.CASH Pay is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.