Ext Ops Panel
Open dashboard
Comparison

io.github.FurlPay/furlpay-cli vs io.github.KingPeque/coinvoyage

io.github.FurlPay/furlpay-cli is an MCP server published by FurlPay. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.KingPeque/coinvoyage is an MCP server published by KingPeque. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.FurlPay/furlpay-cliio.github.KingPeque/coinvoyage
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (npm): 227
Downloads/week (npm): 28
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 131
Downloads/week (npm): 21
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.FurlPay/furlpay-cli vs io.github.KingPeque/coinvoyage
Factio.github.FurlPay/furlpay-cliio.github.KingPeque/coinvoyage
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@furlpay/cli)On your machine (@kingpeque/coinvoyage-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/furlpay/furlpay-cligithub.com/kingpeque/coinvoyage-paykit
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.FurlPay/furlpay-cli

In its own words, on Official MCP Registry:

Stablecoin payments, swaps, stock orders, market data, travel booking, yield and card controls.

io.github.KingPeque/coinvoyage

In its own words, on Official MCP Registry:

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

How to run each

io.github.FurlPay/furlpay-cli As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio furlpay-cli -- npx -y @furlpay/cli mcp

io.github.KingPeque/coinvoyage As a local MCP server: npm package

Claude Code
claude mcp add --env "COINVOYAGE_API_KEY=<YOUR_COINVOYAGE_API_KEY>" --env "COINVOYAGE_API_SECRET=<YOUR_COINVOYAGE_API_SECRET>" --transport stdio coinvoyage -- npx -y @kingpeque/coinvoyage-mcp

Requires: COINVOYAGE_API_KEY, COINVOYAGE_API_SECRET (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.FurlPay/furlpay-cli publish no settings it asks for, so we do not compare settings.

What it can do: io.github.FurlPay/furlpay-cli · What it can do: io.github.KingPeque/coinvoyage · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built