Log inSubmit server
BlindPay logo

BlindPay

Manage BlindPay instances, customers, KYC/KYB, bank accounts, virtual accounts, RFIs, and stablecoin payment workflows through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install BlindPay

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "blindpay": {
      "command": "npx",
      "args": [
        "-y",
        "@blindpay/mcp"
      ],
      "env": {
        "BLINDPAY_API_KEY": "YOUR_VALUE_HERE",
        "BLINDPAY_INSTANCE_ID": "YOUR_VALUE_HERE",
        "BLINDPAY_MCP_PROFILE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

BlindPay MCP server connects AI assistants to BlindPay’s stablecoin payment API for global payment operations. It supports instance administration, customer onboarding, KYC/KYB records, RFIs, bank accounts, virtual accounts, terms-of-service flows, and customer limits. Use the hosted Streamable HTTP endpoint with OAuth 2.1, or run the npm package locally over stdio with an API key and instance ID. Development instances simulate settlement and automatically approve customers, while production instances move real funds.

Use cases

  • Onboard individual and business customers
  • Review and resolve pending compliance RFIs
  • Manage customer bank-account destinations
  • Create virtual accounts for stablecoin payins
  • Inspect instance onboarding and customer limits

Key features

  • Remote Streamable HTTP and local stdio transports
  • OAuth 2.1 or API-key authentication
  • Customer KYC and KYB management
  • Bank-account and virtual-account operations
  • Read-only tool profile
  • Instance, member, and compliance administration

Tools92

What BlindPay lets your agent do. Expand a tool for its parameters.

Verified live~50.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

10/10 checks healthy over the last 45d

What it can do

From the 92 tools this server returned when we ran it; 92 declare their own safety hints.

Runs commands · 2Can delete or modify data · 8Handles credentials · 11Makes network requests · 92Read-only tools · 82
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age293 days
Maintainers2

Observed 2026-10-26 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @blindpay/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars9Stargazers on the source repository.
npm downloads1.2kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Tools exposed92Callable tools this server registers over MCP.

How BlindPay works

What BlindPay does

BlindPay exposes BlindPay’s stablecoin payment infrastructure through the Model Context Protocol. The available operations cover instance and onboarding data, members and roles, compliance requests, customers, payout destinations, and virtual accounts.

Customer creation starts KYC for individuals or KYB for businesses. The required fields depend on the customer type and verification configuration. Businesses use standard KYB, while individual records can use the supported standard flow. Customers begin in a verifying state; development instances approve them automatically.

Virtual accounts accept inbound USD deposits through ACH, wire, or RTP and convert those deposits into stablecoins delivered to a linked wallet. The API also supports Plaid Link creation and bank-account destinations for customers.

How it works

The hosted endpoint is https://mcp.blindpay.com/mcp and uses Streamable HTTP. Authentication uses OAuth 2.1 with PKCE: the client opens a browser, the user signs in to BlindPay, and the connection is scoped to the selected instance and role.

The local package runs with npx -y @blindpay/mcp over stdio. Local authentication uses a BlindPay API key and an instance ID. The server provides a full tool profile by default. Setting BLINDPAY_MCP_PROFILE=readonly limits exposure to GET operations, including status, balances, and history, and removes tools for actions such as signing wallet messages and managing webhook access.

Setup and configuration

For a local connection, create a BlindPay account, create a development instance, generate an API key in the dashboard, and copy the instance ID from the dashboard URL. Node.js and npm are required.

A local client configuration needs:

  • BLINDPAY_API_KEY: the BlindPay API key.
  • BLINDPAY_INSTANCE_ID: the instance selected for API operations.
  • BLINDPAY_MCP_PROFILE: optional profile selection; use readonly for GET-only tools.

The remote connection does not require an API key. Clients can point to the hosted URL and complete BlindPay sign-in. Local execution can also run in Docker with the same API key and instance ID environment variables.

Tools and capabilities

The tool set includes operations to:

  • Retrieve and update instance details, business profiles, ownership documents, members, and member roles.
  • Check the bound instance, its onboarding state, and whether it is a development or production environment.
  • Retrieve and submit pending instance-level or customer-level requests for information.
  • Start terms-of-service acceptance and use the returned terms identifier during customer creation.
  • Create, retrieve, update, and delete individual or business customers.
  • Retrieve customer limits and request limit increases.
  • Create Plaid Link sessions and manage customer bank accounts.
  • Create and manage virtual accounts that convert eligible USD deposits into stablecoins.

Customer bank-account fields vary by payment rail and country. Some rails require additional tax, phone, business-industry, or regional information. File fields used for customer verification must be publicly fetchable HTTPS URLs.

Limitations and notes

Check the bound instance before moving money. Development instances simulate settlement and do not move real funds; production instances process real funds. A customer’s onboarding or KYC state determines which bank-account rails are available.

Terms of service must be accepted by a person in a browser. The API creates an acceptance URL but cannot complete the acceptance itself. After acceptance, the redirect includes a tos_id, and a tos.accept webhook is emitted.

Submitting an RFI response is only valid when a pending RFI exists. If none exists, the operation returns a failure result and the caller should retrieve the RFI state again instead of retrying.

Virtual-account fees depend on deposit size. Deposits below $100 accrue the BlindPay fee to the billing cycle, while deposits of $100 or more deduct the transaction fee from the delivered amount. Deposits are processed regardless of size and deliver at least $0.01 on-chain; an optional partner fee is taken only from the remaining amount.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about BlindPay

BlindPay is an MCP server that connects AI assistants to BlindPay’s stablecoin payment API. Its main tools manage instances, customers, KYC/KYB data, bank accounts, virtual accounts, onboarding RFIs, terms-of-service flows, and customer limits. It supports remote Streamable HTTP with OAuth 2.1 or local stdio authenticated by an API key.

Install it locally with `npx -y @blindpay/mcp`, or connect a client to `https://mcp.blindpay.com/mcp`. Local use requires Node.js, npm, `BLINDPAY_API_KEY`, and `BLINDPAY_INSTANCE_ID`; the hosted endpoint uses BlindPay sign-in through OAuth 2.1.

Yes, BlindPay works with Cursor through either the hosted HTTP endpoint or the local npm server. Configure the hosted URL in Cursor, or run `npx -y @blindpay/mcp` with `BLINDPAY_API_KEY` and `BLINDPAY_INSTANCE_ID` in `~/.cursor/mcp.json`.

Yes, set `BLINDPAY_MCP_PROFILE=readonly` when running the local server. The readonly profile exposes GET operations for status, balances, and history while excluding write operations and selected wallet and webhook-access tools.

No, development instances simulate settlement and do not move real funds. Check the instance `type` before money movement; production instances process real funds, and an `onboarding_step` of `completed` indicates that the instance can transact.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBlindPay AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/blindpay?style=directory)](https://allmcps.com/mcp/blindpay)
HTML Embed
<a href="https://allmcps.com/mcp/blindpay"><img src="https://allmcps.com/api/badge/blindpay?style=directory" alt="BlindPay on AllMCPs" /></a>