InvoiceFlow MCP server
io.github.EarthyPunyapat/invoiceflowEarthyPunyapatstreamable-httpv1.0.0Scanned
Create invoices, clients, and Stripe payment links from any agent. 7 tools. No email or deletes.
7 tools: 2 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the InvoiceFlow MCP server can do
The InvoiceFlow MCP server is published by the GitHub account EarthyPunyapat. It has 7 tools. It can create or change data (2 tools: invoiceflow_create_client and invoiceflow_create_invoice), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 2Claude Code: ask
invoiceflow_create_clientCreate a customer record.No findings
Why it is in this group
- The name "invoiceflow_create_client" says "create": a word for a change.
Description, as the server wrote it Create a customer record. A client is required before an invoice can be created. Returns the new client id.
invoiceflow_create_invoiceCreate a DRAFT invoice for an existing client.No findings
Why it is in this group
- The name "invoiceflow_create_invoice" says "create": a word for a change.
Description, as the server wrote it 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.
Only reads 5Show 5 read-only tools
invoiceflow_get_invoiceFetch one invoice by id, including line items and derived totals.No findings
Why it is in this group
- The name "invoiceflow_get_invoice" says "get": a word for reading.
Description, as the server wrote it Fetch one invoice by id, including line items and derived totals.
invoiceflow_list_clientsList existing clients.No findings
Why it is in this group
- The name "invoiceflow_list_clients" says "list": a word for reading.
Description, as the server wrote it List existing clients. Use this before create_client to avoid making duplicate customer records.
invoiceflow_list_invoicesList invoices with their status and totals.No findings
Why it is in this group
- The name "invoiceflow_list_invoices" says "list": a word for reading.
Description, as the server wrote it List invoices with their status and totals. Invoices belonging to other accounts are not visible and return as absent, not as errors.
invoiceflow_whoamiCheck which InvoiceFlow account this key belongs to and that the key works.No findings
Why it is in this group
- The name "invoiceflow_whoami" says "whoami": a word for reading.
Description, as the server wrote it Check which InvoiceFlow account this key belongs to and that the key works. Call this first; it is the cheapest way to fail early.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://invoiceflow-ten-azure.vercel.app/api/mcp: tools/list returned 7 tools to an anonymous client, including invoiceflow_create_client (write), invoiceflow_create_invoice (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:invoiceflow_share_invoiceOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http invoiceflow https://invoiceflow-ten-azure.vercel.app/api/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http invoiceflow https://invoiceflow-ten-azure.vercel.app/api/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__invoiceflow__invoiceflow_whoami",
"mcp__invoiceflow__invoiceflow_list_clients",
"mcp__invoiceflow__invoiceflow_list_invoices",
"mcp__invoiceflow__invoiceflow_get_invoice",
"mcp__invoiceflow__invoiceflow_share_invoice"
],
"ask": [
"mcp__invoiceflow__invoiceflow_create_client",
"mcp__invoiceflow__invoiceflow_create_invoice"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as invoiceflow. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.EarthyPunyapat/invoiceflow/verify?hash=181ade15096c458ff3eceedb7036173da2bcee92d010ae71659c51f40bc0808a" | jq -e '.changed == false'Pinned hash 181ade15096c, from Nov 15, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.EarthyPunyapat/invoiceflow/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.EarthyPunyapat/invoiceflow)Source: MCP Registry · repository. Synced Nov 2, 2026, 03:17 UTC.
InvoiceFlow MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the InvoiceFlow MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the InvoiceFlow MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the InvoiceFlow MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the InvoiceFlow MCP server have?
- 7 tools: 2 write, 5 read. invoiceflow_create_client, invoiceflow_create_invoice, invoiceflow_whoami, invoiceflow_list_clients, invoiceflow_list_invoices, invoiceflow_get_invoice and invoiceflow_share_invoice.
Does the InvoiceFlow MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the InvoiceFlow MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the InvoiceFlow MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.