BlindPay MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to BlindPay stablecoin payment-account tools: Do required payment scopes and beneficiary data boundaries remain explicit before agent-initiated transfers?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Operate stablecoin global payment workflows and associated receiver/account administration through an official MCP server.

What we know

Official BlindPay MCP server: stablecoin payouts, payins, quotes and receivers for global payments. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@blindpay/mcp 1.8.0 published 2026-09-21T12:53:24.377Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Credential-scoped payment initiation and payment infrastructure administration Writes: Create and process real payouts and payins; Create and modify receivers and virtual accounts; Manage webhooks and API keys.
BlindPay instance-scoped API key
Sensitive access: API key, Beneficiary information, Payment data, Instance configuration

Potential high-impact side effects: Create and process real payouts and payins, Create and modify receivers and virtual accounts, Manage webhooks and API keys.
Live payouts can transfer value and may be irreversible

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do required payment scopes and beneficiary data boundaries remain explicit before agent-initiated transfers?

The bounded review of the publisher's documented BlindPay stablecoin payment-account tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potential high-impact side effects: Create and process real payouts and payins, Create and modify receivers and virtual accounts, Manage webhooks and API keys.
Credential-scoped payment initiation and payment infrastructure administration
BlindPay instance-scoped API key
Payment instructions, beneficiary/receiver details and financial identifiers are processed by BlindPay and its payment infrastructure.
Reviewed write actions: Create and process real payouts and payins; Create and modify receivers and virtual accounts; Manage webhooks and API keys
Sensitive access: API key, Beneficiary information, Payment data, Instance configuration
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Live payouts can transfer value and may be irreversible
Instance and API-key permissions control real financial authority
Do not equate API-driven payouts with local-wallet signing
This API-key MCP has real payout/pay-in authority; it must not be described as merely preparing unsigned wallet transactions.

Original activity observations

@blindpay/mcp 1.8.0 published 2026-09-21T12:53:24.377Z

Technical identity

npm/@blindpay/mcp

Exact implementation source: https://www.npmjs.com/package/@blindpay/mcp ↗
Reviewed resource type: MCP Server
Repository identity: blindpaylabs/blindpay-mcp
Package identity: npm:@blindpay/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@blindpay/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
blindpaylabs/blindpay-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Recommended hosted endpoint with OAuth 2.1; alternative local `npx -y @blindpay/mcp` needs BLINDPAY_API_KEY and BLINDPAY_INSTANCE_ID. Codex: codex mcp add blindpay --url https://mcp.blindpay.com/mcp
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add --transport http blindpay https://mcp.blindpay.com/mcp
Configure / authenticate
MCP100 setup guide
Prefer remote OAuth at `https://mcp.blindpay.com/mcp` (Claude: `claude mcp add --transport http blindpay https://mcp.blindpay.com/mcp`); stdio alternative `npx -y @blindpay/mcp` requires BLINDPAY_API_KEY and BLINDPAY_INSTANCE_ID.
Previously reviewed client configuration / prerequisites: Two alternatives: remote Streamable HTTP https://mcp.blindpay.com/mcp authenticates via OAuth 2.1 PKCE user sign-in and instance selection; local npx -y @blindpay/mcp uses BLINDPAY_API_KEY and BLINDPAY_INSTANCE_ID. Do not require both mechanisms together.
Check connection
Suggested check
Check authenticated tool discovery and read-only account/instance information; do not create transfers.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `blindpay-mcp`, run `claude mcp remove blindpay-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove blindpay-mcp

Official Documentation & Sources

What it does

Official BlindPay MCP server: stablecoin payouts, payins, quotes and receivers for global payments. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: Operate stablecoin global payment workflows and associated receiver/account administration through an official MCP server.

Representative uses

Create and manage payment receivers
Create payouts and payins
Fetch FX quotes and payment status
Manage virtual accounts, wallets, webhooks and API keys

Limitations

Live payouts can transfer value and may be irreversible
Instance and API-key permissions control real financial authority
Do not equate API-driven payouts with local-wallet signing
This API-key MCP has real payout/pay-in authority; it must not be described as merely preparing unsigned wallet transactions.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: BlindPay instance-scoped API key
Permissions: Credential-scoped payment initiation and payment infrastructure administration
Data handling: Payment instructions, beneficiary/receiver details and financial identifiers are processed by BlindPay and its payment infrastructure.
Cost: service_and_transaction_dependent
Risk and cautions: Potential high-impact side effects: Create and process real payouts and payins, Create and modify receivers and virtual accounts, Manage webhooks and API keys.

Access scope and cautions

Write actions: Create and process real payouts and payins Create and modify receivers and virtual accounts Manage webhooks and API keys
Sensitive access: API key Beneficiary information Payment data Instance configuration
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Create and manage payment receivers; Create payouts and payins; Fetch FX quotes and payment status; Manage virtual accounts, wallets, webhooks and API keys.

What authentication is documented?

BlindPay instance-scoped API key

Can it modify data or perform write operations?

Documented write actions include: Create and process real payouts and payins; Create and modify receivers and virtual accounts; Manage webhooks and API keys. Recorded permission boundary: Credential-scoped payment initiation and payment infrastructure administration

What data-handling boundary should I consider?

Payment instructions, beneficiary/receiver details and financial identifiers are processed by BlindPay and its payment infrastructure. Recorded sensitive-access context: API key; Beneficiary information; Payment data; Instance configuration.

What limitations and risks should I check before use?

Potential high-impact side effects: Create and process real payouts and payins, Create and modify receivers and virtual accounts, Manage webhooks and API keys. Live payouts can transfer value and may be irreversible. Instance and API-key permissions control real financial authority. Do not equate API-driven payouts with local-wallet signing. This API-key MCP has real payout/pay-in authority; it must not be described as merely preparing unsigned wallet transactions. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is service and transaction dependent. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.