authorize_payment

4 registry entries were observed exposing a tool named authorize_payment — 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-ap2
    trust 60/100 · BMCP serverobserved · static extraction
    MCP server for AP2 — Google's Agent-to-Agent Payment Protocol (authorization, audit, trust)
  2. @codespar/mcp-safrapay
    trust 60/100 · BMCP serverobserved · static extraction
    MCP server for Safrapay — Banco Safra's acquirer (B2B-banking crossover, mid-to-large BR merchants). Credit, Pix, boleto + split, statement,
  3. @codespar/mcp-worldpay
    trust 60/100 · BMCP serverobserved · static extraction
    MCP server for Access Worldpay — enterprise processor: authorize, capture, refund, tokenize
  4. @gocushy/mcp
    trust 60/100 · BMCP serverobserved · static extraction
    The checkout your AI runs — bumps, upsells, subscriptions, tax and affiliates on your own Stripe.

All indexed toolsSearch the registry for authorize_payment