refund

6 registry entries were observed exposing a tool named refund — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @codespar/mcp-ebanx
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   MCP server for EBANX — cross-border payments, payouts, exchange rates
2. @codespar/mcp-pagar-me
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   MCP server for Pagar.me — orders, charges, recipients, transfers, plans, subscriptions, webhooks
3. @codespar/mcp-pagseguro
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   MCP server for PagSeguro/PagBank — orders, Pix, boleto, credit card, charges
4. com.mnemopay/sdk
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Memory + wallet for AI agents. Real payment rails, Agent FICO 300-850, Merkle audit, identity.
5. io.github.theYahia/cloudpayments-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server for CloudPayments API — charge, auth, confirm, void, refund, find transaction. 6 tools.
6. io.github.vrllrv/junto-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   The payment protocol for people and agents. One MCP server, any payment rail.

All indexed toolsSearch the registry for refund