Is BlindPay open source?

Partly. Some of BlindPay is published as source (https://github.com/blindpaylabs/blindpay-mcp) and some is not. Checked as of 2026-10-21.

Which chains does BlindPay support?

BlindPay lists support for Multichain as of 2026-10-21.

Is BlindPay still maintained?

The most recent code activity Sato Hub observed was on 2026-10-20 (last commit 2026-10-20, last release 2026-09-21), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.

How do I install or run BlindPay?

Node.js (npm package, run via npx). Install: npx -y @blindpay/mcp. Entry: {"mcpServers": {"blindpay": {"command": "npx", "args": ["-y", "@blindpay/mcp"], "env": {"BLINDPAY_API_KEY": "your-api-key-here", "BLINDPAY_INSTANCE_ID": "your-instance-id-here"}}}}. Sato Hub reproduced this install in a container on 2026-09-21. It runs as an MCP server (npx -y @blindpay/mcp (stdio); also: claude mcp add --transport stdio blindpay --env BLINDPAY_API_KEY=... --env BLINDPAY_INSTANCE_ID=... -- npx -y @blindpay/mcp).

Is BlindPay verified on Sato Hub?

Sato Hub holds one earned check for BlindPay: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 78 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.

Payment Rail

BlindPay

Official MCP server for BlindPay's stablecoin payment rails: payouts, payins, virtual accounts, and FX quotes.

Sato Score78
ChainsMultichain

ActiveUnverifiedActive · today

BlindPay is a partly open-source payment rail, with last code activity on 2026-10-20 (Active). Latest release on 2026-09-21. Sato Score 78/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install BlindPay →

Last commit Oct 20, 2026 · Last release Sep 21, 2026 (v1.8.0) · ★ 10

Listed from blindpay.com on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21. Evidence →

Website ↗Docs ↗GitHub ↗X / Twitter ↗

Next step

Watch BlindPay

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp

Run Sato Hub Preflight on blindpaylabs/blindpay-mcp before I use it.

Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

BlindPay is API-first infrastructure connecting stablecoins to local payment rails, business accounts, and compliance checks, focused on cross-border payment corridors including LatAm. Its official MCP server lets an AI agent create receivers, initiate payouts/payins across blockchains, manage virtual accounts, fetch FX quotes, and configure webhooks — the same operations available through BlindPay's REST API.

Sato Score

78/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness: 35/35
Code transparency: 14/20
Interface verifiability: 8/10
Docs & demo: 6/10
Listing transparency & provenance: 12/15
Independent verification: 3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

View verification & embed badge →History →How the Sato Score works

Sato Check

v1.8.0 · as of 2026-09-29

Does it take your key?: No key read found
Does your key leave?: Not yet run
Can it move funds on its own?: Unknown

Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from blindpay.com on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21.

Claim	Value	Evidence	Source	Checked
Chains supported	Multichain	self-reported	blindpay.com	as of 2026-10-21
Verification status	Unverified — not independently reviewed	self-reported	blindpay.com	as of 2026-10-21
Recent activity	last release 2026-09-21 · last commit 2026-10-20	observed	github.com/blindpaylabs/blindpay-mcp	2026-10-21
Install works	reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour	✓ reproduced	github.com/blindpaylabs/blindpay-mcp	2026-09-21
Website answers	answered (HTTP 200)	observed	blindpay.com	2026-10-21
Daily check record	90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history	observed	—	2026-10-20
Takes your key	no private-key read found in what we read	traced	satohub.ai	2026-09-29
Key leaves the machine	not yet run with planted test keysthe sandbox lane has not run on this version	observed	satohub.ai	not dated
Moves funds on its own	unknown — could not read what it exposes	traced	satohub.ai	2026-09-29
Works with	Cursor, Claude Code, Claude Desktop, Codexconfidence 0.90	self-reported	github.com/blindpaylabs/blindpay-mcp	as of 2026-07-26
Docs	https://blindpay.com/docs/getting-started/overviewconfidence 0.90	self-reported	github.com/blindpaylabs/blindpay-mcp	as of 2026-07-26
X account	https://twitter.com/blindpayconfidence 0.85	self-reported	github.com/blindpaylabs/blindpay-mcp	as of 2026-07-26
Sato Score	78/100 (High)how open, active and verifiable — not a safety or quality grade	computed	satohub.ai	2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Sep 21, 2026

Runtime: Node.js (npm package, run via npx)

npx -y @blindpay/mcp
{"mcpServers": {"blindpay": {"command": "npx", "args": ["-y", "@blindpay/mcp"], "env": {"BLINDPAY_API_KEY": "your-api-key-here", "BLINDPAY_INSTANCE_ID": "your-instance-id-here"}}}}

You supply: BLINDPAY_API_KEY (required, from BlindPay Dashboard), BLINDPAY_INSTANCE_ID (required, format in_xxxxxxxxxxxx)

MCP invocation: npx -y @blindpay/mcp (stdio); also: claude mcp add --transport stdio blindpay --env BLINDPAY_API_KEY=... --env BLINDPAY_INSTANCE_ID=... -- npx -y @blindpay/mcp

Read from the project’s own docs as of 2026-09-21. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

100%of 91 checks since 2026-07-23 succeeded

Currently responding for 91 days

Succeeded: 91
Failed: 0
Their error: 0
Unattributed: 0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded

100%

7-day rolling; unattributable days are gaps · 30/30 days

Tools listed

fewer than 2 points—

from the server's own tools/list · 0/30 days

Sato Score

as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains: Multichain
Agent types: MCP server
Open source: Partial
Works with: Cursor, Claude Code, Claude Desktop, Codex
Last checked: 2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#payments#stablecoins#mcp#payouts#fx

Where BlindPay fits

Payments

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

What's Changed feat: sync MCP with API changes (v1.6.8) by @BernardoSM in #15 Full Changelog : v1.6.7...v1.6.8

Multichain

GitHub ↗

Listing History

Recorded changes to BlindPay's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

Sep 26, 2026
Edited: entity class, resource type
Sep 21, 2026
Sato Score tier: Medium → High
Score 68 → 78.
Sep 21, 2026
Verified: deploy spec
Sep 21, 2026
New release published
Aug 8, 2026
New release published
Jul 27, 2026
6 releases tracked
Showing the 2 most recent. Full release history is retained in the listing record.
Jul 26, 2026
Auto-enriched: docs url, x url, supported integrations
Jul 24, 2026
Sato Hub began tracking this listing
Jul 19, 2026
Listed on Sato Hub

Compared with

Alternatives to BlindPay →

Appears in

Active★ 9.5k

Reference

QuestionsWhat people ask about this pageShowHide

Cite this pagePlain text, APA or BibTeXShowHide

Cite this page

Sato Hub. "BlindPay — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/blindpay

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

BlindPay

Next step

Watch BlindPay

Check it from your agent

Your project?

Overview

Sato Score

Sato Check

Evidence — listed vs checked · what the words mean

Install — reproduced in a container Sep 21, 2026

Observed record — 91 daily checks since 2026-07-23

Last 30 days — to 2026-10-21, one point per UTC day

Details

Marketplace Signals

Where BlindPay fits

Recent Activity

blindpay-mcp v1.8.0

blindpay-mcp v1.7.1

blindpay-mcp v1.7.0

blindpay-mcp v1.6.12

blindpay-mcp v1.6.9

blindpay-mcp v1.6.8

Listing History

Compared with

Appears in

Related Resources

Coinbase AgentKit

Hyperliquid

Model Context Protocol (MCP)

Questions people ask about BlindPay

Cite this page

Join the Sato Hub Briefing