Coinvoyage

io.github.KingPequePublished by GitHub account KingPequev0.1.2Updated Oct 24, 2026

CoinVoyage MCP — create crypto PayOrders, webhooks, swaps across Bitcoin/Solana/EVM chains.

Overview

AI-generated overview

Community MCP server that lets an assistant create and check CoinVoyage crypto PayOrders, manage webhooks, and get swap quotes across Bitcoin, Solana and EVM…

What you can do
  • Create and check crypto PayOrders, including DEPOSIT invoices and, with the secret, SALE and REFUND orders
  • Manage webhooks for order events
  • Get swap quotes and look up supported chains and tokens
  • Call the CoinVoyage REST API directly from the assistant (15 tools in total)
When to use it
Useful when you are building crypto checkout, donation pages or stablecoin settlement into an app and want the assistant to create test invoices, register webhooks or fetch swap quotes against CoinVoyage without leaving the editor.
Requirements
Runs locally over stdio as the npm package @kingpeque/coinvoyage-mcp (Node.js). Requires a CoinVoyage public API key in COINVOYAGE_API_KEY; the optional COINVOYAGE_API_SECRET unlocks SALE/REFUND orders, fee claims and webhook management. COINVOYAGE_API_BASE_URL overrides the default api.coinvoyage.io endpoint. Network access to the CoinVoyage API is needed.
Before you install
COINVOYAGE_API_SECRET is a privileged server-side secret enabling SALE/REFUND orders, fee claims and webhook management; leave it unset to limit the assistant to read and DEPOSIT flows. Tools create orders and register webhooks, which change state on your merchant account. Real payments incur CoinVoyage's 1.5% fee. The integration is community-maintained and not officially affiliated with CoinVoyage.

Installation

In SourceWeft

  1. Open Coinvoyage in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

coinvoyage-paykit-claudeplugin

Claude Code plugin for integrating CoinVoyage — a non-custodial, multi-chain crypto payment gateway — into any app you build with Claude.

Bundles two surfaces:

  1. Skill (coinvoyage-payments) — triggers whenever Claude is helping with crypto payments, checkout, stablecoins, or web3 payment work. Guides the integration end to end: server-side PayOrder creation, React PaymentWidget, webhook signature verification, and REST API fallback for non-JS stacks.
  2. MCP server (@kingpeque/coinvoyage-mcp) — gives Claude 15 tools for calling the CoinVoyage API directly: create PayOrders, check status, manage webhooks, get swap quotes, and more.

Community-maintained integration. Not officially affiliated with CoinVoyage.

Install

bash
/plugin install KingPeque/coinvoyage-paykit

You'll be prompted at install for:

FieldRequiredNotes
api_keyyesYour public API key from https://dashboard.coinvoyage.io → Developers
api_secretoptionalNeeded for SALE/REFUND orders, webhook management, and fee claims. Leave blank to restrict Claude to read + DEPOSIT flows only.
api_base_urloptionalDefaults to https://api.coinvoyage.io

The secret is stored in your system keychain via Claude Code's sensitive-config pathway — it never lands in a file you'd commit.

What you can now say to Claude

Once installed, these kinds of requests will activate the skill and/or MCP tools:

  • "Add crypto payments to my Next.js checkout"
  • "I want to accept Bitcoin on from my site"
  • "Build a donation page that takes any crypto while I settle to USDC on base"
  • "Create a $25 test invoice and settle to USDC on Base heres my wallet"
  • "Register a webhook at https://mysite.com/api/webhooks/coinvoyage for completed orders"

What's inside

coinvoyage-paykit/├── .claude-plugin/│   └── plugin.json              # Plugin manifest (prompts user for API keys)├── mcp.json                     # Declares the bundled MCP server├── skills/│   └── coinvoyage-payments/│       └── SKILL.md             # Integration guide + trigger description├── mcp-server/                  # Source for @kingpeque/coinvoyage-mcp (npm)│   ├── src/index.ts│   ├── package.json│   └── tsconfig.json├── README.md└── LICENSE

Supported chains

Bitcoin, Solana, Ethereum, Optimism, Arbitrum, Base, BSC, Polygon, Sui — plus any ERC-20 / SPL / native token on these chains. See full chain ID reference in the supported_chains MCP tool.

Pricing (CoinVoyage's, not this plugin's)

  • 1.5% per successful payment
  • 0% offramp
  • Merchants can add a custom percentage fee on top
  • This plugin is free and MIT-licensed. Volume discounts on CoinVoyage fees: [email protected].

Security posture

  • No secrets in this repo. Everything sensitive lives in your Claude Code config, injected into the MCP server at runtime.
  • Per-user keys. Every builder uses their own CoinVoyage API key. Nothing is centrally hosted; there's no shared server to compromise.
  • Minimal network surface. The MCP server only talks to api.coinvoyage.io (or your configured override).
  • HMAC-SHA256 authentication for privileged operations (SALE/REFUND/webhooks/fee claims).
  • Open source. Read the MCP server source at mcp-server/src/index.ts — it's under 300 lines.

Local development

bash
git clone https://github.com/KingPeque/coinvoyage-paykitcd coinvoyage-paykit/mcp-servernpm installnpm run build# Point your MCP client at ./mcp-server/dist/index.js with COINVOYAGE_API_KEY set

Run the skill locally by symlinking skills/coinvoyage-payments/ into ~/.claude/skills/ (or installing the plugin in dev mode).

Contributing

Issues and PRs welcome at https://github.com/KingPeque/coinvoyage-paykit/issues. Please don't commit API keys, secrets, or wallet addresses.

License

MIT — see LICENSE.

Links

Source: README.md at commit b60fb89

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% 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 days25 pts

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

  • Auth declared10 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
  • License10 pts