Epayco MCP server
MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks
271 stars11 downloads/wk
Reviews
Write oneNobody has reviewed Epayco yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Epayco tools (8, 5 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
charge_cardwrite actionCharge a tokenized card (POST /payment/v1/charge/create). Amounts in COP unless currency says otherwise. Test mode is controlled by EPAYCO_TEST.
create_cash_paymentwrite actionCreate a cash payment voucher on a Colombian cash network (POST /restpagos/v2/efectivo/{network} on secure.payco.co). The payer takes the voucher code to a physical point to pay.
create_customerwrite actionCreate an ePayco customer bound to a card token (POST /payment/v1/customer/create). Returns customer_id used by charge_card.
create_pse_paymentwrite actionCreate a PSE bank-debit payment (POST /restpagos/pagos/debitos.json on secure.payco.co). Returns a bank redirect URL the payer must open to authorize the debit.
get_pse_transactionGet a PSE transaction's status by transaction id (GET /restpagos/pse/transactioninfo.json on secure.payco.co).
get_transactionGet transaction detail by referencePayco (GET https://secure.epayco.co/validation/v1/reference/{ref}). Works for card, PSE and cash payments.
list_pse_banksList PSE banks available for bank debit (GET /restpagos/pse/bancos.json on secure.payco.co).
tokenize_cardwrite actionCreate a one-time card token (POST /v1/tokens on api.secure.payco.co). The token is then bound to a customer via create_customer and charged via charge_card.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan3 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 28 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Epayco 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,243 servers
- Tools
- 8
- the typical server has 7
- Tools that change things
- 63%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 271
- more than 95% of 28,706 servers
- Downloads a week
- 11
- more than 3% of 12,306 servers with a package
What its tools let an agent do: 3 read · 3 create · 2 change
Install Epayco in Claude Code, Cursor or VS Code
Runs npx -y @codespar/mcp-epayco on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-epayco -- npx -y @codespar/mcp-epayco
What the publisher says
From the Epayco 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.
Epayco: common questions
- Is Epayco MCP server safe?
- Mostly: it is graded B (82/100). Read the Epayco safety report
- How do I install Epayco?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Epayco need an API key?
- Yes. The registry entry asks for
EPAYCO_PRIVATE_KEY. - Is Epayco maintained?
- The last commit was 69 days ago (2026-08-29). The latest release is v0.1.0.
- How does Epayco compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,243 servers); tools 8 (the typical server has 7); tools that change things 63% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.