agents.u.cash

io.github.uxdevoPublished by GitHub account uxdevov0.6.18Updated Oct 24, 2026

Non-custodial HTTP-402 crypto payments for AI agents. 79-tool MCP server.

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

A local MCP server that gives an assistant non-custodial HTTP-402 crypto payment tools, described as a 79-tool set for agent payments.

What you can do
Provides a large tool set (reported as 79 tools) for non-custodial crypto payments over HTTP-402, aimed at AI agents handling payments themselves. The manifest lists no individual tools, so the exact operations cannot be confirmed from the supplied material. It runs as a local process on the user's machine over stdio.
When to use it
Consider it when an assistant needs to make or handle crypto payments between agents using the HTTP-402 protocol, and you are prepared to run a local container-based server. Without a tool list or README, review it directly before relying on it.
Requirements
Runs as a local process over stdio, distributed as an OCI container image, so a container runtime is needed. The manifest declares no authentication, environment variables or headers; any wallet or payment configuration is not documented in the supplied material.
Before you install
It concerns crypto payments, so real funds and wallet credentials may be involved; the manifest declares no authentication or environment variables, so how keys are supplied is unclear. Payment actions may move money. The tool list and documentation are absent, so capabilities cannot be verified before installing.

Installation

In SourceWeft

  1. Open agents.u.cash in the dashboard and add it to a workspace.
  2. 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

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

Version history

1
  1. v0.6.18LatestSep 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.