servers / peru-payments-mercado-pago-yape-pagoefectivo
Peru Payments (Mercado Pago — Yape / PagoEfectivo) MCP server
communitystreamable_httpremotebrokenbroken
Peru payments for AI agents — Yape / PagoEfectivo via Mercado Pago. Never holds funds.
01Tools · 3
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| query_payment_status Check whether a Peru payment (created by create_payment_link) has been paid. Queries Mercado Pago directly — pull-based, no webhook needed. paid=true when status is PAID (Mercado Pago APPROVED). | read | false | unknown |
| create_payment_link Create a payment link in PEN for Peru via Mercado Pago. Buyer pays with Yape, PagoEfectivo cash, cards, Mercado Pago wallet. Returns a hosted checkout URL the buyer opens to pay — payment completes automatically, no confirm step. Bring your own credentials via HTTP header (x-mercadopago-access-token; free test credentials from mercadopago.com developers never move real money). Money always flows buyer→Mercado Pago→merchant; this service never touches funds. | write | true | unknown |
| refund_payment Refund a paid payment (created by create_payment_link). Full refund by default; pass amount for a partial refund where supported. Refunds respect the same owner policy guardrails (x-agentpay-max-amount) as payments — the amount is checked before anything is sent to the gateway. | destructive | true | true |
02Install & source
https://mcp-pe.wishpool.app/mcp
remote_url- repohttps://github.com/junter1989k-ai/peru-payments-mcp
- homepagehttps://mcp-pe.wishpool.app/mcp
- licenseMIT
- adoption0 stars · 0 forks
03Access granted
Process payments · writeProcess payments · destructive
The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-08-23 23:17Z
next_check2026-08-24 02:17Z
cadenceevery 3h
verifiedhandshake:failed metadata:failed handshake:failed metadata:failed handshake:failed metadata:failed handshake:failed metadata:failed handshake:failed metadata:failed
index_statusindex — 9 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README. 
[](https://mcpexplorer.com/servers/peru-payments-mercado-pago-yape-pagoefectivo)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →