InvoiceBloom
REMOTE · INVOICEBLOOM.IO · SCANNED OCT 3
Create, send and track invoices for freelancers and small businesses.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 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
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.
remote · invoicebloom.io
claude mcp add --transport http theasteve-invoicebloom 'https://invoicebloom.io/mcp'
{
"mcpServers": {
"theasteve-invoicebloom": {
"url": "https://invoicebloom.io/mcp"
}
}
} {
"servers": {
"theasteve-invoicebloom": {
"type": "http",
"url": "https://invoicebloom.io/mcp"
}
}
} [mcp_servers.theasteve-invoicebloom] url = "https://invoicebloom.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theasteve-invoicebloom": {
"type": "remote",
"url": "https://invoicebloom.io/mcp",
"enabled": true
}
}
} openclaw mcp add theasteve-invoicebloom --url 'https://invoicebloom.io/mcp' --transport streamable-http
mcp_servers:
theasteve-invoicebloom:
url: "https://invoicebloom.io/mcp" {
"McpServers": {
"theasteve-invoicebloom": {
"Transport": "http",
"Url": "https://invoicebloom.io/mcp"
}
}
} assistant mcp add theasteve-invoicebloom -t streamable-http -u 'https://invoicebloom.io/mcp'
{
"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.
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.
- 3 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 2 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 1 Oct 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 29 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Sept 26 0
- 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 functional
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 3 Oct 2026 · Probed https://invoicebloom.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=invoicebloom.io | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6fcaf8b14fd1b33eb57042d398ffb27cee2 |
| SANs: invoicebloom.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of invoicebloom.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| invoicebloom.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://invoicebloom.io/mcp | Verified | 200 | |
| http (plaintext) | http://invoicebloom.io/mcp | HTTPS enforced | 301 | https://invoicebloom.io/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 →
create_client ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Postal address, printed on invoices. |
| company_name | string | – | – |
| string | yes | Email address invoices will be sent to. | |
| name | string | yes | Contact name, up to 100 characters. |
| notes | string | – | Private notes, never shown to the client. |
| phone | string | – | – |
No output schema declared.
No examples provided.
create_invoice ~293
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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'. |
No output schema declared.
No examples provided.
delete_invoice ~47
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | – |
No output schema declared.
No examples provided.
get_account ~59
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_invoice ~50
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | – |
No output schema declared.
No examples provided.
list_clients ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional case-insensitive search across name, email and company name. |
No output schema declared.
No examples provided.
list_invoices ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | integer | – | – |
| limit | integer | – | Defaults to 25. |
| overdue_only | boolean | – | Only unpaid invoices whose due date has passed. |
| status | string | – | – |
No output schema declared.
No examples provided.
mark_invoice_paid ~47
Marks an invoice as paid, for payments received outside InvoiceBloom (bank transfer, cash, cheque). Card payments through the payment link are recorded automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | – |
No output schema declared.
No examples provided.
send_invoice ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | integer | yes | – |
No output schema declared.
No examples provided.
update_client ~80
Updates an existing client's details. Only the fields you pass are changed.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| client_id | integer | yes | – |
| company_name | string | – | – |
| string | – | – | |
| name | string | – | – |
| notes | string | – | – |
| phone | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
update_invoice ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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'. |
No output schema declared.
No examples provided.
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.