# FoxyInvoice (remote · foxyinvoice.com)

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

- Trust score: 72/100 (medium)
- Change this week: +36
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `foxyinvoice.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/seolith-llc-foxyinvoice/api-v1-mcp.md), [page](https://verifymcp.io/servers/seolith-llc-foxyinvoice/api-v1-mcp)

## Channel facts

- Endpoint: `https://foxyinvoice.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.28.1`

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

- **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**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 703 tokens (~78/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 15% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_invoice" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the FoxyInvoice MCP server?

FoxyInvoice is a hosted endpoint at https://foxyinvoice.com/api/v1/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 seolith-llc-foxyinvoice 'https://foxyinvoice.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "seolith-llc-foxyinvoice": {
      "url": "https://foxyinvoice.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "seolith-llc-foxyinvoice": {
      "type": "http",
      "url": "https://foxyinvoice.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.seolith-llc-foxyinvoice]
url = "https://foxyinvoice.com/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seolith-llc-foxyinvoice": {
      "type": "remote",
      "url": "https://foxyinvoice.com/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add seolith-llc-foxyinvoice --url 'https://foxyinvoice.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  seolith-llc-foxyinvoice:
    url: "https://foxyinvoice.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "seolith-llc-foxyinvoice": {
      "Transport": "http",
      "Url": "https://foxyinvoice.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add seolith-llc-foxyinvoice -t streamable-http -u 'https://foxyinvoice.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "seolith-llc-foxyinvoice": {
      "type": "http",
      "url": "https://foxyinvoice.com/api/v1/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-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 70, +34)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: 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.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 15
- [functional] First check of Schema quality: good

### 2026-11-13 (score 36)

First indexed and scored.

## MCP tools (9)

### `list_clients` (~70 tokens)

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.

Input parameters:

- `page` (integer)
- `pageSize` (integer)
- `search` (string): Case-insensitive match on name or email

### `create_client` (~85 tokens)

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.

Input parameters:

- `billingAddress` (string)
- `email` (string)
- `name` (string, required)
- `phone` (string)
- `taxExempt` (boolean)
- `taxId` (string)

### `list_products` (~56 tokens)

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.

Input parameters:

- `page` (integer)
- `pageSize` (integer)

### `list_invoices` (~65 tokens)

List invoices, newest first. Filter by status (Draft, Sent, Paid, Overdue, Void) and/or clientId.

Input parameters:

- `clientId` (string)
- `page` (integer)
- `pageSize` (integer)
- `status` (string)

### `get_invoice` (~31 tokens)

Fetch one invoice with all lines and computed totals (server-side tax math included).

Input parameters:

- `id` (string, required)

### `create_invoice` (~175 tokens)

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.

Input parameters:

- `clientId` (string, required)
- `dueDate` (string): Defaults to today + dueInDays
- `dueInDays` (integer)
- `issueDate` (string): Defaults to today
- `lines` (array, required)
- `notes` (string)
- `requestId` (string): Idempotency key

### `send_invoice` (~57 tokens)

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.

Input parameters:

- `id` (string, required)

### `list_documents` (~42 tokens)

List the workspace's client documents (agreements, NDAs, terms)              with their acceptance status. Filter by clientId.

Input parameters:

- `clientId` (string)

### `send_document` (~68 tokens)

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.

Input parameters:

- `id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70
- 2026-11-15: 36
- 2026-11-14: 36
- 2026-11-13: 36

## Common questions

### What is the FoxyInvoice MCP server?

FoxyInvoice is an MCP server listed in the public MCP registry as io.github.seolith-llc/foxyinvoice. Invoicing for AI assistants: clients, quotes, invoices with computed tax, email send, card payments. This page covers its hosted endpoint (https://foxyinvoice.com/api/v1/mcp).

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

FoxyInvoice scores 72 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 FoxyInvoice MCP server expose?

FoxyInvoice exposes 9 tools: list_clients, create_client, list_products, list_invoices, get_invoice, and 4 more. Their descriptions and schemas cost roughly 649 tokens of context every time the server is loaded.

### Does the FoxyInvoice MCP server require authentication?

Yes. FoxyInvoice 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 FoxyInvoice MCP server still maintained?

FoxyInvoice is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the FoxyInvoice MCP server?

VerifyMCP ran 13 checks on FoxyInvoice, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://foxyinvoice.com/api/v1/mcp
- Repository: https://github.com/seolith-llc/seolith-tax-manager
- Website: https://foxyinvoice.com/
- Changelog RSS feed: https://verifymcp.io/servers/seolith-llc-foxyinvoice/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/seolith-llc-foxyinvoice/api-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/seolith-llc-foxyinvoice/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/seolith-llc-foxyinvoice/api-v1-mcp
