# InvoiceBloom (remote · invoicebloom.io)

Create, send and track invoices for freelancers and small businesses.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `invoicebloom.io`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theasteve-invoicebloom/invoicebloom.md), [page](https://verifymcp.io/servers/theasteve-invoicebloom/invoicebloom)

## Channel facts

- Endpoint: `https://invoicebloom.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1332 tokens (~121/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 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 InvoiceBloom MCP server?

InvoiceBloom is a hosted endpoint at https://invoicebloom.io/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 theasteve-invoicebloom 'https://invoicebloom.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theasteve-invoicebloom": {
      "url": "https://invoicebloom.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theasteve-invoicebloom": {
      "type": "http",
      "url": "https://invoicebloom.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theasteve-invoicebloom]
url = "https://invoicebloom.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theasteve-invoicebloom": {
      "type": "remote",
      "url": "https://invoicebloom.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theasteve-invoicebloom --url 'https://invoicebloom.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theasteve-invoicebloom:
    url: "https://invoicebloom.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theasteve-invoicebloom": {
      "Transport": "http",
      "Url": "https://invoicebloom.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theasteve-invoicebloom -t streamable-http -u 'https://invoicebloom.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theasteve-invoicebloom": {
      "type": "http",
      "url": "https://invoicebloom.io/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-10-03 (score 79, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-02 (score 79, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-01 (score 79, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-30 (score 78, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-29 (score 78, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-28 (score 77, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 77, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-26 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (11)

### `get_account` (~59 tokens)

Returns the signed-in user's profile: business name, address, saved payment instructions, whether their email is confirmed (required before sending invoices), whether they can take card payments, and client/invoice counts. Call this first to know who you are acting for.

### `list_clients` (~64 tokens)

Lists the user's clients (people or companies they invoice), optionally filtered by a search term matched against name, email and company. Use it to find a client_id before creating an invoice.

Input parameters:

- `query` (string): Optional case-insensitive search across name, email and company name.

### `create_client` (~112 tokens)

Creates a new client to invoice. Name and email are required; the email is where invoices are sent. Check list_clients first so you do not create duplicates.

Input parameters:

- `address` (string): Postal address, printed on invoices.
- `company_name` (string)
- `email` (string, required): Email address invoices will be sent to.
- `name` (string, required): Contact name, up to 100 characters.
- `notes` (string): Private notes, never shown to the client.
- `phone` (string)

### `update_client` (~80 tokens)

Updates an existing client's details. Only the fields you pass are changed.

Input parameters:

- `address` (string)
- `client_id` (integer, required)
- `company_name` (string)
- `email` (string)
- `name` (string)
- `notes` (string)
- `phone` (string)
- `status` (string)

### `list_invoices` (~107 tokens)

Lists the user's invoices, newest first, without line items. Filter by status (draft, sent, paid), by client, or overdue_only for unpaid invoices past their due date (there is no 'overdue' status; use overdue_only). Use get_invoice for full detail.

Input parameters:

- `client_id` (integer)
- `limit` (integer): Defaults to 25.
- `overdue_only` (boolean): Only unpaid invoices whose due date has passed.
- `status` (string)

### `get_invoice` (~50 tokens)

Returns one invoice with its line items, totals, status, the client it is for, a public_url the client can open, and a payment link if one exists.

Input parameters:

- `invoice_id` (integer, required)

### `create_invoice` (~293 tokens)

Creates a draft invoice with line items for an existing client. Identify the client by client_id or client_email (must already exist; use create_client otherwise). Totals are computed server-side: subtotal + tax% + late_fee. Nothing is emailed until you call send_invoice. Returns the invoice, including its invoice_number and public_url.

Input parameters:

- `business_address` (string): Override the sender address printed on this invoice.
- `business_name` (string): Override the sender name printed on this invoice.
- `client_email` (string): Alternative to client_id: email of an existing client.
- `client_id` (integer): ID from list_clients.
- `date` (string): Invoice date, YYYY-MM-DD. Defaults to today.
- `due_date` (string): Due date, YYYY-MM-DD. Defaults to 30 days from today.
- `late_fee` (number): Flat late fee amount added to the total. Omit for none.
- `line_items` (array, required): At least one line item.
- `payment_instructions` (string): How to pay (bank details etc.). Defaults to the user's saved instructions.
- `tax` (number): Tax as a percentage of the subtotal, e.g. 8.5. Omit for no tax.
- `terms` (string): Payment terms text, e.g. 'Net 30'.
- `theme` (string): Visual template. Defaults to 'minimal'.

### `update_invoice` (~274 tokens)

Updates an invoice. Only fields you pass change. If you pass line_items, they REPLACE the existing line items entirely, so include every item that should remain. Works on draft and sent invoices; re-send with send_invoice if the client needs the new version.

Input parameters:

- `business_address` (string): Override the sender address printed on this invoice.
- `business_name` (string): Override the sender name printed on this invoice.
- `client_email` (string)
- `client_id` (integer)
- `date` (string): Invoice date, YYYY-MM-DD. Defaults to today.
- `due_date` (string): Due date, YYYY-MM-DD. Defaults to 30 days from today.
- `invoice_id` (integer, required)
- `late_fee` (number): Flat late fee amount added to the total. Omit for none.
- `line_items` (array): Full replacement list of line items.
- `payment_instructions` (string): How to pay (bank details etc.). Defaults to the user's saved instructions.
- `tax` (number): Tax as a percentage of the subtotal, e.g. 8.5. Omit for no tax.
- `terms` (string): Payment terms text, e.g. 'Net 30'.
- `theme` (string): Visual template. Defaults to 'minimal'.

### `send_invoice` (~76 tokens)

Emails the invoice (with a PDF attached) to the client's email address and marks it as sent. This contacts a real person: confirm with the user before calling. Requires at least one line item and a confirmed user email. If the user takes card payments, a Stripe payment link is added first.

Input parameters:

- `invoice_id` (integer, required)

### `mark_invoice_paid` (~47 tokens)

Marks an invoice as paid, for payments received outside InvoiceBloom (bank transfer, cash, cheque). Card payments through the payment link are recorded automatically.

Input parameters:

- `invoice_id` (integer, required)

### `delete_invoice` (~47 tokens)

Permanently deletes an invoice and its line items. Cannot be undone. Confirm with the user before calling; prefer leaving paid invoices in place for their records.

Input parameters:

- `invoice_id` (integer, required)

## Diagnostics

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

## Score history

- 2026-10-03: 79
- 2026-10-02: 79
- 2026-10-01: 79
- 2026-09-30: 78
- 2026-09-29: 78
- 2026-09-28: 77
- 2026-09-27: 77
- 2026-09-26: 76
- 2026-09-25: 76

## Common questions

### What is the InvoiceBloom MCP server?

InvoiceBloom is an MCP server listed in the public MCP registry as io.github.theasteve/invoicebloom. Create, send and track invoices for freelancers and small businesses. This page covers its hosted endpoint (https://invoicebloom.io/mcp).

### Is the InvoiceBloom MCP server safe to use?

InvoiceBloom scores 79 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 InvoiceBloom MCP server expose?

InvoiceBloom exposes 11 tools: get_account, list_clients, create_client, update_client, list_invoices, and 6 more. Their descriptions and schemas cost roughly 1,209 tokens of context every time the server is loaded.

### Does the InvoiceBloom MCP server require authentication?

Yes. InvoiceBloom asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the InvoiceBloom MCP server still maintained?

InvoiceBloom is still listed as active in the MCP registry. We last reached this channel on 3 October 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://invoicebloom.io/mcp
- Authorisation metadata: https://invoicebloom.io/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/theasteve/invoicebloom-mcp
- Website: https://invoicebloom.io/developers
- Changelog RSS feed: https://verifymcp.io/servers/theasteve-invoicebloom/invoicebloom.xml
- Changelog JSON feed: https://verifymcp.io/servers/theasteve-invoicebloom/invoicebloom.json
- HTML version of this page: https://verifymcp.io/servers/theasteve-invoicebloom/invoicebloom