ToolsMCP
MuPag Sandbox Payments
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- mupag.com.br
- Prerequisites
- Install @mupag/mcp-server from npm (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.0 · updated
- Official links
Publisher’s description
Sandbox-only MuPag MCP server for approved payments, subscriptions, refunds, and reconciliation.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- mupag.com.br
- Version observed
- 0.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/br.com.mupag%2Fmcp-server/versions/0.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Create invoices and handle payments | Publisher description mentions “payments”, “subscriptions”, “refunds”. | No connection check or task run. Capability is as described by the publisher. | Rule payments-invoices matched: “payments”, “subscriptions”, “refunds”. Rule payments-invoices. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@mupag/mcp-server(npm, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
br.com.mupag/mcp-server
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.