U.CASH Pay

cash.uv0.9.0Updated Oct 4, 2026

Pay x402 resources on U.CASH from your own wallet: view the price, pay on-chain, settle by hash.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage a U.CASH Pay merchant account: create hosted checkouts, verify settlement webhooks, and read settings and integration credentials.

What it does
A merchant-side MCP server for U.CASH Pay. Its tools create a checkout with an amount, currency, title and external reference and return a hosted checkout URL plus transaction id; verify an incoming webhook body against an X-Webhook-Signature using HMAC; and read agent settings and integration credentials for Discord, Telegram, BigCommerce, Ecwid and Wix. It is aimed at merchant operations rather than paying as a buyer.
When to use it
Use it when an assistant should help run a U.CASH Pay merchant account: generating payment links or checkouts during a workflow, checking that settlement webhooks are authentic, or reviewing store settings and connected integrations.
Requirements
Runs locally as a Python 3.10+ process, typically launched with uvx from the mcp-ucash package, or installed from source with pip. Needs three credentials supplied as environment variables: UXC_API_KEY for reads, UCASH_CLOUD_TOKEN for create_checkout, and UCASH_WEBHOOK_SECRET for verify_webhook. Network access to U.CASH endpoints is required.
Before you install
The server handles merchant credentials: UXC_API_KEY, UCASH_CLOUD_TOKEN and UCASH_WEBHOOK_SECRET. create_checkout creates real payment requests on a live merchant account, so amounts and references should be confirmed before use. get_integrations returns third-party integration credentials, which may be exposed to the model and its conversation history; treat that output as sensitive.

Installation

In SourceWeft

  1. Open U.CASH Pay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

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

README

mcp-ucash

A merchant-side MCP server for U.CASH Pay. Let Claude Desktop, Cursor, or any MCP client manage a merchant's pay.u.cash: create checkouts, verify settlement webhooks, and read settings + integration credentials.

Tools

  • create_checkout(amount, currency, title, external_reference) → hosted checkout URL + transaction id
  • verify_webhook(raw_body, signature_header) → HMAC verify an X-Webhook-Signature
  • get_integrations() → Discord/Telegram/BigCommerce/Ecwid/Wix credentials (from /v1/integrations)
  • get_settings() → safe agent settings (from /v1/settings)

Run

bash
# one-liner: uv installs an isolated Python 3.10+ and the deps for youuvx --from mcp-ucash python -m mcp_ucash

Or from source:

bash
pip install "mcp[cli]"export UXC_API_KEY=uxc_...          # agent API key, for /v1/* readsexport UCASH_CLOUD_TOKEN=st_...     # store cloud token, for create_checkoutexport UCASH_WEBHOOK_SECRET=...     # for verify_webhookpython mcp_ucash.py

Claude Desktop / Cursor config

json
{  "mcpServers": {    "ucash": {      "command": "uvx",      "args": ["--from", "mcp-ucash", "python", "-m", "mcp_ucash"],      "env": {        "UXC_API_KEY": "uxc_...",        "UCASH_CLOUD_TOKEN": "st_...",        "UCASH_WEBHOOK_SECRET": "..."      }    }  }}

MCP directories

This repo ships the manifests the MCP directories read:

  • mcp.json - client/registry descriptor (Glama, MCP Registry).
  • smithery.yaml - build + start spec for Smithery.

License

MIT.

Source: README.md at commit d476364

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.9.0LatestOct 4, 2026