Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Whiteflow

NPM · WHITEFLOW-MCP

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

Available components

0 this week 71 Trust /100

Last scanned (21 hours ago)

Scores higher than 42% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2014 tokens (~143/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 0
    • Security disclosure: fail → pass ▲ functional
  • 7 Nov 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/whiteflow-mcp@0.3.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~1,952 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_customer ~187

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.

NameTypeReqDescription
confirm_newboolean–true only after the merchant confirmed that a listed possible duplicate is a different customer.
create_anotherboolean–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.
emailstring–Optional email, only if the merchant gave it.
idempotency_keystring–Optional, advanced: your own key for this exact request. Leave it out normally: a retry of an unresolved request is resumed automatically.
namestringyesThe customer's or company's name, as the merchant said it.

No output schema declared.

No examples provided.

create_invoice_draft ~292

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. Invoices are in USDT, the settlement asset: if the merchant priced in another currency, ask for the USDT amounts or offer a payment link; never convert. Never invent a tax rate. Resolve a relative due date ("next Friday") with get_business_profile's today and confirm the resulting date.

NameTypeReqDescription
create_anotherboolean–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.
currencystringyesMust be "USDT".
customer_idstringyesFrom search_customers or create_customer. Never a name.
discount––Only if the merchant asked for one.
due_datestringyesYYYY-MM-DD in the business time zone; today or later.
idempotency_keystring–Optional, advanced: your own key for this exact request. Leave it out normally: a retry of an unresolved request is resumed automatically.
line_itemsarrayyes–
memostring–Optional note shown on the invoice.
taxobject–Only a tax the merchant explicitly named, with its rate. Never infer one.

No output schema declared.

No examples provided.

create_payment_link ~349

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). currency is the price's currency, exactly as the merchant said it (₹ → INR, $ → USD); never convert it yourself. A price not in USDT is converted by Whiteflow at checkout.

NameTypeReqDescription
amountstringyesThe price as a decimal string in `currency`, e.g. "15000" or "15000.00" (at most 2 decimals for fiat, 6 for USDT).
create_anotherboolean–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.
currencystringyesThe price's currency, as the merchant stated it. Ask if unclear; don't assume.
customer_idstring–Optional customer id from search_customers/create_customer (sandbox backend only).
descriptionstringyesWhat it's for, shown to the customer, e.g. "Acme website redesign".
expires_onstring–Optional last day the link can be paid, YYYY-MM-DD in the business time zone (it closes at the end of that day).
idempotency_keystring–Optional, advanced: your own key for this exact request. Leave it out normally: a retry of an unresolved request is resumed automatically.
referencestring–Optional merchant reference (unique per link), e.g. an order number.
single_useboolean–true (default): closes after one payment. false: a reusable link.

No output schema declared.

No examples provided.

finalize_invoice ~152

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. A conversation 'yes' is not that approval. The connector re-checks the totals first and refuses if they don't add up. Nothing is emailed or sent.

NameTypeReqDescription
idempotency_keystring–Optional, advanced: your own key for this exact request. Leave it out normally: a retry of an unresolved request is resumed automatically.
invoicestringyesThe invoice id (inv_…) or its number (WF-1042).

No output schema declared.

No examples provided.

get_business_profile ~67

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`.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_collection_summary ~109

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.

NameTypeReqDescription
fromstring–YYYY-MM-DD, inclusive (with to; instead of period).
periodstring–this_week starts on Monday. Default: this_week.
tostring–YYYY-MM-DD, inclusive.

No output schema declared.

No examples provided.

get_invoice ~77

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.

NameTypeReqDescription
invoicestringyesThe invoice id (inv_…) or its number (WF-1042).

No output schema declared.

No examples provided.

get_operation_status ~133

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. Pass acknowledge: true only after the merchant has checked the record themselves; it clears the local flag so a new, identical request can be made.

NameTypeReqDescription
acknowledgeboolean–With idempotency_key: the merchant checked this record; stop treating it as unresolved.
idempotency_keystring–One operation; leave out to list every unresolved one.

No output schema declared.

No examples provided.

get_payment_link ~63

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

NameTypeReqDescription
link_idstringyesThe link id, like lnk_…, from create_payment_link.

No output schema declared.

No examples provided.

list_invoices ~115

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.

NameTypeReqDescription
cursorstring–The `next_cursor` of the previous page.
customer_idstring––
due_fromstring–YYYY-MM-DD, inclusive.
due_tostring–YYYY-MM-DD, inclusive.
limitinteger––
statusstring––

No output schema declared.

No examples provided.

list_payments ~80

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.

NameTypeReqDescription
cursorstring–The `next_cursor` of the previous page.
limitinteger–How many, 1 to 100.

No output schema declared.

No examples provided.

prepare_invoice_reminder ~70

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.

NameTypeReqDescription
invoicestringyesThe invoice id (inv_…) or its number (WF-1042).

No output schema declared.

No examples provided.

search_customers ~87

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.

NameTypeReqDescription
limitinteger–At most this many, 1 to 20.
querystringyesPart of the customer's name or email, e.g. "Acme".

No output schema declared.

No examples provided.

update_invoice_draft ~171

Change a DRAFT before publication: customer, line items, due date, discount, tax or memo (give only what changes; `discount: null` / `tax: null` removes one). It creates a new revision, and any pending publication approval for the old one is cancelled. Published invoices can't be edited.

NameTypeReqDescription
customer_idstring––
discount–––
due_datestring––
idempotency_keystring–Optional, advanced: your own key for this exact request. Leave it out normally: a retry of an unresolved request is resumed automatically.
invoicestringyesThe invoice id (inv_…) or its number (WF-1042).
line_itemsarray––
memo–––
tax–––

No output schema declared.

No examples provided.

Install

How do I install the Whiteflow MCP server?

Whiteflow runs locally as an npm package, launched with npx -y whiteflow-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · whiteflow-mcp

# add to Claude Code
claude mcp add vishal4742-whiteflow -- npx -y whiteflow-mcp
Common questions

What is the Whiteflow MCP server?

Whiteflow is an MCP server listed in the public MCP registry as io.github.Vishal4742/whiteflow. USDT payment links, payments and collection summaries on Whitechain testnet. Can't move money. This page covers its npm package (whiteflow-mcp).

Is the Whiteflow MCP server safe to use?

Whiteflow scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Whiteflow MCP server expose?

Whiteflow exposes 14 tools: get_business_profile, search_customers, create_customer, create_payment_link, get_payment_link, and 9 more. Their descriptions and schemas cost roughly 1,952 tokens of context every time the server is loaded.

Is the Whiteflow MCP server still maintained?

Whiteflow is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Whiteflow MCP server under?

Whiteflow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Whiteflow MCP server?

VerifyMCP ran 15 checks on Whiteflow, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Whiteflow: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.