io.github.codespar/mcp-moonpay

NPM · @CODESPAR/MCP-MOONPAY · SCANNED AUG 4

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

Available components

+24 this week 69 69 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security83

No malware found by supply-chain analysis.Pass
CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available. View diagnostics → Fail
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 42 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2489 tokens (~124/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management30

Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @codespar/mcp-moonpay

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add codespar-mcp-moonpay -- npx -y @codespar/mcp-moonpay

# add to Codex CLI

codex mcp add codespar-mcp-moonpay -- npx -y @codespar/mcp-moonpay

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "codespar-mcp-moonpay": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@codespar/mcp-moonpay"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add codespar-mcp-moonpay --command npx --arg -y --arg @codespar/mcp-moonpay

# ~/.hermes/config.yaml

mcp_servers:
  codespar-mcp-moonpay:
    command: "npx"
    args: ["-y", "@codespar/mcp-moonpay"]

// mcp.json

{
  "mcpServers": {
    "codespar-mcp-moonpay": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-moonpay"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

4 Aug 26 0
- CVE-2026-69207 affects this package: medium ▼ security
- Known CVEs: partial → fail ▼ security
2 Aug 26 +29
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
1 Aug 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 +10
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Install scripts: unverified → pass ▲ security
- Dependency health: partial → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
29 Jul 26 −19
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
27 Jul 26 45

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Aug 2026 · Analysed npm/@codespar/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 1 finding

ID	CVE	Severity	Vector	Fix available
GHSA-8j4g-w8fx-2239	CVE-2026-69207	medium	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L	yes

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 20 exposed · ~2,422 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

create_buy_transaction ~248

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.

Input Output Examples

Name	Type	Req	Description
baseCurrencyAmount	number	yes	Fiat amount to charge (major units)
baseCurrencyCode	string	yes	Fiat currency code (e.g. brl, usd)
currencyCode	string	yes	Crypto currency code to receive (e.g. btc, usdc)
customerId	string	—	Existing MoonPay customer id (use create_customer first)
externalCustomerId	string	—	Your internal user id, propagated to MoonPay for reconciliation
externalTransactionId	string	—	Your internal transaction reference
extraFields	object	—	Additional provider-specific fields passed through as-is
paymentMethod	string	—	Payment method (e.g. credit_debit_card, sepa_bank_transfer, pix)
returnUrl	string	—	Browser redirect after hosted flow completes
walletAddress	string	yes	Destination crypto wallet address
walletAddressTag	string	—	Destination tag / memo (for chains that require it, e.g. XRP, XLM)

No output schema declared.

No examples provided.

create_customer ~113

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

Input Output Examples

Name	Type	Req	Description
address	object	—	Residential address object
dateOfBirth	string	—	ISO date (YYYY-MM-DD)
email	string	yes	Customer email (used for MoonPay communications + KYC)
externalCustomerId	string	—	Your internal user id for correlation
firstName	string	—	Legal first name
lastName	string	—	Legal last name

No output schema declared.

No examples provided.

create_sell_transaction ~199

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

Input Output Examples

Name	Type	Req	Description
bankAccount	object	—	Destination bank account detail (country-specific fields)
baseCurrencyAmount	number	yes	Crypto amount to sell (major units)
baseCurrencyCode	string	yes	Crypto currency code (e.g. btc, usdc)
customerId	string	—	MoonPay customer id receiving the fiat payout
externalCustomerId	string	—	Your internal user id
externalTransactionId	string	—	Your internal transaction reference
extraFields	object	—	Additional provider-specific fields passed through as-is
payoutMethod	string	—	Fiat payout method (e.g. sepa_bank_transfer, pix)
quoteCurrencyCode	string	yes	Fiat currency to receive (e.g. usd, brl)
returnUrl	string	—	Browser redirect after hosted flow completes

No output schema declared.

No examples provided.

get_buy_quote ~207

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.

Input Output Examples

Name	Type	Req	Description
areFeesIncluded	boolean	—	If true, baseCurrencyAmount includes MoonPay fees.
baseCurrencyAmount	number	—	Amount in fiat to spend (major units). Either this or quoteCurrencyAmount must be supplied.
baseCurrencyCode	string	yes	Fiat currency you are paying with (e.g. usd, eur, brl, mxn)
currencyCode	string	yes	Crypto currency code you want to buy (e.g. btc, eth, usdc, sol). Must be a code returned by list_currencies.
paymentMethod	string	—	Optional payment method hint (e.g. credit_debit_card, sepa_bank_transfer, pix)
quoteCurrencyAmount	number	—	Amount of crypto to receive (major units). Either this or baseCurrencyAmount must be supplied.

No output schema declared.

No examples provided.

get_buy_transaction ~43

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	MoonPay transaction id

No output schema declared.

No examples provided.

get_currency ~61

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

Input Output Examples

Name	Type	Req	Description
currencyCode	string	yes	Currency code (e.g. btc, usdc, brl, usd)

No output schema declared.

No examples provided.

get_customer ~27

Retrieve a MoonPay customer by id.

Input Output Examples

Name	Type	Req	Description
id	string	yes	MoonPay customer id

No output schema declared.

No examples provided.

get_customer_kyc_status ~54

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	MoonPay customer id

No output schema declared.

No examples provided.

get_sell_quote ~167

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.

Input Output Examples

Name	Type	Req	Description
baseCurrencyAmount	number	—	Crypto amount to sell (major units). Either this or quoteCurrencyAmount must be supplied.
currencyCode	string	yes	Crypto currency code you want to sell (e.g. btc, usdc)
payoutMethod	string	—	Optional payout method hint (e.g. sepa_bank_transfer, credit_debit_card, pix)
quoteCurrencyAmount	number	—	Fiat amount to receive (major units). Either this or baseCurrencyAmount must be supplied.
quoteCurrencyCode	string	yes	Fiat currency to receive (e.g. usd, eur, brl)

No output schema declared.

No examples provided.

get_sell_transaction ~36

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	MoonPay sell transaction id

No output schema declared.

No examples provided.

get_transaction_receipt ~70

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

Input Output Examples

Name	Type	Req	Description
id	string	yes	MoonPay transaction id (buy or sell)
type	string	—	Whether the id refers to a buy or sell transaction. Defaults to buy.

No output schema declared.

No examples provided.

get_user_country ~84

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.

Input Output Examples

Name	Type	Req	Description
ipAddress	string	—	Optional IP to check. If omitted, MoonPay resolves from the request origin.

No output schema declared.

No examples provided.

list_buy_transactions ~86

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

Input Output Examples

Name	Type	Req	Description
customerId	string	—	Filter to a single MoonPay customer id
externalCustomerId	string	—	Filter to your internal user id
limit	number	—	Max results to return
status	string	—	Filter by transaction status (e.g. pending, completed, failed)

No output schema declared.

No examples provided.

list_countries ~41

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.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_currencies ~71

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.

Input Output Examples

Name	Type	Req	Description
show	string	—	Filter to enabled currencies only, or return everything. Defaults to enabled on the API side.

No output schema declared.

No examples provided.

list_customer_transactions ~77

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

Input Output Examples

Name	Type	Req	Description
customerId	string	yes	MoonPay customer id
limit	number	—	Max results to return
status	string	—	Optional status filter (e.g. pending, completed, failed)

No output schema declared.

No examples provided.

list_payment_methods ~90

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.

Input Output Examples

Name	Type	Req	Description
country	string	—	ISO-3166 alpha-2 country code (e.g. BR, US, MX)
currencyCode	string	—	Fiat currency code (e.g. brl, usd, eur)

No output schema declared.

No examples provided.

refund_sell_transaction ~99

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.

Input Output Examples

Name	Type	Req	Description
amount	number	—	Optional partial refund amount (in the transaction's base/crypto currency). Omit for full refund.
id	string	yes	MoonPay sell transaction id to refund
reason	string	—	Reason code or free-text justification for the refund

No output schema declared.

No examples provided.

sign_buy_url ~353

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.

Input Output Examples

Name	Type	Req	Description
baseCurrencyAmount	number	—	Pre-fill fiat amount
baseCurrencyCode	string	—	Fiat currency code (e.g. usd, brl)
colorCode	string	—	Hex accent color for the widget
currencyCode	string	yes	Crypto currency code to buy (e.g. btc, usdc)
email	string	—	Pre-fill end-user email
externalCustomerId	string	—	Your internal user id, propagated to MoonPay
externalTransactionId	string	—	Your internal transaction reference
extraParams	object	—	Additional widget parameters passed through as-is (object values are JSON-stringified)
language	string	—	BCP-47 language tag (e.g. en, pt-BR)
paymentMethod	string	—	Pre-select payment method (e.g. credit_debit_card, pix)
quoteCurrencyAmount	number	—	Pre-fill crypto amount
redirectURL	string	—	Where to redirect after the hosted flow completes
showWalletAddressForm	boolean	—	If true, force the widget to show the wallet form even when prefilled
theme	string	—	Widget theme (light / dark)
walletAddress	string	—	Pre-fill destination wallet address
walletAddressTag	string	—	Destination tag / memo for chains that require it

No output schema declared.

No examples provided.

sign_sell_url ~296

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.

Input Output Examples

Name	Type	Req	Description
baseCurrencyAmount	number	—	Pre-fill crypto amount
baseCurrencyCode	string	yes	Crypto currency code being sold (e.g. btc, usdc)
colorCode	string	—	Hex accent color for the widget
email	string	—	Pre-fill end-user email
externalCustomerId	string	—	Your internal user id
externalTransactionId	string	—	Your internal transaction reference
extraParams	object	—	Additional widget parameters passed through as-is (object values are JSON-stringified)
language	string	—	BCP-47 language tag (e.g. en, pt-BR)
payoutMethod	string	—	Pre-select payout method (e.g. sepa_bank_transfer, pix)
quoteCurrencyAmount	number	—	Pre-fill fiat amount
quoteCurrencyCode	string	—	Fiat currency to receive (e.g. usd, brl)
redirectURL	string	—	Where to redirect after the hosted flow completes
refundWalletAddress	string	—	Wallet to refund crypto to if the sell fails
theme	string	—	Widget theme (light / dark)

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 4 Aug

Day	Score
27 Jul	45
28 Jul	45
29 Jul	26
31 Jul	36
1 Aug	40
2 Aug	69
3 Aug	69
4 Aug	69