# Invoice by Ouroboros Apps (remote · invoice-continuity2.vercel.app)

Freelance invoice line items, rates, due dates, and late terms for AI assistants

- Trust score: 90/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `invoice-continuity2.vercel.app`: 90/100 (this document), [markdown](https://verifymcp.io/servers/lahutchins91-invoice/invoice-continuity2.md), [page](https://verifymcp.io/servers/lahutchins91-invoice/invoice-continuity2)

## Channel facts

- Endpoint: `https://invoice-continuity2.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

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

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1267 tokens (~97/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 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 Invoice by Ouroboros Apps MCP server?

Invoice by Ouroboros Apps is a hosted endpoint at https://invoice-continuity2.vercel.app/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 lahutchins91-invoice 'https://invoice-continuity2.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lahutchins91-invoice": {
      "url": "https://invoice-continuity2.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lahutchins91-invoice": {
      "type": "http",
      "url": "https://invoice-continuity2.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lahutchins91-invoice]
url = "https://invoice-continuity2.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lahutchins91-invoice": {
      "type": "remote",
      "url": "https://invoice-continuity2.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lahutchins91-invoice --url 'https://invoice-continuity2.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lahutchins91-invoice:
    url: "https://invoice-continuity2.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lahutchins91-invoice": {
      "Transport": "http",
      "Url": "https://invoice-continuity2.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lahutchins91-invoice -t streamable-http -u 'https://invoice-continuity2.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lahutchins91-invoice": {
      "type": "http",
      "url": "https://invoice-continuity2.vercel.app/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-04 (score 90, +1)

- [security] Stability: 0.97 → pass

### 2026-11-02 (score 89, +1)

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

### 2026-10-30 (score 88, +1)

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

### 2026-10-28 (score 87, +1)

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

### 2026-10-26 (score 86, +1)

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

### 2026-10-24 (score 85, +1)

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

### 2026-10-22 (score 84, +1)

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

### 2026-10-20 (score 83, +1)

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

## MCP tools (13)

### `list_invoices` (~38 tokens)

list invoices

List the signed-in freelancer's invoices. Use a returned id with read_invoice. Do not guess an invoice.

Input parameters:

- `offset` (integer)

Output parameters:

- `data`

### `begin_invoice` (~74 tokens)

begin invoice

Start a draft invoice. Draft figures are not an approved commitment until seal_invoice. Currency is a three-letter code. Amounts later are minor units of that currency and are the freelancer's figures.

Input parameters:

- `clientName` (string, required)
- `currency` (string, required)
- `number` (string, required)
- `title` (required)

Output parameters:

- `data`

### `read_invoice` (~57 tokens)

read invoice

Read the invoice before answering. Quote only this record. Draft status is not an approved commitment. Proposed changes do not authorize a new line, a different rate, a discount, or a new due date.

Input parameters:

- `invoiceId` (string, required)

Output parameters:

- `data`

### `place_line` (~89 tokens)

place line

Add one line: description, quantity, rate in whole minor units, and unit hour, each, or day. After the invoice is sealed, a new line is refused until accept_invoice_change applies an add_line suggestion.

Input parameters:

- `description` (string, required)
- `invoiceId` (string, required)
- `quantity` (integer, required)
- `rateMinor` (integer, required)
- `unit` (string, required)

Output parameters:

- `data`

### `describe_line` (~62 tokens)

describe line

Correct a line description while the invoice is still a draft. After approval, a different description is refused. Use suggest_invoice_change with add_line for a different line.

Input parameters:

- `description` (string, required)
- `invoiceId` (string, required)
- `lineId` (required)

Output parameters:

- `data`

### `quote_line_rate` (~73 tokens)

quote line rate

Set the rate already chosen for one line, as a whole number of minor units in the invoice currency. After the invoice is sealed, a different rate is refused until accept_invoice_change applies a change_rate suggestion.

Input parameters:

- `invoiceId` (string, required)
- `lineId` (required)
- `rateMinor` (integer, required)

Output parameters:

- `data`

### `set_line_quantity` (~58 tokens)

set line quantity

Set the quantity on one line. After the invoice is sealed, a different quantity is refused until accept_invoice_change applies an adjust_quantity suggestion.

Input parameters:

- `invoiceId` (string, required)
- `lineId` (required)
- `quantity` (integer, required)

Output parameters:

- `data`

### `set_invoice_due` (~61 tokens)

set invoice due

Set the due date as a calendar day in YYYY-MM-DD form. After the invoice is sealed, a different date is refused until accept_invoice_change applies a move_due_date suggestion.

Input parameters:

- `dueOn` (string, required)
- `invoiceId` (string, required)

Output parameters:

- `data`

### `write_late_terms` (~124 tokens)

write late terms

Record late terms: grace days, and a basis of none, flat_fee, or percent_per_period. flat_fee uses feeMinor and a percent of 0. percent_per_period uses percent and a fee of 0. After approval, a different basis, grace, fee, or percent is refused until an accepted revise_late_terms suggestion.

Input parameters:

- `basis` (string, required)
- `feeMinor` (integer, required)
- `graceDays` (integer, required)
- `invoiceId` (string, required)
- `note` (string, required)
- `percent` (integer, required)

Output parameters:

- `data`

### `offer_discount` (~105 tokens)

offer discount

Record a discount the freelancer is putting on the invoice. kind none uses value 0. kind percent takes a whole number from 1 to 100. kind fixed takes a whole number of minor units. After the invoice is sealed, a different discount is refused until accept_invoice_change applies an apply_discount suggestion. Do not invent a discount.

Input parameters:

- `invoiceId` (string, required)
- `kind` (string, required)
- `note` (string, required)
- `value` (integer, required)

Output parameters:

- `data`

### `seal_invoice` (~62 tokens)

seal invoice

Mark the current draft as the approved invoice. Pass confirmed true only after the freelancer explicitly approves the lines, quantities, rates, due date, late terms, and any discount already on the draft.

Input parameters:

- `confirmed` (boolean, required)
- `invoiceId` (string, required)

Output parameters:

- `data`

### `suggest_invoice_change` (~223 tokens)

suggest invoice change

Record a suggested change. This does not change the invoice. kind add_line requires description, quantity, rateMinor, and unit. kind change_rate requires lineId and rateMinor. kind apply_discount requires discountKind, discountValue, and discountNote. kind move_due_date requires dueOn. kind adjust_quantity requires lineId and quantity. kind revise_late_terms requires graceDays, lateBasis, feeMinor, latePercent, and lateNote.

Input parameters:

- `description` (string)
- `discountKind` (string)
- `discountNote`
- `discountValue` (integer)
- `dueOn` (string)
- `feeMinor` (integer)
- `graceDays` (integer)
- `invoiceId` (string, required)
- `kind` (string, required)
- `lateBasis` (string)
- `lateNote`
- `latePercent` (integer)
- `lineId`
- `quantity` (integer)
- `rateMinor` (integer)
- `summary` (string, required)
- `unit` (string)

Output parameters:

- `data`

### `accept_invoice_change` (~85 tokens)

accept invoice change

Apply one suggested invoice change after the freelancer explicitly approves that change. Pass confirmed true only then. This is the path that may add a line, change a rate, apply a discount, or move the due date. Calling it is not a substitute for the freelancer's approval.

Input parameters:

- `changeId` (required)
- `confirmed` (boolean, required)
- `invoiceId` (string, required)

Output parameters:

- `data`

## Diagnostics

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

## Score history

- 2026-11-05: 90
- 2026-11-04: 90
- 2026-11-03: 89
- 2026-11-02: 89
- 2026-11-01: 88
- 2026-10-31: 88
- 2026-10-30: 88
- 2026-10-29: 87
- 2026-10-28: 87
- 2026-10-27: 86
- 2026-10-26: 86
- 2026-10-25: 85
- 2026-10-24: 85
- 2026-10-23: 84
- 2026-10-22: 84
- 2026-10-21: 83
- 2026-10-20: 83
- 2026-10-19: 82
- 2026-10-18: 82
- 2026-10-17: 81
- 2026-10-16: 81
- 2026-10-15: 81
- 2026-10-14: 80
- 2026-10-13: 80
- 2026-10-12: 79
- 2026-10-11: 79
- 2026-10-10: 78
- 2026-10-07: 77

## Common questions

### What is the Invoice by Ouroboros Apps MCP server?

Invoice by Ouroboros Apps is an MCP server listed in the public MCP registry as io.github.LAHutchins91/invoice. Freelance invoice line items, rates, due dates, and late terms for AI assistants. This page covers its hosted endpoint (https://invoice-continuity2.vercel.app/mcp).

### Is the Invoice by Ouroboros Apps MCP server safe to use?

Invoice by Ouroboros Apps scores 90 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 Invoice by Ouroboros Apps MCP server expose?

Invoice by Ouroboros Apps exposes 13 tools: list_invoices, begin_invoice, read_invoice, place_line, describe_line, and 8 more. Their descriptions and schemas cost roughly 1,111 tokens of context every time the server is loaded.

### Does the Invoice by Ouroboros Apps MCP server require authentication?

Yes. Invoice by Ouroboros Apps 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 Invoice by Ouroboros Apps MCP server still maintained?

Invoice by Ouroboros Apps is still listed as active in the MCP registry. We last reached this channel on 5 November 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://invoice-continuity2.vercel.app/mcp
- Repository: https://github.com/LAHutchins91/invoice-mcp
- Website: https://ouroborosapps.com/docs/invoice
- Changelog RSS feed: https://verifymcp.io/servers/lahutchins91-invoice/invoice-continuity2.xml
- Changelog JSON feed: https://verifymcp.io/servers/lahutchins91-invoice/invoice-continuity2.json
- HTML version of this page: https://verifymcp.io/servers/lahutchins91-invoice/invoice-continuity2