Mexico Payments (Mercado Pago — OXXO cash)

app.wishpoolPublished by wishpool.appOfficial publisherv0.1.0Updated Oct 24, 2026

Mexico payments for AI agents — OXXO cash via Mercado Pago. Never holds funds.

The publisher's own server: Algeria Payments (Chargily Pay — EDAHABIA / CIB)

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant create and manage OXXO cash payments in Mexico through Mercado Pago, without holding funds itself.

What you can do
This remote MCP server exposes Mexico-focused payment capabilities built on Mercado Pago, centered on OXXO cash payment flows. Based on the description, it lets an assistant initiate or handle OXXO cash payments for agents. The manifest lists no tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to support OXXO cash payments in Mexico, for example in checkout or order flows where customers pay in cash at a store. It is not aimed at general payment processing outside that market or method.
Requirements
It runs as a remote streamable HTTP endpoint, so no local runtime or package is needed. The manifest declares no authentication, environment variables, or headers, but the actual endpoint may still require credentials; confirm before relying on it.
Before you install
It handles payment flows, so treat any money movement or payment creation as sensitive and verify amounts and recipients. The description states it never holds funds, but the manifest documents no authentication, so confirm how access is controlled before connecting it to real transactions.

Installation

In SourceWeft

  1. Open Mexico Payments (Mercado Pago — OXXO cash) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.wishpool%2Fmexico-payments-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mexico-payments-mercado-pago-oxxo-cash": {
      "type": "http",
      "url": "https://mcp-mx.wishpool.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Wishpool integrations