WebMoney MCP

Connect an AI assistant to WebMoney

View balances and history, work with messages, invoices, and transfers through MCP. Access is limited by OAuth, selected wallets, individual grants, and operation confirmation.

Connect an AI assistant Go to account
You control access

You control access. Grant only the permissions you need. Before an operation, check the recipient, amount and details. Signing in does not approve an individual transaction.

AI assistants and MCP clients

Each client shows its actual status: verified, manual setup required, experimental guide, or preparing publication.

View data

An agent can view balances, history, messages, and invoices only within granted permissions.

Protected actions

Sending messages, working with invoices, and transfers require separate permissions and action confirmation.

Three permission layers

  1. OAuth permissionsOAuth permissions define an application's broad capabilities.
  2. Access grants and walletsIndividual access grants determine which wallets and capabilities an application may use.
  3. Action parametersCheck the parameters before an action. A client guard argument does not replace 2FA or create an independent confirmation screen.

Security model

Sensitive permissions are granted with 2FA. The application then acts within delegated access; manage grants and applications in your account.

Wallet MCP

Available

Balances, history, messages, invoices, transfers, and recipient lookup with layered access controls.

Open module

Exchanger MCP

In development

Exchanger is in development and is not presented as a ready public capability yet.

About the module