Connection guide

Back to category: Local clients

MCP Inspector

Sign in through id.web.money, then check your available wallets or balance. A successful sign-in alone does not verify every operation.

Requirements

Status
Connection verified by WebMoney
Connection channel
Local public client
What you do
Copy the public client_id and local settings into your desktop client, then authorize through id.web.money.
Connection values

Notes

  • This is a public client with PKCE: its application identifier is published, and no client secret is created or entered.

Setup

MCP Inspector Local

MCP Inspector has its own published WebMoney public OAuth client with PKCE and registered loopback callback URIs. The application identifier is not a secret, and no client secret is required.

The recommended route is the PowerShell block below. It creates a temporary JSON file containing only the public identifier, URL, and complete scope set, then launches the verified Inspector version shown below in config mode. The adjacent JSON block shows the same exact configuration separately. For the initial verification, complete only OAuth sign-in, two-factor verification, and read-only requests; do not run write tools.

The Read-only session banner in config mode means that the server list came from the configuration file and cannot be overwritten through the UI. It does not restrict OAuth scopes and does not make the MCP session read-only.

For a manual connection, open Add server, enter the published Server ID, choose Streamable HTTP, and copy the exact MCP URL. Inspector 2.x manual forms do not reliably expose a static client ID and complete scope list in every build, so config mode is preferred for the verified profile.

If Inspector displays or requests MCP_INSPECTOR_API_TOKEN, that value protects only Inspector's local proxy. It is not a WebMoney OAuth token: never paste it into WebMoney OAuth, send it to the MCP server, or include it in a support request. Never paste an OAuth access token, refresh token, authorization code, or Network/Authorization header into Inspector, chat, or a support request.

After launch, open the local UI, select the loaded server, complete OAuth at id.web.money, review consent, and finish two-factor verification. Open Tools and keep the smoke test to the two verified safe reads listed in the profile verification note below. Do not run write tools.

Ready-to-copy setup

Verified with client version 2.0.0 on Node.js 24.15.0 on 2026-10-28.

The fresh OAuth, two-factor, tools/list, and read smoke verified wallet_check_credentials, wallet_get_balance. No write tool was called in this Inspector smoke.

Launch MCP Inspector with a temporary config

Launches the verified version from the profile below with a temporary file of public settings only. No sign-in data is stored in the file and tools are not called automatically.

powershell
node --version
$configPath = Join-Path ([IO.Path]::GetTempPath()) 'webmoney-mcp-inspector.json'
$config = @'
{
  "mcpServers": {
    "webmoney": {
      "type": "http",
      "url": "https://mcp.webmoney.com/mcp",
      "oauth": {
        "clientId": "VMq_9XDRAorUes7VZ6n4",
        "scopes": "openid email phone profile offline_access wm.balance.read wm.transactions.read wm.messages.read wm.messages.send wm.invoices.manage wm.transfers.create wm.recipients.resolve"
      }
    }
  }
}
'@
[IO.File]::WriteAllText($configPath, $config, (New-Object Text.UTF8Encoding($false)))
npx '@modelcontextprotocol/inspector@2.0.0' --config $configPath
Exact Inspector configuration

This route reliably supplies the static public client identifier and complete scope set; those fields are not available in every Inspector manual-form build.

json
{
  "mcpServers": {
    "webmoney": {
      "type": "http",
      "url": "https://mcp.webmoney.com/mcp",
      "oauth": {
        "clientId": "VMq_9XDRAorUes7VZ6n4",
        "scopes": "openid email phone profile offline_access wm.balance.read wm.transactions.read wm.messages.read wm.messages.send wm.invoices.manage wm.transfers.create wm.recipients.resolve"
      }
    }
  }
}
Exact OAuth registration settings

These are the public settings registered for this catalog client.

Client name
WebMoney MCP for MCP Inspector Local
Client ID
VMq_9XDRAorUes7VZ6n4
Registered audience
https://mcp.webmoney.com
MCP URL
https://mcp.webmoney.com/mcp
OAuth resource
https://mcp.webmoney.com/
Scopes
  • openid
  • email
  • phone
  • profile
  • offline_access
  • wm.balance.read
  • wm.transactions.read
  • wm.messages.read
  • wm.messages.send
  • wm.invoices.manage
  • wm.transfers.create
  • wm.recipients.resolve
Grant types
  • authorization_code
  • refresh_token
Response types
code
Redirect URLs
  • http://localhost:6274/oauth/callback
  • http://127.0.0.1:6274/oauth/callback
  • http://localhost:6274/oauth/callback/debug
  • http://127.0.0.1:6274/oauth/callback/debug
  • http://127.0.0.1:6276/oauth/callback
Allowed CORS origins
  • http://localhost:6274
  • http://127.0.0.1:6274
Token endpoint client authentication
none — no client secret
PKCE
S256
Client URL
https://mcp.webmoney.com/docs
Verification status
Connection verified by WebMoney
Last verified
2026-10-28

Connection help

Reauthorization

Reauthorize after changing requested capabilities or wallet access grants.

Troubleshooting

Check the MCP address, callback URL, application identifier, and MCP support in the selected platform.

Never paste secrets into chat

Do not enter access tokens, refresh tokens, WebMoney JWTs, or client secret values in any AI message.

Known limitations

This guide may require manual client configuration.