WebMoney MCP

com.webmoneyPublished by webmoney.comOfficial publisherv0.1.0Updated Oct 29, 2026

Authenticated MCP access to WebMoney wallets, transactions, messages and invoices.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote, OAuth-protected MCP endpoint giving an assistant authenticated access to WebMoney wallets, transactions, messages and invoices.

What you can do
  • Access WebMoney wallets through an authenticated connection
  • Review transactions and payment history
  • Read and handle messages
  • Work with invoices
  • No individual tools are documented, so the exact actions available are not specified.
When to use it
When you want an assistant to work with a WebMoney account — checking wallet balances, reviewing transactions, reading messages or handling invoices — without building your own integration.
Requirements
A remote MCP endpoint at mcp.webmoney.com over streamable HTTP; no local package or runtime is needed. A WebMoney account and OAuth sign-in are required. Network access to the endpoint is required.
Before you install
The server is authenticated and tied to a financial account, so granting access exposes wallet, transaction, message and invoice data to the assistant. The tool list is not published, so whether it can move money, send messages or change invoices cannot be confirmed from this listing; check before connecting. OAuth consent should be reviewed carefully.

Installation

In SourceWeft

  1. Open WebMoney MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.webmoney%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "webmoney": {
      "type": "http",
      "url": "https://mcp.webmoney.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

56% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.