Skip to content

InvoiceBloom MCP server

io.github.theasteve/invoicebloomtheastevestreamable-httpv1.0.0Scanned

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

11 tools: 1 can delete or cancel things, 1 do something that can't be undone, 5 change things and 4 only read.

Tools: 1 delete, 1 irreversible, 5 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 4
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 InvoiceBloom MCP server can do

The InvoiceBloom MCP server is published by the GitHub account theasteve. It has 11 tools. It can delete or cancel things (1 tool: delete_invoice), do things that cannot be undone, such as sending, paying or publishing (send_invoice) and create or change data (5 tools: create_client, update_client, create_invoice, update_invoice and 1 more). 4 tools only read.

2 tools read private data (get_account and list_clients); 4 tools bring in text other people can write (get_account, list_clients, get_invoice and 1 more); 3 tools can send data out of your system (create_client, update_client and send_invoice). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way 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.

Last scanned Nov 20, 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.

11 tools

Deletes or cancels 1Claude Code: deny
  • delete_invoicePermanently deletes an invoice and its line items.No findings

    Why it is in this group

    • The name "delete_invoice" says "delete": a word for removing or ending something.
    • The description says "Permanently deletes".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
Can't be undone 1Claude Code: ask
  • send_invoiceEmails the invoice (with a PDF attached) to the client's email address and marks it as sent.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_invoice" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_invoice" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
Changes things 5Claude Code: ask
  • create_clientCreates a new client to invoice.Can send data outNo findings

    Why it is in this group

    • The name "create_client" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • create_invoiceCreates a draft invoice with line items for an existing client.No findings

    Why it is in this group

    • The name "create_invoice" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
  • mark_invoice_paidMarks an invoice as paid, for payments received outside InvoiceBloom (bank transfer, cash, cheque).No findings

    Why it is in this group

    • The name "mark_invoice_paid" says "mark": a word for a change.
    Description, as the server wrote it
    Marks an invoice as paid, for payments received outside InvoiceBloom (bank transfer, cash, cheque). Card payments through the payment link are recorded automatically.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • update_clientUpdates an existing client's details.Can send data outNo findings

    Why it is in this group

    • The name "update_client" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Updates an existing client's details. Only the fields you pass are changed.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • update_invoiceUpdates an invoice.No findings

    Why it is in this group

    • The name "update_invoice" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
Only reads 4Show 4 read-only tools
  • get_accountReturns 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "return" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_invoiceReturns 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_invoice" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • list_clientsLists the user's clients (people or companies they invoice), optionally filtered by a search term matched against name, email and company.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_clients" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • list_invoicesLists the user's invoices, newest first, without line items.No findings

    Why it is in this group

    • The name "list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: true

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.

24 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 private-data tools breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__invoicebloom__get_account",
      "mcp__invoicebloom__list_clients"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 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
7
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
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 destructive, 1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://invoicebloom.io/mcp: tools/list returned 11 tools to an anonymous client, including delete_invoice (destructive), send_invoice (irreversible), create_client (write), update_client (write), create_invoice (write) and 2 more

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http invoicebloom https://invoicebloom.io/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http invoicebloom https://invoicebloom.io/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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__invoicebloom__get_account",
      "mcp__invoicebloom__list_clients",
      "mcp__invoicebloom__list_invoices",
      "mcp__invoicebloom__get_invoice"
    ],
    "ask": [
      "mcp__invoicebloom__create_client",
      "mcp__invoicebloom__update_client",
      "mcp__invoicebloom__create_invoice",
      "mcp__invoicebloom__update_invoice",
      "mcp__invoicebloom__send_invoice",
      "mcp__invoicebloom__mark_invoice_paid"
    ],
    "deny": [
      "mcp__invoicebloom__delete_invoice"
    ]
  }
}

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 invoicebloom. Review it before you use it.

Capability tags behind 6 rules
  • mcp__invoicebloom__get_account private-data, untrusted-input
  • mcp__invoicebloom__list_clients private-data, untrusted-input
  • mcp__invoicebloom__create_client outbound
  • mcp__invoicebloom__update_client outbound
  • mcp__invoicebloom__get_invoice untrusted-input
  • mcp__invoicebloom__send_invoice untrusted-input, outbound

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.theasteve/invoicebloom/verify?hash=f089a3727e16f37995429eb7359f2ceefd77d14e0f2f0382eccfb6fbd617ed2d" | jq -e '.changed == false'

Pinned hash f089a3727e16, from Nov 20, 2026, 15: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.theasteve/invoicebloom/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theasteve/invoicebloom
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theasteve/invoicebloom.svg)](https://radar.anlyon.com/servers/io.github.theasteve/invoicebloom)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.

InvoiceBloom MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the InvoiceBloom MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 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 InvoiceBloom MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_invoice.

Can the InvoiceBloom MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send_invoice.

What tools does the InvoiceBloom MCP server have?

11 tools: 1 destructive, 1 irreversible, 5 write, 4 read. delete_invoice, send_invoice, create_client, update_client, create_invoice, update_invoice, mark_invoice_paid, get_account and 3 more.

Does the InvoiceBloom MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the InvoiceBloom MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_client, update_client and send_invoice.

Has the InvoiceBloom MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.