MCP.Market

Izipay MCP server

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

MCP server for Izipay — Peru enterprise acquirer (Niubiz): authorize/capture/refund, cuotas

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 Izipay yet.

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

Izipay tools (20, 13 write)

write = sends, deletes, buys or posts

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

  • authenticate_3ds

    Complete a 3-D Secure challenge. Call after the payer finishes the issuer challenge (redirected back to return_url) with the authenticator response (cres / PaRes). Returns the authenticated charge state so capture or authorization can proceed.

  • cancel_chargewrite action

    Void an authorized-but-uncaptured charge. Does not work on captured charges — use refund_charge for those.

  • cancel_subscriptionwrite action

    Cancel an active subscription. No further charges will be attempted; historical charges are preserved.

  • capture_chargewrite action

    Capture a previously authorized charge (when capture=false was used in create_charge).

  • create_chargewrite action

    Authorize a card payment. Supports 3-D Secure (3DS) challenge flow when required by issuer/brand. Set capture=true for authorize+capture atomically; capture=false to authorize only and capture later via capture_charge.

  • create_installment_planwrite action

    Create a Peruvian cuotas (installment) plan on a charge. Enables splitting a card payment into N monthly installments, with or without interest, per the issuer's cuota program.

  • create_payment_linkwrite action

    Create a hosted payment link (pay-by-link). Returns a URL to share with the payer; Izipay renders the checkout and reports via webhook. Useful for WhatsApp/email flows where no integrated checkout exists.

  • create_subscriptionwrite action

    Start a recurring card charge (subscription). The card must be tokenized first via tokenize_card. Izipay will charge the token on the configured cadence and emit webhooks per cycle.

  • delete_tokenwrite action

    Delete a stored card token.

  • get_chargewrite action

    Retrieve a charge by Izipay charge id.

  • get_charge_by_orderwrite action

    Retrieve a charge by the merchant-side orderNumber (order_id passed to create_charge). Use when you have the merchant reference but not the Izipay charge id.

  • get_payment_link

    Retrieve a payment link by id. Returns current status, associated charge (if paid), and expiration.

  • get_settlement

    Get the daily settlement batch (liquidación) for a given date. Returns gross, fees, net, and line items that settled to the merchant's bank account.

  • list_installment_options

    Query available cuota programs for a given card BIN and amount. Returns the list of issuer-offered installment plans (number of cuotas, with/without interest) that can be attached via create_installment_plan.

  • list_settlements

    List settlement batches across a date range. Summary view over get_settlement for multi-day reconciliation.

  • list_transactions

    List transactions for reconciliation. Filter by date range and status.

  • pay_plinwrite action

    Initiate a Plin direct payment. Plin is the inter-bank wallet (Interbank, BBVA, Scotiabank, BanBif). The payer authorizes in-app; this call sends the payment request to their phone.

  • pay_yapewrite action

    Initiate a Yape direct payment. Yape is BCP's mobile wallet (most-used wallet in Peru). The payer authorizes via an OTP code from their Yape app bound to their phone number.

  • refund_chargewrite action

    Refund a captured charge. Pass amount for a partial refund; omit for a full refund.

  • tokenize_card

    Tokenize a card for PCI-safe reuse. Returns a token_id to pass into create_charge.card.token_id.

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 Izipay 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
20
the typical server has 7
Tools that change things
65%
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: 7 read · 4 create · 6 change · 3 delete

Install Izipay in Claude Code, Cursor or VS Code

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

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

What the publisher says

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

Izipay: common questions

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

More from codespar →