MCP.Market

Moonpay MCP server

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

MCP server for MoonPay — fiat-to-crypto on/off-ramp, 100+ assets; Pix for Brazil onramp

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

full report

Adoption
Established

271 stars19 downloads/wk

Reviews

Write one

Nobody has reviewed Moonpay yet.

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

Moonpay tools (20, 8 write)

write = sends, deletes, buys or posts

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

  • create_buy_transactionwrite action

    Create a buy transaction (fiat -> crypto). The returned object contains status plus — depending on method — redirect URL for hosted checkout, Pix QR data, or card auth next steps.

  • create_customerwrite action

    Create a MoonPay customer (KYC'd end user). Required before creating transactions that must be tied to an identified individual.

  • create_sell_transactionwrite action

    Create a sell transaction (crypto -> fiat). Used for agents that need to pay out in local fiat after receiving crypto.

  • get_buy_quotewrite action

    Preview a fiat -> crypto buy quote in real time. Use this before create_buy_transaction to show the end user the exact crypto amount, fees, and effective rate.

  • get_buy_transactionwrite action

    Retrieve a buy transaction (fiat -> crypto) by its MoonPay id. Returns current status and settlement detail.

  • get_currency

    Retrieve metadata for a single currency (fiat or crypto) by its MoonPay code. Returns network, decimals, min/max amounts, fee structure.

  • get_customer

    Retrieve a MoonPay customer by id.

  • get_customer_kyc_status

    Fetch KYC verification status (and any pending document requirements) for a MoonPay customer. Use to gate flows that require an approved customer before transacting.

  • get_sell_quote

    Preview a crypto -> fiat sell quote in real time. Use this before create_sell_transaction to show the end user the exact fiat amount, fees, and effective rate.

  • get_sell_transaction

    Retrieve a sell transaction (crypto -> fiat) by its MoonPay id.

  • get_transaction_receipt

    Fetch a tax-/audit-grade receipt for a completed buy or sell transaction. Useful for end-user reporting or accounting export.

  • get_user_country

    Resolve the caller's (or a given IP's) country via MoonPay's IP-address geolocation endpoint. Returns ISO alpha-2 + alpha-3 country, plus state for US. Compliance helper to gate flows by jurisdiction before quoting or creating a transaction.

  • list_buy_transactionswrite action

    List buy transactions with optional filters. Used for reconciliation and agent-driven monitoring.

  • list_countries

    List countries supported by MoonPay along with which flows (buy / sell / NFT) are allowed per geography. Use this to gate UI before initiating a quote.

  • list_currencies

    List supported currencies (fiat + crypto). Essential for agents: use this to discover currency codes dynamically rather than hard-coding, and to check which assets/fiats are currently enabled.

  • list_customer_transactions

    List all transactions (buy + sell) tied to a single MoonPay customer. Convenience wrapper for unified history / reconciliation by user.

  • list_payment_methods

    List payment methods supported for a given fiat currency / country combination (e.g. credit_debit_card, sepa_bank_transfer, pix). Use to populate checkout selectors dynamically.

  • refund_sell_transactionwrite action

    Request a refund on an off-ramp (sell) transaction. Used when the destination bank rejects payout or the user disputes the trade. Reason codes are MoonPay-defined.

  • sign_buy_urlwrite action

    Build and HMAC-SHA256 sign a MoonPay buy widget URL (buy.moonpay.com). Returns a ready-to-redirect URL with the merchant's apiKey + signature appended. Requires MOONPAY_PUBLISHABLE_KEY and MOONPAY_SECRET_KEY in the environment. Use when embedding the hosted onramp in your own UI.

  • sign_sell_url

    Build and HMAC-SHA256 sign a MoonPay sell widget URL (sell.moonpay.com). Returns a ready-to-redirect URL with apiKey + signature appended. Requires MOONPAY_PUBLISHABLE_KEY and MOONPAY_SECRET_KEY in the environment.

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 Moonpay compares

Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 73% of 1,761 Finance servers
Tools
20
the typical Finance server has 8
Tools that change things
40%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 946 Finance servers
Downloads a week
19
more than 5% of 421 Finance servers with a package

What its tools let an agent do: 12 read · 3 create · 5 change

Install Moonpay in Claude Code, Cursor or VS Code

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

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

What the publisher says

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

Moonpay: common questions

Is Moonpay MCP server safe?
Mostly: it is graded B (82/100). Read the Moonpay safety report
How do I install Moonpay?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Moonpay need an API key?
Yes. The registry entry asks for MOONPAY_API_KEY, MOONPAY_SECRET_KEY.
Is Moonpay maintained?
The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.
What can I use instead of Moonpay?
Servers from other publishers that do the same job: Pyth Pro MCP Server, Orla MCP server and Cryptoetf MCP server. Compare all Moonpay alternatives.
How does Moonpay compare with other Finance MCP servers?
safety score 82/100 (higher than 73% of 1,761 Finance servers); tools 20 (the typical Finance server has 8); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Moonpay

Same job from other publishers: the closest match first, then the best rated.

All Moonpay alternatives →
  • Pyth Pro MCP Server
    Real-time and historical price feeds for 500+ crypto, equities, FX, and commodities assets.
    A
  • Orla
    Personal, family and business books over fiat and crypto. Reads and records; it cannot pay.
    A
  • Cryptoetf
    Live spot crypto ETF flows for 16 assets and their funds, CEFI index and prices.
    A
  • Blockrun
    Web search, deep research, prediction markets & crypto data for AI agents. Pay per call via x402.
    B
  • Yolfi Payments MCP
    Let AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks.
    A
Moonpay vs Pyth Pro MCP Server

More from codespar →