# InvoiceFlow (remote · invoiceflow-ten-azure.vercel.app)

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

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `invoiceflow-ten-azure.vercel.app`: 68/100 (this document), [markdown](https://verifymcp.io/servers/earthypunyapat-invoiceflow/api-mcp.md), [page](https://verifymcp.io/servers/earthypunyapat-invoiceflow/api-mcp)

## Channel facts

- Endpoint: `https://invoiceflow-ten-azure.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 566 tokens (~80/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http earthypunyapat-invoiceflow 'https://invoiceflow-ten-azure.vercel.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "earthypunyapat-invoiceflow": {
      "url": "https://invoiceflow-ten-azure.vercel.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "earthypunyapat-invoiceflow": {
      "type": "http",
      "url": "https://invoiceflow-ten-azure.vercel.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.earthypunyapat-invoiceflow]
url = "https://invoiceflow-ten-azure.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "earthypunyapat-invoiceflow": {
      "type": "remote",
      "url": "https://invoiceflow-ten-azure.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add earthypunyapat-invoiceflow --url 'https://invoiceflow-ten-azure.vercel.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  earthypunyapat-invoiceflow:
    url: "https://invoiceflow-ten-azure.vercel.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "earthypunyapat-invoiceflow": {
      "Transport": "http",
      "Url": "https://invoiceflow-ten-azure.vercel.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add earthypunyapat-invoiceflow -t streamable-http -u 'https://invoiceflow-ten-azure.vercel.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "earthypunyapat-invoiceflow": {
      "type": "http",
      "url": "https://invoiceflow-ten-azure.vercel.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 68, +1)

- [security] Tool “invoiceflow_share_invoice” rewrote its description, which is the text the model reads

### 2026-11-03 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 67)

First indexed and scored.

## MCP tools (7)

### `invoiceflow_whoami` (~39 tokens)

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

### `invoiceflow_create_client` (~102 tokens)

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

Input parameters:

- `company` (string): Optional company name if it differs from name.
- `email` (string, required): Billing email. Required in practice - it is where the invoice goes if a human later sends it.
- `name` (string, required): Customer or company name. Required.
- `notes` (string): Optional internal note. Never shown to the customer.

### `invoiceflow_list_clients` (~41 tokens)

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

Input parameters:

- `query` (string): Optional search term matched against name or email.

### `invoiceflow_create_invoice` (~179 tokens)

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.

Input parameters:

- `clientId` (string, required): 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, required): 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.

### `invoiceflow_list_invoices` (~74 tokens)

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

Input parameters:

- `limit` (integer): Optional maximum number of results.
- `status` (string): Optional filter: DRAFT, SENT, PAID, OVERDUE, or CANCELLED.

### `invoiceflow_get_invoice` (~32 tokens)

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

Input parameters:

- `id` (string, required): Invoice id.

### `invoiceflow_share_invoice` (~61 tokens)

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.

Input parameters:

- `id` (string, required): Invoice id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/earthypunyapat-invoiceflow/api-mcp#diagnostics

## Score history

- 2026-11-04: 68
- 2026-11-03: 67
- 2026-11-02: 67

## Common questions

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

## Links

- Remote endpoint: https://invoiceflow-ten-azure.vercel.app/api/mcp
- Authorisation metadata: https://invoiceflow-ten-azure.vercel.app/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/EarthyPunyapat/invoiceflow
- Website: https://invoiceflow-ten-azure.vercel.app/
- Changelog RSS feed: https://verifymcp.io/servers/earthypunyapat-invoiceflow/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/earthypunyapat-invoiceflow/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/earthypunyapat-invoiceflow/api-mcp