Name: InvoiceFlow
Author: EarthyPunyapat

InvoiceFlow MCP

Create invoices, clients, and Stripe payment links from any agent. 7 tools. No email or deletes.

Tool-list grade A Remote · Streamable HTTP API key 7 tools v1.0.0

No reviews yet by EarthyPunyapatGitHub The publisher’s own endpoint — this marketplace is not in the path

96/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Create invoices, clients, and Stripe payment links from any agent. 7 tools. No email or deletes.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http invoiceflow-mcp https://invoiceflow-ten-azure.vercel.app/api/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

# 2 — ask your agent for something these tools do
#   invoiceflow_whoami, invoiceflow_create_client, invoiceflow_list_clients and 4 more

It needs AUTHORIZATION (Bearer token: `Bearer ifk_...` where ifk_... is an InvoiceFlow API key. Without it the server lists tools but every call explains what is missing): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.

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

Publishernot claimed

EarthyPunyapat1 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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.

Claude Codedeclared by this listing

This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer token: `Bearer ifk_...` where ifk_... is an InvoiceFlow API key. Without it the server lists tools but every call explains what is missing) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).

claude mcp add --scope user --transport http invoiceflow-mcp https://invoiceflow-ten-azure.vercel.app/api/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

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

Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer token: `Bearer ifk_...` where ifk_... is an InvoiceFlow API key. Without it the server lists tools but every call explains what is missing.. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.

What you approve

7 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

Check which InvoiceFlow account this key belongs to and that the key works. Call this first; it is the cheapest way to fail early.

No parameter schema on file.

Create a customer record. A client is required before an invoice can be created. Returns the new client id.

Parameter	Type	Required	Notes
name	string	yes	Customer or company name. Required.
email	string	yes	Billing email. Required in practice - it is where the invoice goes if a human later sends it.
company	string	no	Optional company name if it differs from name.
notes	string	no	Optional internal note. Never shown to the customer.

List existing clients. Use this before create_client to avoid making duplicate customer records.

Parameter	Type	Required	Notes
query	string	no	Optional search term matched against name or email.

Create a DRAFT invoice for an existing client. Amounts are INTEGER CENTS: unitPrice 25000 means $250.00, not $25,000. Do not send totals - the server derives subtotal and total from the line items. Does not email anyone.

Parameter	Type	Required	Notes
clientId	string	yes	id of an existing client, from list_clients or create_client. Required.
items	array	yes	One or more line items. At least one is required.
dueDate	string	no	Due date, ISO yyyy-mm-dd. If omitted, 14 days from today is used.
currency	string	no	3-letter ISO code. Defaults to USD.
notes	string	no	Optional note printed on the invoice.
tax	integer	no	Optional total tax in INTEGER CENTS. Defaults to 0.

List invoices with their status and totals. Invoices belonging to other accounts are not visible and return as absent, not as errors.

Parameter	Type	Required	Notes
status	string	no	Optional filter: DRAFT, SENT, PAID, OVERDUE, or CANCELLED.
limit	integer	no	Optional maximum number of results.

Fetch one invoice by id, including line items and derived totals.

Parameter	Type	Required	Notes
id	string	yes	Invoice id.

Get the payable Stripe Checkout link for an invoice. This is what you give a human so they can actually pay. Does not email anyone.

Parameter	Type	Required	Notes
id	string	yes	Invoice id.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

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

ATool-list grade · score 96 / 100

Release 1.0.0 · scanned 2 Nov 2026

Graded from the tools this server lists, not from its source code.

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 score96

Findings0 threat · 0 capability

Capabilityminimal

Coveragemanifest

Verificationnot in this report

Surface digest9d8563cd65f4e1203aa7c798daed8209d3587f9150b030160521bcbca06209df

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

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.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

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
invoiceflow_whoami	no tags
invoiceflow_create_client	no tags
invoiceflow_list_clients	no tags
invoiceflow_create_invoice	no tags
invoiceflow_list_invoices	no tags
invoiceflow_get_invoice	untrusted-input	untrusted-input: keyword "fetch"
invoiceflow_share_invoice	no tags

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 digest9d8563cd65f4e120

Scanned2026-11-02

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.