Name: Whiteflow
Author: vishal4742

Whiteflow MCP

USDT payment links, payments and collection summaries on Whitechain testnet. Can't move money.

Grade A Local · stdio API key 14 tools v0.3.0 MIT

No reviews yet by vishal4742npm Runs on your machine, nothing hosted

99/100

trust score

tools declared

local

runs on your machine

—

downloads a day

What it does

USDT payment links, payments and collection summaries on Whitechain testnet. Can't move money.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user whiteflow-mcp '--' npx -y whiteflow-mcp

# 2 — ask your agent for something these tools do
#   get_business_profile, search_customers, create_customer and 11 more

Whiteflow costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

vishal47421 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Whiteflow as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user whiteflow-mcp '--' npx -y whiteflow-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take WHITEFLOW_MODE (sandbox (default: local simulator, no key) or testnet), WHITEFLOW_API_KEY (Your sk_test_ key from the Whiteflow dashboard (testnet only)), WHITEFLOW_TIMEZONE (Business time zone for due dates and weekly summaries, e.g. Asia/Kolkata) if you want to set them.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

The signed-in business: name, environment (sandbox or testnet), time zone and today's date there, supported price currencies, invoice currency, payment methods and limits, and what this API key may do. Call it first, and resolve relative dates ("next Friday") against its today.

No parameter schema on file.

Find existing customers by name or email (part of either). Returns stable customer ids with a masked email. Use it before create_customer, and to turn a name into the customer_id an invoice needs.

Parameter	Type	Required	Notes
query	string	yes	Part of the customer's name or email, e.g. "Acme".
limit	integer	no	At most this many, 1 to 20.

Create a customer with only what's needed: a name, and an email if the merchant gives one. Refuses a likely duplicate (same name or email) and lists it instead; pass confirm_new only after the merchant confirms it's a different customer.

Parameter	Type	Required	Notes
name	string	yes	The customer's or company's name, as the merchant said it.
email	string	no	Optional email, only if the merchant gave it.
confirm_new	boolean	no	true only after the merchant confirmed that a listed possible duplicate is a different customer.
idempotency_key	string	no	Optional, advanced: your own key for this exact request. Leave it out normally: a retry of an unresolved request is resumed automatically.
create_another	boolean	no	true only when the merchant deliberately wants a second record identical to one just created (e.g. two identical sales). Never to retry an error.

Verified payments received, newest first: amount in USDT, refunded amount, time, the related invoice or link, and evidence (an explorer link on testnet). A cursor pages through older ones.

Parameter	Type	Required	Notes
limit	integer	no	How many, 1 to 100.
cursor	string	no	The next_cursor of the previous page.

Money collected in a period (gross, fees, refunds, net and count, per currency) and, where the backend has invoices, what is outstanding and overdue now. Days are the business's own time zone. Give a period, or from and to.

Parameter	Type	Required	Notes
period	string	no	this_week starts on Monday. Default: this_week.
from	string	no	YYYY-MM-DD, inclusive (with to; instead of period).
to	string	no	YYYY-MM-DD, inclusive.

Save a private invoice DRAFT (not sent, not payable) for an existing customer_id: line items with quantity × unit price, a due date, and only an explicit discount or tax the merchant stated.

Parameter	Type	Required	Notes
customer_id	string	yes	From search_customers or create_customer. Never a name.
currency	string	yes	Must be "USDT".
line_items	array	yes	—
due_date	string	yes	YYYY-MM-DD in the business time zone; today or later.
discount		no	Only if the merchant asked for one.
tax	object	no	Only a tax the merchant explicitly named, with its rate. Never infer one.
memo	string	no	Optional note shown on the invoice.
idempotency_key		yes	—
create_another		yes	—

Change a DRAFT before publication: customer, line items, due date, discount, tax or memo (give only what changes; discount: null / tax: null removes one).

Parameter	Type	Required	Notes
invoice	string	yes	The invoice id (inv_…) or its number (WF-1042).
customer_id	string	no	—
line_items	array	no	—
due_date	string	no	—
discount		no	Only if the merchant asked for one.
tax	object	no	Only a tax the merchant explicitly named, with its rate. Never infer one.
memo	string	no	—
idempotency_key		yes	—

Ask to publish a reviewed DRAFT. This doesn't publish by itself: Whiteflow creates an approval request for this exact version (total, currency, customer), and an Owner of the business approves it on the review page; then the invoice gets its number and payment URL.

Parameter	Type	Required	Notes
invoice	string	yes	The invoice id (inv_…) or its number (WF-1042).
idempotency_key		yes	—

An invoice's status (draft, awaiting approval, open, overdue, paid), totals, amount paid and still due, due date, payment URL, and its verified payments. Paid status comes only from Whiteflow's verified payment records.

Parameter	Type	Required	Notes
invoice	string	yes	The invoice id (inv_…) or its number (WF-1042).

Invoices newest first, filtered by customer, status (draft, open, paid, overdue) and due-date range, with a cursor for the next page. Amounts stay in each invoice's own currency.

Parameter	Type	Required	Notes
customer_id	string	no	—
status	string	no	—
due_from	string	no	YYYY-MM-DD, inclusive.
due_to	string	no	YYYY-MM-DD, inclusive.
limit	integer	no	—
cursor	string	no	The next_cursor of the previous page.

Draft a payment reminder for an open invoice: subject, body, the intended recipient and the payment URL. It does NOT send anything (sent: false); the merchant reviews and sends it.

No parameter schema on file.

Create a hosted payment link and return its URL and status. It is NOT sent to anyone: the merchant shares the URL. Single-use by default (one payment closes it).

Parameter	Type	Required	Notes
amount	string	yes	The price as a decimal string in currency, e.g. "15000" or "15000.00" (at most 2 decimals for fiat, 6 for USDT).
currency	string	yes	The price's currency, as the merchant stated it. Ask if unclear; don't assume.
description	string	yes	What it's for, shown to the customer, e.g. "Acme website redesign".
customer_id	string	no	Optional customer id from search_customers/create_customer (sandbox backend only).
reference	string	no	Optional merchant reference (unique per link), e.g. an order number.
expires_on	string	no	Optional last day the link can be paid, YYYY-MM-DD in the business time zone (it closes at the end of that day).
single_use	boolean	no	true (default): closes after one payment. false: a reusable link.
idempotency_key		yes	—
create_another		yes	—

A payment link's current status (active, paid, expired, cancelled) and the verified payments made through it, newest first, from Whiteflow's own records.

Parameter	Type	Required	Notes
link_id	string	yes	The link id, like lnk_…, from create_payment_link.

Writes whose outcome is still unknown or needs reconciliation (after a timeout, a lost reply, or a reply that didn't match the request), or one write by its idempotency_key: what was attempted, when, and what Whiteflow's records say.

Parameter	Type	Required	Notes
idempotency_key	string	no	One operation; leave out to list every unresolved one.
acknowledge	boolean	no	With idempotency_key: the merchant checked this record; stop treating it as unresolved.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Whiteflow or to call it, at any volume.

ATrust score 99 / 100

Release 0.3.0 · scanned 8 Nov 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score99

Findings1 threat · 0 capability

Capabilityminimal

Coveragesource

Verificationrepo

Surface digeste4acdb77e91a37ff39b5b377580f408b539c8fcd46b1e100c04e653aa9ebaa1b

Score vectorthreat 100 → client 99

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfacenot available

Implementation sourceread

Package metadataread

Live transportnot available

No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
No per-tool rows for this release — see the note below.

No tool surface was enumerated, so there is nothing to attribute a capability to.

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digeste4acdb77e91a37ff

Scanned2026-11-08

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.