U.CASH Pay

What U.CASH Pay MCP server does

The U.CASH Pay MCP server exposes merchant-side operations for a pay.u.cash account. An MCP client can create a hosted checkout, verify the signature on a webhook request, inspect configured integrations, and retrieve agent-safe settings.

Checkout creation accepts an amount, currency, title, and external reference. The result includes a hosted checkout URL and a transaction ID, which an agent or surrounding application can use to direct a customer to payment and track the request.

Webhook verification handles the X-Webhook-Signature header. The server receives the unmodified request body and signature header, then performs the HMAC verification using the configured webhook secret.

How it works

The U.CASH Pay MCP server runs locally and communicates with an MCP client over standard input and output. Claude Desktop, Cursor, or another MCP-compatible client starts the Python process and invokes its tools through MCP.

Different operations use different credentials. Reads from the /v1/* API use UXC_API_KEY; checkout creation uses UCASH_CLOUD_TOKEN; and webhook verification uses UCASH_WEBHOOK_SECRET. The server retrieves integration information from /v1/integrations and safe agent settings from /v1/settings.

The available integration response can include credentials for Discord, Telegram, BigCommerce, Ecwid, and Wix. The material does not describe additional payment, wallet, or settlement operations beyond checkout creation and webhook verification.

Setup and configuration

Install and run the package with uvx, which supplies an isolated Python 3.10-or-newer environment and the package dependencies:

uvx --from mcp-ucash python -m mcp_ucash

When running from source, install the MCP CLI dependency and start the Python file:

pip install "mcp[cli]"
python mcp_ucash.py

Set these environment variables before starting the process:

• UXC_API_KEY: agent API key used for /v1/* reads.
• UCASH_CLOUD_TOKEN: store cloud token used to create checkouts.
• UCASH_WEBHOOK_SECRET: secret used to verify webhook signatures.

The repository includes an MCP configuration example using the uvx command and these three variables. It also ships mcp.json and smithery.yaml manifests for client and registry tooling.

Tools and capabilities

• create_checkout(amount, currency, title, external_reference): creates a hosted checkout and returns its URL and transaction ID.
• verify_webhook(raw_body, signature_header): verifies an HMAC signature supplied in X-Webhook-Signature.
• get_integrations(): reads configured Discord, Telegram, BigCommerce, Ecwid, and Wix credentials from /v1/integrations.
• get_settings(): reads safe agent settings from /v1/settings.

Limitations and notes

The U.CASH Pay MCP server is oriented toward merchant account administration and checkout workflows. The provided tool list does not document direct wallet management, on-chain payment execution, or a general transaction query tool. Webhook verification requires the raw request body and the signature header, so callers need to preserve the body before parsing it.

The README identifies the project as MIT-licensed and names Claude Desktop and Cursor in its setup instructions. Other MCP clients may work when they can launch a standard stdio MCP server, but no client-specific configuration is provided for them in the supplied material.