Skip to content

FoxyInvoice MCP server

io.github.seolith-llc/foxyinvoiceseolith-llcstreamable-httpv1.28.1Scanned

Invoicing for AI assistants: clients, quotes, invoices with computed tax, email send, card payments.

9 tools: 2 do something that can't be undone, 2 change things and 5 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do 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 FoxyInvoice MCP server can do

The FoxyInvoice MCP server is published by the GitHub account seolith-llc. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_invoice and send_document) and create or change data (2 tools: create_client and create_invoice), but cannot delete data. 5 tools only read.

2 tools read private data (list_clients and list_documents); 1 tool brings in text other people can write (list_clients); 3 tools can send data out of your system (create_client, send_invoice and send_document). 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 16, 2026, version 1.28.1.

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.

9 tools

Can't be undone 2Claude Code: ask
  • send_documentEmail a Draft document (agreement/NDA/terms) to its client for electronic acceptance — the client reviews it, types their name, and the acceptance is archived with a certificate.Can send data outNo findings

    Why it is in this group

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

    What it can reach

    • outboundThe name "send_document" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Email a Draft document (agreement/NDA/terms) to its client for electronic acceptance — the client reviews it, types their name, and the acceptance is archived with a certificate. CONFIRM with the user before calling — this emails a real person.
  • send_invoiceEmail a Draft/Sent/Overdue invoice to its client (requires the client to have an email; counts against the monthly send quota).Can 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

    • outboundThe name "send_invoice" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Email a Draft/Sent/Overdue invoice to its client (requires the client to have an email; counts against the monthly send quota). CONFIRM with the user before calling — this emails a real person.
Changes things 2Claude Code: ask
  • create_clientCreate a client so invoices can be billed to them.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
    Create a client so invoices can be billed to them. Returns the new client with its id. Name is required; email is needed later for send_invoice.
  • create_invoiceCreate a DRAFT invoice for a client; the server assigns the number (INV-YYYY-NNNN), computes taxes from the client's jurisdiction and rounds per invoice rules — never state amounts…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
    Create a DRAFT invoice for a client; the server assigns the number (INV-YYYY-NNNN), computes taxes from the client's jurisdiction and rounds per invoice rules — never state amounts yourself. Lines need description, qty and unitPrice (decimal). Due date defaults to 14 days from today. Pass a stable requestId when retrying: the same requestId returns the same invoice instead of creating a duplicate. Use send_invoice to email it — do NOT send without the user's confirmation.
Only reads 5Show 5 read-only tools
  • get_invoiceFetch one invoice with all lines and computed totals (server-side tax math included).No findings

    Why it is in this group

    • The name "get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one invoice with all lines and computed totals (server-side tax math included).
  • list_clientsSearch the workspace's clients by name or email.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 "search" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "search" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Search the workspace's clients by name or email. Returns id, name, email, billing address. Use this to find a clientId before creating an invoice.
  • list_documentsList the workspace's client documents (agreements, NDAs, terms) with their acceptance status.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "list_documents" says "list" and "document": it reads documents.
    • private-dataThe description's first sentence says "list" and "document": it reads documents.
    Description, as the server wrote it
    List the workspace's client documents (agreements, NDAs, terms) with their acceptance status. Filter by clientId.
  • list_invoicesList invoices, newest first.No findings

    Why it is in this group

    • The name "list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices, newest first. Filter by status (Draft, Sent, Paid, Overdue, Void) and/or clientId.
  • list_productsList the workspace's catalog products (id, sku, name, unit price).No findings

    Why it is in this group

    • The name "list_products" says "list": a word for reading.
    Description, as the server wrote it
    List the workspace's catalog products (id, sku, name, unit price). A product's id can be attached to an invoice line; otherwise lines stand alone.

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.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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__foxyinvoice__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 21, 2026, 19:21 UTC, unchanged since Nov 21, 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
4
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 4 tools that change things (2 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://foxyinvoice.com/api/v1/mcp: tools/list returned 9 tools to an anonymous client, including send_invoice (irreversible), send_document (irreversible), create_client (write), create_invoice (write)

    What this check looks for

Posture changes

  1. Nov 21, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed

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.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 4 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 4
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed

Install

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

claude mcp add --transport http foxyinvoice https://foxyinvoice.com/api/v1/mcp
claude mcp add --transport http foxyinvoice https://foxyinvoice.com/api/v1/mcp

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__foxyinvoice__list_clients",
      "mcp__foxyinvoice__list_products",
      "mcp__foxyinvoice__list_invoices",
      "mcp__foxyinvoice__get_invoice",
      "mcp__foxyinvoice__list_documents"
    ],
    "ask": [
      "mcp__foxyinvoice__create_client",
      "mcp__foxyinvoice__create_invoice",
      "mcp__foxyinvoice__send_invoice",
      "mcp__foxyinvoice__send_document"
    ],
    "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 foxyinvoice. Review it before you use it.

Capability tags behind 5 rules
  • mcp__foxyinvoice__list_clients private-data, untrusted-input
  • mcp__foxyinvoice__create_client outbound
  • mcp__foxyinvoice__send_invoice outbound
  • mcp__foxyinvoice__list_documents private-data
  • mcp__foxyinvoice__send_document 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.seolith-llc/foxyinvoice/verify?hash=c43f80fa09e20dc5b3b64b3660783bc6ab6b809ff2e28526b39dc74232d3a2ca" | jq -e '.changed == false'

Pinned hash c43f80fa09e2, from Nov 16, 2026, 21: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.seolith-llc/foxyinvoice/changes.xml

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

Badge

Anlyon Radar badge for io.github.seolith-llc/foxyinvoice
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.seolith-llc/foxyinvoice.svg)](https://radar.anlyon.com/servers/io.github.seolith-llc/foxyinvoice)

Source: MCP Registry · repository. Synced Nov 16, 2026, 21:18 UTC.

FoxyInvoice MCP server: questions and answers

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

Is the FoxyInvoice MCP server safe?

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

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

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

Yes. 2 tools can send, pay, publish or merge: send_invoice and send_document.

What tools does the FoxyInvoice MCP server have?

9 tools: 2 irreversible, 2 write, 5 read. send_invoice, send_document, create_client, create_invoice, list_clients, list_products, list_invoices, get_invoice and 1 more.

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

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

Does the FoxyInvoice 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, send_invoice and send_document.

Has the FoxyInvoice MCP server changed its tools?

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