Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Furlpay Cli

by FurlPayversion 0.2.2i★ –iRuns on your computer
Registry nameio.github.FurlPay/furlpay-cli

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Online shops & payments

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add furlpay-cli -- npx -y @furlpay/cli mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "furlpay-cli": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@furlpay/cli",
        "mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account FurlPay, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Online shops & paymentsi

  • More stars than 0% of the other 1742 servers in this category
  • Published to the registry more recently than 17% of the other 1742 servers in this category
  • Basic checks equal to or better than 100% of the other 1742 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Furlpay Cli safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Stripe MCP

by stripe

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

Runs in the cloud★ 2,043MITUpdated 12 months ago
Install

MCP Cn Commerce

by TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

Runs on your computer★ 96MITUpdated 27 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@furlpay/cli

Phase 5 hardening adds Windows DPAPI configuration encryption, durable payment retry keys and HTTPS-only directory links. See the implementation status and remaining integration requirements. Matching automatic payment requests reuse their saved key; use an explicit new --idempotency-key only for a separate payment after reconciling the previous one.

FurlPay's terminal client for reviewed account-to-account payments and freshness-aware financial monitoring.

The payment review follows the supplied dark fintech reference: mint confirmations, violet panels, rounded terminal geometry, a wide two-column profile and transfer layout, and responsive compact layouts. It adapts to TrueColor, 256-colour, basic ANSI, NO_COLOR, and narrow terminals.

Tech stack

LayerImplementation
RuntimeNode.js 22+, JavaScript with native CommonJS
Terminal UIANSI rendering with TrueColor, 256-colour, basic colour and NO_COLOR support
NetworkHTTPS REST snapshots, SSE and optional WebSocket transport through ws
CredentialsWindows DPAPI CurrentUser encryption; POSIX file permissions
VerificationNode.js built-in test runner and build checks
AutomationGitHub Actions matrix for Node 22/24 on Linux, macOS and Windows

Completion status

The terminal UI, monitoring client, Windows credential encryption, durable retry keys and HTTPS-only profile links are implemented. Production readiness is still incomplete: certificate pinning and request signatures, macOS Keychain/Linux Secret Service, backend quote and atomic settlement verification, production event feeds, and release signing remain open. See the Phase 5 status report for exact boundaries. Pushing this source does not publish an npm package or deploy the backend.

Install

Requires Node.js 22 or newer.

npm install -g @furlpay/cli

furlpay login

Payments

The executable flow fetches a new server quote, binds it to the reviewed recipient, amount, currency, source account, verification and sanctions decision, then asks for a single-key confirmation. The server remains the authority for authorization, fees, limits, balance and settlement.

# Safe, labelled offline recreation of the supplied reference. It never calls an API.

furlpay pay --demo

Authoritative quote review. This fetches current server data and never sends.

furlpay pay '@recipient' 10.00 USD --dry-run

Interactive terminal only: press y once the review screen is shown.

furlpay pay '@recipient' 10.00 USD

Scripted execution needs explicit intent and keeps a reconciliation key.

furlpay pay '@recipient' 10.00 USD --yes --idempotency-key invoice_20261029_001

PowerShell treats an unquoted @handle as a splat expression. Quote it as shown above. The CLI does not fabricate a recipient, quote, account balance, payment ID, or settlement outcome. If an execution request has an unknown outcome, it prints the idempotency key and requires reconciliation before a retry.

Live monitoring

Every monitor starts with the signed-in account's REST snapshot. It only displays LIVE after an authenticated event stream delivers authoritative, committed events with source and ingestion timestamps. REST-only values are marked UNKNOWN or DELAYED; data is hidden during SYNCING, STALE, and OFFLINE states.

furlpay dashboard --live

furlpay wallet balance --watch furlpay chains status --watch furlpay transactions --live furlpay directory '@recipient' --watch furlpay security monitor furlpay ledger --watch

The inspected backend exposes authenticated snapshots for wallets, transactions, chains, directory profiles, and selected admin data. It does not yet expose a general authenticated financial event feed, a Stripe payment feed, or an organisation-scoped customer feed. The CLI surfaces those gaps as UNKNOWN or OFFLINE rather than claiming live data. An SSE or WebSocket feed can be enabled with a same-origin endpoint:

furlpay dashboard --live --stream-path /api/events/stream --transport sse

furlpay dashboard --live --stream-path /api/events/ws --transport ws

The required event contract, source matrix, security controls, benchmarks, and failover evidence are in docs/cli.

Other commands

furlpay whoami

furlpay env sandbox furlpay balance --output json furlpay wallet address furlpay swap USDT USDC 100 --quote-only furlpay tx list furlpay invest portfolio furlpay travel search --city Tokyo --checkin 2026-12-01 --checkout 2026-12-05 furlpay card list furlpay earn furlpay completion bash|zsh|fish|powershell

MCP and AI clients

furlpay mcp

The MCP server exposes current, permission-scoped read tools and labels their freshness as UNKNOWN unless upstream provenance is available. It rejects financial mutations because a model must not manufacture payment approval. Use the interactive payment flow for payments.

{ "mcpServers": { "furlpay": { "command": "furlpay", "args": ["mcp"] } } }

Security model

  • Session cookies are sent only to the configured same-origin API over HTTPS, except loopback sandbox HTTP.
  • Terminal text from APIs is stripped of ANSI, OSC clipboard sequences, bidirectional overrides, hidden controls, and zero-width characters.
  • Every payment checks a fresh authenticated quote before confirmation and again immediately before execution.
  • Payment completion requires server-issued transaction evidence; a timeout, disconnect, approval, or pending state never becomes success.
  • Event updates are subject- and organisation-scoped, sequenced, deduplicated, gap-detected, reconciled from a snapshot after reconnection, and size-limited.

Development

npm ci

npm run build npm test npm run docs:preview npm run benchmark

The package uses Node.js CommonJS and one audited runtime dependency, ws, for optional authenticated WebSocket subscriptions. CI tests Node 22 and 24 on Ubuntu, macOS, and Windows.

Local verification on 29 October 2026 (Windows, Node.js 26.7.0): build check passed; all 75 tests passed. This does not replace the Node 22/24 CI matrix or production integration verification.

Documentation

  • Real-time architecture
  • Authoritative data-source matrix
  • Streaming security audit
  • Measured local benchmarks
  • Failover test evidence

License

MIT

Ask PopNx