MCP.Market

Safrapay MCP server

by codespar·io.github.codespar/mcp-safrapay·v0.2.0-alpha.3·271 stars
No reviews yet

MCP server for Safrapay — Banco Safra acquirer: credit, Pix, boleto + split, 3DS, chargebacks

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Established

271 stars22 downloads/wk

Reviews

Write one

Nobody has reviewed Safrapay yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Safrapay tools (22, 10 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • authenticate_3ds

    Kick off 3-D Secure authentication before authorize_payment. Returns a challenge URL / eci / cavv / xid to pass back into authorize_payment for a liability-shifted transaction.

  • authorize_payment

    Authorize a credit-card payment on Safrapay. Set preauth=true to authorize only (use capture_payment later); false to authorize+capture atomically.

  • cancel_paymentwrite action

    Cancel (void) an authorized-but-uncaptured payment. Also used for full refund of a captured payment in Safrapay.

  • cancel_recurrencewrite action

    Cancel an active recurrence. Future charges will stop; already-charged cycles are untouched.

  • capture_payment

    Capture a previously authorized (pre-auth) payment.

  • create_boletowrite action

    Create a boleto charge. Returns boleto PDF URL, barcode, digitable line, and expiration date.

  • create_payment_linkwrite action

    Create a hosted-checkout payment link. Returns a short URL the merchant shares with the payer; Safrapay hosts the checkout and accepts credit/Pix/boleto per configuration.

  • create_pixwrite action

    Create a Pix charge. Returns qr_code (EMV copy-paste payload), qr_code_image, and chargeId.

  • create_recurrencewrite action

    Create a recurring-billing subscription. Safrapay will charge card_token on the configured interval until cancel_recurrence or end_date. POST /v2/recurrence.

  • create_split_rulewrite action

    Configure split distribution for an existing charge. Each rule routes a portion of the charge to a receiver (onboard receivers via the Portal first).

  • delete_card_tokenwrite action

    Revoke a stored card token. For persistent card-on-file tokens created via tokenize_card (temporary=false). DELETE /v2/card/{cardId}.

  • get_payment

    Retrieve a charge by Safrapay chargeId. Works for credit, Pix, and boleto.

  • get_recurrence

    Retrieve a recurrence by id: schedule, next-charge date, charge history, status.

  • get_settlement_report

    Retrieve a settlement (liquidacao) report from the reconciliation host. Groups captured charges by settlement date so merchants can tie payouts to charges.

  • get_statement

    Retrieve the digital statement (extrato). A Safrapay differentiator, reflecting the Banco Safra bank-account integration.

  • list_transactions

    List charges with optional filters.

  • query_chargeback

    Retrieve chargeback (contestacao) detail for a charge: reason code, acquirer deadline, dispute amount, evidence status.

  • query_installments

    Simulate an installment plan for a given amount. Returns the per-installment amount, buyer-fee, and total for each available installment count.

  • refund_paymentwrite action

    Refund a captured payment. Pass amount for a partial refund; omit for full. Safrapay routes both through /v2/charge/cancelation with an amount field.

  • register_webhook

    Bulk-register webhook subscriptions on the Safrapay webhook product. Sends to POST /v1/webhook/bulk on the webhook host.

  • search_by_merchant_orderwrite action

    Look up charges by the merchant-side order identifier (the order_id supplied at creation). Useful when the Safrapay chargeId was lost but the merchant order id is known.

  • tokenize_card

    Tokenize a card for PCI-safe reuse. Set temporary=true for a single-use token (POST /v2/temporary/card); false for a persistent card-on-file (POST /v2/card).

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Safrapay compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
22
the typical server has 7
Tools that change things
45%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 28,688 servers
Downloads a week
22
more than 8% of 12,191 servers with a package

What its tools let an agent do: 11 read · 6 create · 2 change · 3 delete

Install Safrapay in Claude Code, Cursor or VS Code

Runs npx -y @codespar/mcp-safrapay on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-safrapay -- npx -y @codespar/mcp-safrapay
Add to Cursor

What the publisher says

From the Safrapay repository's README, as published. We do not edit it. Read it on GitHub

MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute

The Problem

AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

The Solution

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
  → 📦 Agent generates shipping label (Melhor Envio / Skydropx)
  → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
  → 📊 Agent records in ERP (Omie / Bling / Tiny)
  → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

Four servers for the emerging agentic payment stack:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Safrapay: common questions

Is Safrapay MCP server safe?
Mostly: it is graded B (82/100). Read the Safrapay safety report
How do I install Safrapay?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Safrapay need an API key?
Yes. The registry entry asks for SAFRAPAY_CLIENT_SECRET.
Is Safrapay maintained?
The last commit was 67 days ago (2026-08-29). The latest release is v0.2.0-alpha.3.
How does Safrapay compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 22 (the typical server has 7); tools that change things 45% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from codespar →