MCP.Market

Dlocal MCP server

by codespar·io.github.codespar/mcp-dlocal·v0.2.2·271 stars
No reviews yet

MCP server for dLocal — LatAm cross-border payments, payouts, refunds across 15+ countries

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

full report

Adoption
Growing

271 stars

Reviews

Write one

Nobody has reviewed Dlocal yet.

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

Dlocal tools (18, 7 write)

write = sends, deletes, buys or posts

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

  • cancel_paymentwrite action

    Cancel an authorized-but-not-captured payment, or void a PENDING payment. Card payments must be in AUTHORIZED state.

  • capture_payment

    Capture an AUTHORIZED card payment. Omit amount for full capture; pass amount for partial capture (must be ≤ authorized amount). Card-only.

  • create_card_tokenwrite action

    Tokenize a card for use in DIRECT-flow create_payment. Use the returned token in the card.token field instead of raw PAN. Required for PCI scope reduction.

  • create_paymentwrite action

    Create a payment (pay-in) in a LatAm country using a local payment method. Returns the payment object with a status and, for voucher/QR methods, the redirect/display data.

  • create_payoutwrite action

    Send money out to a beneficiary in a LatAm country. Used for marketplace seller payouts, creator payouts, and cross-border settlement.

  • create_refundwrite action

    Refund a captured payment. Supports full refund (amount omitted) or partial refund (amount set).

  • get_balance

    Get the merchant's current available balance per currency.

  • get_exchange_rate

    Query the dLocal FX rate for a destination country/currency pair. Used to preview converted amounts before a payout or USD-funded charge.

  • get_payment

    Get payment status and full detail by dLocal payment id.

  • get_payment_by_order_idwrite action

    Get a payment by the merchant-side order_id supplied at creation time. Useful when the agent only kept its own reference and not dLocal's id.

  • get_payout

    Get payout status by dLocal payout id.

  • get_payout_by_external_id

    Get a payout by the merchant external_id / order_id supplied at creation time. Mirror of get_payment_by_order_id for the payouts side.

  • get_refundwrite action

    Get refund status by refund id.

  • list_payment_methods

    List all payment methods available for a given country. Agents use this to dynamically discover local methods (Pix in BR, OXXO in MX, PSE in CO, etc) without hard-coding per-country logic.

  • list_payments

    List payments with optional date / country / status filters. Useful for reconciliation and reporting agents.

  • list_payouts

    List payouts with optional date / country / status filters. Useful for settlement reconciliation across countries.

  • list_refunds

    List refunds, optionally scoped to a payment_id. Useful for reconciling partial refunds against the original charge.

  • validate_document

    Validate a LatAm tax/identity document (CPF or CNPJ in BR, CUIT/CUIL/DNI in AR, RUT in CL/UY, RFC/CURP in MX, etc). Returns whether the document is well-formed and, when supported, registry-validated.

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 Dlocal 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
18
the typical server has 7
Tools that change things
39%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 28,688 servers

What its tools let an agent do: 11 read · 4 create · 2 change · 1 delete

Install Dlocal in Claude Code, Cursor or VS Code

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

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

What the publisher says

From the Dlocal 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.

Dlocal: common questions

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

More from codespar →