MCP.Market

Airwallex MCP server

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

MCP server for Airwallex — cross-border collection + payouts, global accounts, FX, transfers

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

full report

Adoption
Established

271 stars21 downloads/wk

Reviews

Write one

Nobody has reviewed Airwallex yet.

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

Airwallex tools (20, 11 write)

write = sends, deletes, buys or posts

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

  • cancel_payment_intentwrite action

    Cancel a payment intent that has not yet been captured. Fails on already-captured intents; use create_refund instead.

  • cancel_transferwrite action

    Cancel a transfer that has not yet settled. Only works while the transfer is in an early status (e.g. APPROVED, IN_PROGRESS before funds leave). Fails on DELIVERED transfers.

  • capture_payment_intent

    Capture a previously-authorized payment intent (two-step auth + capture flow). Use this after confirm_payment_intent on intents created with capture_method=manual. Amount may be less than authorized for partial capture.

  • confirm_payment_intent

    Confirm a previously-created payment intent with a payment method. For card intents this triggers authorization; for APM intents this returns a next_action (redirect, QR, etc).

  • create_beneficiarywrite action

    Create a transfer beneficiary (recipient) with bank details. Required before sending cross-border payouts via create_transfer. Entity type, bank details fields, and required IDs vary by destination country.

  • create_conversionwrite action

    Execute an FX conversion between wallet currencies (e.g. swap USD received into BRL before settling locally). Pass quote_id for a locked quoted rate, or omit for a market rate.

  • create_customerwrite action

    Create an Airwallex customer for saved payment methods and recurring charges. Returns a customer object whose id can be passed into create_payment_intent.customer_id.

  • create_payment_intentwrite action

    Create an Airwallex payment intent (pay-in). Used when a LatAm seller needs to collect USD/EUR/GBP from buyers abroad. Returns the intent with client_secret for client-side confirmation.

  • create_refundwrite action

    Refund a captured payment intent (full or partial). Returns the refund object with status.

  • create_transferwrite action

    Send a cross-border transfer to a pre-created beneficiary. Supports same-currency payouts (source_currency === transfer_currency) or FX-inclusive payouts. Use quote_id from a prior quote for locked rates.

  • list_beneficiaries

    List beneficiaries. Supports pagination and filters by entity_type, nickname and bank_country_code.

  • list_payment_intents

    List payment intents with optional filters (status, merchant_order_id, date range). Supports pagination via page_num / page_size.

  • list_transfers

    List transfers with optional filters (status, date range). Supports pagination.

  • retrieve_balance

    Retrieve the current wallet balance for every currency the account holds.

  • retrieve_beneficiary

    Retrieve a beneficiary by id. Returns bank details, entity_type, and allowed payment_methods.

  • retrieve_customer

    Retrieve a customer by id. Returns the customer profile plus metadata.

  • retrieve_payment_intent

    Retrieve a payment intent by id. Returns current status, payment_attempts, and latest payment_method.

  • retrieve_refundwrite action

    Retrieve a refund by id. Returns current status (RECEIVED, ACCEPTED, PROCESSING, SUCCEEDED, FAILED).

  • retrieve_transferwrite action

    Retrieve a transfer by id. Returns current status (APPROVED, IN_PROGRESS, DELIVERED, CANCELLED, etc).

  • update_customerwrite action

    Update fields on an existing customer (email, phone, address, metadata). Immutable fields like merchant_customer_id cannot be changed.

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 Airwallex 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
55%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 28,688 servers
Downloads a week
21
more than 8% of 12,191 servers with a package

What its tools let an agent do: 9 read · 6 create · 3 change · 2 delete

Install Airwallex in Claude Code, Cursor or VS Code

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

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

What the publisher says

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

Airwallex: common questions

Is Airwallex MCP server safe?
Mostly: it is graded B (82/100). Read the Airwallex safety report
How do I install Airwallex?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Airwallex need an API key?
Yes. The registry entry asks for AIRWALLEX_API_KEY.
Is Airwallex maintained?
The last commit was 67 days ago (2026-08-29). The latest release is v0.2.2.
How does Airwallex 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 55% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from codespar →