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

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.u.cash`: 80/100 (this document), [markdown](https://verifymcp.io/servers/cash-u-ucash-pay/mcp.md), [page](https://verifymcp.io/servers/cash-u-ucash-pay/mcp)

## Channel facts

- Endpoint: `https://mcp.u.cash/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1318 tokens (~94/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http cash-u-ucash-pay 'https://mcp.u.cash/'
```

### Cursor

```json
{
  "mcpServers": {
    "cash-u-ucash-pay": {
      "url": "https://mcp.u.cash/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cash-u-ucash-pay": {
      "type": "http",
      "url": "https://mcp.u.cash/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cash-u-ucash-pay]
url = "https://mcp.u.cash/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cash-u-ucash-pay": {
      "type": "remote",
      "url": "https://mcp.u.cash/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cash-u-ucash-pay --url 'https://mcp.u.cash/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cash-u-ucash-pay:
    url: "https://mcp.u.cash/"
```

### Netclaw

```json
{
  "McpServers": {
    "cash-u-ucash-pay": {
      "Transport": "http",
      "Url": "https://mcp.u.cash/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cash-u-ucash-pay -t streamable-http -u 'https://mcp.u.cash/'
```

### Other

```json
{
  "mcpServers": {
    "cash-u-ucash-pay": {
      "type": "http",
      "url": "https://mcp.u.cash/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 79, +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.

### 2026-10-30 (score 78, +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.

### 2026-10-27 (score 77, +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.

### 2026-10-25 (score 76, +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.

### 2026-10-23 (score 75, +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.

### 2026-10-21 (score 74, +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.

### 2026-10-19 (score 73, +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.

## MCP tools (14)

### `uxc_view_door` (~129 tokens)

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.

Input parameters:

- `res_id` (string, required)
- `status` (boolean): poll mode: GET /r/{id}?status=1 - no-mint settlement check

### `uxc_verify_payment` (~108 tokens)

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.

Input parameters:

- `challengeId` (string, required)
- `hash` (string, required)

### `uxc_get_market` (~136 tokens)

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.

Input parameters:

- `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

### `uxc_get_services` (~112 tokens)

The PUBLIC cross-provider services catalog (eSend rail: each row carries the provider contact email, a sendable asset code and a price). No key.

Input parameters:

- `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)

### `uxc_search_catalog` (~74 tokens)

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.

Input parameters:

- `cloud` (string)
- `filters` (string)
- `pagination` (string)
- `query` (string)

### `uxc_get_product` (~47 tokens)

Fetch a single catalog product by id. Public (no key); pair with uxc_search_catalog to find ids.

Input parameters:

- `cloud` (string)
- `id` (string, required)

### `uxc_lookup_products` (~93 tokens)

Batch catalog lookup by ids. Public (no key).

Input parameters:

- `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, required)

### `uxc_create_checkout` (~105 tokens)

Create a UCP checkout session (multi-item, mixed-currency cart) for a merchant catalog. No key. Returns {id, status, currency, line_items, totals, ap2}.

Input parameters:

- `buyer` (string)
- `cloud` (string): merchant token when buying from a hosted merchant
- `context` (string)
- `currency` (string): optional cart display currency
- `line_items` (array, required): each: {item:{id}, quantity}

### `uxc_get_checkout` (~53 tokens)

Fetch a UCP checkout session by id (status: incomplete -> ready_for_complete -> completed). No key; pass cloud for a hosted merchant.

Input parameters:

- `cloud` (string)
- `id` (string, required)

### `uxc_complete_checkout` (~68 tokens)

Mint payment challenges for a checkout session -> ready_for_complete. Optional ap2 (AP2 checkout mandate). No key; pass cloud for a hosted merchant.

Input parameters:

- `ap2` (string): optional AP2 checkout mandate
- `cloud` (string)
- `id` (string, required)

### `uxc_cancel_checkout` (~41 tokens)

Cancel a UCP checkout session. No key; pass cloud for a hosted merchant.

Input parameters:

- `cloud` (string)
- `id` (string, required)

### `uxc_get_order` (~52 tokens)

View a UCP checkout session as an order (per-item fulfillment status + fulfillment events). No key; pass cloud for a hosted merchant.

Input parameters:

- `cloud` (string)
- `id` (string, required)

### `uxc_discover_servers` (~88 tokens)

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.

Input parameters:

- `q` (string): case-insensitive substring over name/product/summary

### `uxc_discover_tools` (~104 tokens)

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.

Input parameters:

- `limit` (integer)
- `q` (string): substring matched over tool name + description
- `server` (string): optional: restrict to one fleet server name

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cash-u-ucash-pay/mcp#diagnostics

## Score history

- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 77
- 2026-10-28: 77
- 2026-10-27: 77
- 2026-10-26: 76
- 2026-10-25: 76
- 2026-10-24: 75
- 2026-10-23: 75
- 2026-10-22: 74
- 2026-10-21: 74
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 24
- 2026-10-15: 24
- 2026-10-14: 70
- 2026-10-13: 70
- 2026-10-12: 70
- 2026-10-10: 69
- 2026-10-07: 67
- 2026-10-04: 65

## Common questions

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

## Links

- Remote endpoint: https://mcp.u.cash/
- Repository: https://github.com/UdotCASH/mcp-ucash
- Changelog RSS feed: https://verifymcp.io/servers/cash-u-ucash-pay/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/cash-u-ucash-pay/mcp.json
- HTML version of this page: https://verifymcp.io/servers/cash-u-ucash-pay/mcp