get_payment_status

5 registry entries were observed exposing a tool named get_payment_status — 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-flow-cl
   trust 60/100 · BMCP serverobserved 2026-08-13 · static extraction
   MCP server for Flow.cl — Chilean PSP: hosted payment orders, Webpay, refunds, HMAC-signed API
2. @codespar/mcp-nequi
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   Nequi — Colombian digital wallet (50M+ users, by Bancolombia)
3. @codespar/mcp-nupay
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   MCP server for NuPay — Nubank merchant checkout: Pix + wallet one-click for 100M+ BR users
4. @codespar/mcp-picpay
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   MCP server for PicPay Business — BR digital wallet (60M+ users): checkout, Pix QR, subscriptions
5. io.github.jams24/inventpay-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   Manage crypto payments, stores, digital products, and orders via InventPay

All indexed toolsSearch the registry for get_payment_status