InvoiceFlow
REMOTE · INVOICEFLOW-TEN-AZURE.VERCEL.APP
Create invoices, clients, and Stripe payment links from any agent. 7 tools. No email or deletes.
Available components
Last scanned (17 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 566 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 4 Nov 26 +1
- Tool “invoiceflow_share_invoice” rewrote its description, which is the text the model reads security
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 67
First indexed and scored.
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 4 Nov 2026 · Probed https://invoiceflow-ten-azure.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of invoiceflow-ten-azure.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://invoiceflow-ten-azure.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://invoiceflow-ten-azure.vercel.app/api/mcp | HTTPS enforced | 308 | https://invoiceflow-ten-azure.vercel.app/api/mcp |
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 →
invoiceflow_create_client ~102
Create a customer record. A client is required before an invoice can be created. Returns the new client id.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional company name if it differs from name. |
| string | yes | Billing email. Required in practice - it is where the invoice goes if a human later sends it. | |
| name | string | yes | Customer or company name. Required. |
| notes | string | – | Optional internal note. Never shown to the customer. |
No output schema declared.
No examples provided.
invoiceflow_create_invoice ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| clientId | string | yes | id of an existing client, from list_clients or create_client. Required. |
| currency | string | – | 3-letter ISO code. Defaults to USD. |
| dueDate | string | – | Due date, ISO yyyy-mm-dd. If omitted, 14 days from today is used. |
| items | array | yes | One or more line items. At least one is required. |
| notes | string | – | Optional note printed on the invoice. |
| tax | integer | – | Optional total tax in INTEGER CENTS. Defaults to 0. |
No output schema declared.
No examples provided.
invoiceflow_get_invoice ~32
Fetch one invoice by id, including line items and derived totals.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Invoice id. |
No output schema declared.
No examples provided.
invoiceflow_list_clients ~41
List existing clients. Use this before create_client to avoid making duplicate customer records.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional search term matched against name or email. |
No output schema declared.
No examples provided.
invoiceflow_list_invoices ~74
List invoices with their status and totals. Invoices belonging to other accounts are not visible and return as absent, not as errors.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional maximum number of results. |
| status | string | – | Optional filter: DRAFT, SENT, PAID, OVERDUE, or CANCELLED. |
No output schema declared.
No examples provided.
invoiceflow_share_invoice ~61
Get the public payment page link for an invoice that is SENT or OVERDUE (drafts cannot be shared). The page shows a Pay button when the account owner has connected Stripe. Does not email anyone.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Invoice id. |
No output schema declared.
No examples provided.
invoiceflow_whoami ~39
Check which InvoiceFlow account this key belongs to and that the key works. Call this first; it is the cheapest way to fail early.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the InvoiceFlow MCP server?
InvoiceFlow is a hosted endpoint at https://invoiceflow-ten-azure.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · invoiceflow-ten-azure.vercel.app
claude mcp add --transport http earthypunyapat-invoiceflow 'https://invoiceflow-ten-azure.vercel.app/api/mcp'
What is the InvoiceFlow MCP server?
InvoiceFlow is an MCP server listed in the public MCP registry as io.github.EarthyPunyapat/invoiceflow. Create invoices, clients, and Stripe payment links from any agent. 7 tools. No email or deletes. This page covers its hosted endpoint (https://invoiceflow-ten-azure.vercel.app/api/mcp).
Is the InvoiceFlow MCP server safe to use?
InvoiceFlow scores 68 out of 100 on VerifyMCP. 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 InvoiceFlow MCP server expose?
InvoiceFlow exposes 7 tools: invoiceflow_whoami, invoiceflow_create_client, invoiceflow_list_clients, invoiceflow_create_invoice, invoiceflow_list_invoices, and 2 more. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.
Does the InvoiceFlow MCP server require authentication?
No. We connected to InvoiceFlow without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the InvoiceFlow MCP server still maintained?
InvoiceFlow is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.