Is Cryptoapis Mcp X402 Pay free?

Yes, Cryptoapis Mcp X402 Pay is free to use.

How do I install Cryptoapis Mcp X402 Pay?

Cryptoapis Mcp X402 Pay is a local plugin. Install it using npm package: @cryptoapis-io/mcp-x402-pay and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Cryptoapis Mcp X402 Pay safe to use?

Yes. Cryptoapis Mcp X402 Pay passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What AI apps work with Cryptoapis Mcp X402 Pay?

Cryptoapis Mcp X402 Pay uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Cryptoapis Mcp X402 Pay MCP Server

by cryptoapis-io

FinanceLow Risk10.0LocalNew

Free

MCP server that pays x402-gated HTTP endpoints — fetch, and on a 402 authorize, sign, retry

About

MCP server that pays x402-gated HTTP endpoints — fetch, and on a 402 authorize, sign, retry

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (2 strong, 3 medium validity signals). 2 code issues detected. No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (14/14 approved). 3 finding(s) downgraded by scanner intelligence.

11 files analyzed · 3 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cryptoapis-io-mcp-x402-pay": {
      "args": [
        "-y",
        "@cryptoapis-io/mcp-x402-pay"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@cryptoapis-io/mcp-x402-pay

This is the BUYER side of x402 — the tool an agent uses to spend (pay for a resource). Merchants who want to charge for an API use the middleware SDK (@cryptoapis-io/x402-merchant-sdk), not an MCP tool.

An MCP server that lets an AI agent pay x402-gated HTTP endpoints. One tool, x402_pay: it fetches a URL and, if the server returns 402 Payment Required, it authorizes the payment via the CryptoAPIs buyer service, signs locally, retries, and returns the paid response.

Non-custodial: the private key is passed per request and never leaves the process (no HTTP server — stdio only).

Supported today: EVM (eip712, e.g. Base USDC) and Solana. Tron, Bitcoin/UTXO, XRP and Kaspa are upcoming — wired but not yet enabled; paying on them returns a clear family_not_yet_supported ("coming soon") result.

Run

node dist/cli.js            # stdio MCP server (no --api-key at startup; keys are per-tool-call)

Prerequisite — an agent `walletId`

x402_pay pays from a CryptoAPIs agent wallet (walletId). Create one ONCE per blockchain+network before paying — a single POST to the buyer API returns the id (non-custodial: you register only your PUBLIC address):

curl -X POST https://ai.cryptoapis.io/x402/buyer/wallets \
  -H "x-api-key: $CRYPTOAPIS_API_KEY" -H "content-type: application/json" \
  -d '{"blockchain":"base","network":"eip155:8453","address":"0xYourAddress"}'
# → { "walletId": "…" }

network MUST be the CAIP-2 id (eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, …), not a bare name — and exactly one of address (any chain; required for Solana/Kaspa) or xpub (xpub-capable chains). A malformed body returns a clear 400 malformed_request. Set the returned id as X402_WALLET_ID (or pass walletId).

Tool: `x402_pay`

Input	Required	Description
`url`	✓	the (possibly paywalled) resource
`apiKey`	✓	your CryptoAPIs key (X402_BUYER feature) — only used to call the buyer `/authorize`
`walletId`	✓	the wallet record id from `POST /wallets` (a registry `_id`) — NOT the on-chain address (an address gets `wallet_not_found`)
`privateKey`	✓	the wallet's EVM key — signs locally, never sent anywhere
`method`/`body`/`headers`		the request to make
`allowedNetworks`		restrict which CAIP-2 networks to pay on
`maxAmount`		safety cap — refuse if the required atomic-unit amount exceeds it

Returns { status, paid, body, settlement? }. On a 402 with no acceptable option (or over maxAmount), paid:false with a reason — nothing is signed or paid.

Flow

fetch(url). Not 402 → return it.
402 → pick an accepts entry (allowlist-aware), authorize via buyer /authorize → the signing artifact.
Sign locally (@cryptoapis-io/mcp-signer evm_sign typed-data) → build the x402 PaymentPayload (wire scheme is always exact; the family is in network).
Retry with the base64 X-PAYMENT header; return the paid response + the X-PAYMENT-RESPONSE settlement.

Security

The private key is a tool parameter and may be logged by MCP clients or stored in conversation history — use only in trusted local environments. This mirrors @cryptoapis-io/mcp-signer.