MuPag Sandbox Payments

br.com.mupagPublished by mupag.com.brv0.1.0Updated Oct 27, 2026

Sandbox-only MuPag MCP server for approved payments, subscriptions, refunds, and reconciliation.

The publisher's own server: Payments Ai Mcp

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Sandbox-only MuPag MCP server that lets an assistant work with test payments, subscriptions, refunds and reconciliation.

What you can do
  • Handle approved payments in the MuPag sandbox environment
  • Create and manage subscriptions
  • Issue refunds
  • Reconcile transactions
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to exercise MuPag payment flows — payments, subscriptions, refunds and reconciliation — against test data before building or testing a real integration.
Requirements
Runs locally over stdio, typically via npx from the npm package. Requires a MuPag sandbox secret key supplied in the MUPAG_API_KEY environment variable, plus the MUPAG_ENV variable, which is fixed to the sandbox environment in this release. Desktop client only.
Before you install
The server handles payment operations such as refunds and subscriptions, which change data in the MuPag sandbox account tied to the key. Keep the MUPAG_API_KEY secret and use only a test key; this release is sandbox-only, so do not expect production payments.

Installation

In SourceWeft

  1. Open MuPag Sandbox Payments 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.1.0LatestSep 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.

Other Payments integrations