U.CASH Pay (merchant MCP)

io.github.uantumPublished by GitHub account uantumv0.1.3Updated Oct 24, 2026

U.CASH Pay merchant MCP: create checkouts, verify webhooks, read settings. Non-custodial.

VerifiedSTDIODesktop onlyFinance Business & Commerce

Server details

Identifier: io.github.uantum/mcp-ucashpay
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account uantum for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.uantum%2Fmcp-ucashpay.svg)](https://sourceweft.com/mcp/io.github.uantum%2Fmcp-ucashpay?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server for U.CASH Pay merchants, letting an assistant create checkouts, verify webhooks and read payment settings.

What you can do: Create payment checkouts for a U.CASH Pay merchant account through the assistant. Verify incoming webhook payloads to confirm payment notifications. Read merchant settings and configuration. The server is described as non-custodial, so it works with a merchant account rather than holding funds itself.
When to use it: Useful when you run a U.CASH Pay merchant account and want an assistant to help set up checkouts, check webhook signatures or look up payment settings during development or operations.
Requirements: Runs as a local process installed from the PyPI package mcp-ucashpay, so a Python environment is needed. The manifest declares no authentication, environment variables or headers, but a merchant account and its credentials are implied by the checkout and settings features.

Before you install

Checkout creation and settings access act on a live merchant account, so confirm what credentials the server expects before installing. Webhook verification handles payment notification data. The manifest declares no authentication or secrets, which is worth reconciling with the merchant account access the tools imply.

Installation

In SourceWeft

Open U.CASH Pay (merchant MCP) in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.3LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.