# Invoiced MCP by usefulapi (remote · invoiced.usefulapi.io)

Read Invoiced customers, invoices, payments, subscriptions; create customers, draft invoices, notes.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `invoiced.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-invoiced/invoiced.md), [page](https://verifymcp.io/servers/io-usefulapi-invoiced/invoiced)

## Channel facts

- Endpoint: `https://invoiced.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## 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-10-17.

- **Endpoint Security**: 78/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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3966 tokens (~146/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params.
  - 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**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 28 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 Invoiced MCP by usefulapi server?

Invoiced MCP by usefulapi is a hosted endpoint at https://invoiced.usefulapi.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-invoiced 'https://invoiced.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-invoiced": {
      "url": "https://invoiced.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-invoiced": {
      "type": "http",
      "url": "https://invoiced.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-invoiced]
url = "https://invoiced.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-invoiced": {
      "type": "remote",
      "url": "https://invoiced.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-invoiced --url 'https://invoiced.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-invoiced:
    url: "https://invoiced.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-invoiced": {
      "Transport": "http",
      "Url": "https://invoiced.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-invoiced -t streamable-http -u 'https://invoiced.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-invoiced": {
      "type": "http",
      "url": "https://invoiced.usefulapi.io/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-10-17 (score 64, +1)

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

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (27)

### `invoiced_list_customers` (~247 tokens)

List customers

List customers (accounts receivable debtors): name, number, email, payment terms, currency, autopay and chasing settings, owner. Filter by open balance, saved payment method, update time or any exact-match column. GET /customers.

Input parameters:

- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `metadata` (object): Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
- `open_balance` (boolean): true = only customers with an open balance; false = only those without.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `payment_source` (boolean): true = only customers with a saved payment method.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_customer` (~66 tokens)

Get customer

One customer by id: contact details, address, terms, currency, autopay, chasing cadence, credit hold/limit, parent customer, metadata. GET /customers/{id}.

Input parameters:

- `customer_id` (integer, required): Invoiced customer id (numeric; not the customer number).

### `invoiced_get_customer_balance` (~74 tokens)

Get customer balance

A customer's current balance: total outstanding, past due, and available credit, in the customer's currency (or `currency`). GET /customers/{id}/balance.

Input parameters:

- `currency` (string): 3-letter currency code (default: the customer's currency).
- `customer_id` (integer, required): Invoiced customer id.

### `invoiced_list_contacts` (~125 tokens)

List customer contacts

List the contacts of one customer: name, title, email, phone, whether primary (copied on communications) and SMS-enabled. GET /customers/{id}/contacts.

Input parameters:

- `customer_id` (integer, required): Invoiced customer id.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".

### `invoiced_list_invoices` (~292 tokens)

List invoices

List invoices with number, customer, status (draft, not_sent, sent, viewed, past_due, pending, paid, voided), dates, totals, balance and line items. Filter by customer, paid flag, invoice date range, update time or any exact-match column. GET /invoices.

Input parameters:

- `customer_id` (integer): Only this customer's invoices.
- `end_date` (string): Invoices dated on or before this date (a bare date includes the whole day).
- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `metadata` (object): Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `paid` (boolean): true = only paid invoices; false = only unpaid.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `start_date` (string): Invoices dated on or after this date or date-time.
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_invoice` (~99 tokens)

Get invoice

One invoice by id: status, dates, payment terms, totals, balance, line items, discounts, taxes, ship-to, payment and PDF links. `expand` replaces ids with full objects (e.g. customer). GET /invoices/{id}.

Input parameters:

- `expand` (array): Relations to expand into full objects.
- `invoice_id` (integer, required): Invoiced invoice id (numeric; find it with invoiced_list_invoices).

### `invoiced_get_invoice_payment_plan` (~67 tokens)

Get invoice payment plan

The payment plan (installments with dates, amounts and balances, and approval status) attached to an invoice. Errors with 404 when the invoice has none. GET /invoices/{id}/payment_plan.

Input parameters:

- `invoice_id` (integer, required): Invoiced invoice id.

### `invoiced_list_payments` (~228 tokens)

List payments

List payments received: customer, date, amount, unapplied balance, method (check, wire, ACH, card, ...), reference, whether matched or voided. Read only. GET /payments.

Input parameters:

- `customer_id` (integer): Only this customer's payments.
- `end_date` (string): Payments dated on or before this date (a bare date includes the whole day).
- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `start_date` (string): Payments dated on or after this date or date-time.
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_payment` (~55 tokens)

Get payment

One payment by id, including which invoices and credit notes it was applied to (`applied_to`). GET /payments/{id}?include=applied_to.

Input parameters:

- `payment_id` (integer, required): Invoiced payment id.

### `invoiced_list_credit_notes` (~247 tokens)

List credit notes

List credit notes: customer, status (draft, open, paid, closed, voided), totals, remaining balance, line items. GET /credit_notes.

Input parameters:

- `customer_id` (integer): Only this customer's credit notes.
- `end_date` (string): Credit notes dated on or before this date (a bare date includes the whole day).
- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `metadata` (object): Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `start_date` (string): Credit notes dated on or after this date or date-time.
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_credit_note` (~46 tokens)

Get credit note

One credit note by id with line items, totals and balance. GET /credit_notes/{id}.

Input parameters:

- `credit_note_id` (integer, required): Invoiced credit note id.

### `invoiced_list_estimates` (~253 tokens)

List estimates

List estimates (quotes): customer, status (draft, not_sent, sent, approved, invoiced, declined, voided), expiration date, deposit, totals, resulting invoice. GET /estimates.

Input parameters:

- `customer_id` (integer): Only this customer's estimates.
- `end_date` (string): Estimates dated on or before this date (a bare date includes the whole day).
- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `metadata` (object): Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `start_date` (string): Estimates dated on or after this date or date-time.
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_estimate` (~46 tokens)

Get estimate

One estimate by id with line items, totals, deposit and approval state. GET /estimates/{id}.

Input parameters:

- `estimate_id` (integer, required): Invoiced estimate id.

### `invoiced_list_items` (~173 tokens)

List catalog items

List the item catalog (products and services): id, name, currency, unit cost, type, taxable. Use item ids as `catalog_item` when creating a draft invoice. GET /items.

Input parameters:

- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_item` (~47 tokens)

Get catalog item

One catalog item by its id (a string such as "delivery"). GET /items/{id}.

Input parameters:

- `item_id` (string, required): Catalog item id (from invoiced_list_items).

### `invoiced_list_tax_rates` (~158 tokens)

List tax rates

List tax rates: id, name, value, whether a percentage, whether inclusive, currency. GET /tax_rates.

Input parameters:

- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_list_plans` (~158 tokens)

List subscription plans

List subscription plans: id, name, currency, amount, pricing mode, billing interval, tiers. GET /plans.

Input parameters:

- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_plan` (~43 tokens)

Get subscription plan

One subscription plan by its id (a string). GET /plans/{id}.

Input parameters:

- `plan_id` (string, required): Plan id (from invoiced_list_plans).

### `invoiced_list_subscriptions` (~246 tokens)

List subscriptions

List recurring subscriptions: customer, plan, quantity, billing period, status (not_started, active, past_due, finished, canceled), recurring total and MRR, contract renewal. GET /subscriptions.

Input parameters:

- `canceled` (boolean): true = only canceled subscriptions; false = only not canceled.
- `customer_id` (integer): Only this customer's subscriptions.
- `filter` (object): Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
- `finished` (boolean): true = only finished subscriptions; false = only unfinished.
- `metadata` (object): Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".
- `updated_after` (string): Only records updated after this date or date-time.

### `invoiced_get_subscription` (~51 tokens)

Get subscription

One subscription by id with plan, add-ons, billing period, contract terms, recurring total and MRR. GET /subscriptions/{id}.

Input parameters:

- `subscription_id` (integer, required): Invoiced subscription id.

### `invoiced_list_notes` (~125 tokens)

List notes

List collection notes, newest first, for one customer or one invoice (give exactly one), or all notes when neither is given. GET /customers/{id}/notes, /invoices/{id}/notes or /notes.

Input parameters:

- `customer_id` (integer): Only this customer's notes.
- `invoice_id` (integer): Only this invoice's notes.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).

### `invoiced_list_tasks` (~138 tokens)

List tasks

List collection tasks (call, letter, email, review): name, action, customer, assignee, due date, whether complete. GET /tasks.

Input parameters:

- `complete` (boolean): true = only completed tasks; false = only open tasks.
- `customer_id` (integer): Only this customer's tasks.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort, "<column> asc|desc", e.g. "date desc".

### `invoiced_list_events` (~143 tokens)

List events

The activity feed, newest first: event type (such as invoice.paid, customer.created), time, the object it concerns and who did it. Optionally only the events of one object. GET /events.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `related_object_id` (integer): Id of the object (needs related_object_type).
- `related_object_type` (string): Object type such as customer or invoice; with related_object_id: only events about this object.

### `invoiced_create_customer` (~214 tokens)

Create customer

WRITE: create a customer in Invoiced. Nothing is sent to anyone and no money moves. Name is required; Invoiced generates the customer number unless given. POST /customers.

Input parameters:

- `address1` (string)
- `address2` (string)
- `attention_to` (string)
- `city` (string)
- `country` (string)
- `currency` (string)
- `email` (string)
- `metadata` (object): Metadata key/values (max 10 keys, names up to 40 characters, values up to 255).
- `name` (string, required): Customer name.
- `notes` (string): Private notes.
- `number` (string): Customer number (default: generated).
- `payment_terms` (string): e.g. "NET 30".
- `phone` (string)
- `postal_code` (string)
- `state` (string)
- `tax_id` (string)
- `type` (string): Default company.

### `invoiced_create_draft_invoice` (~231 tokens)

Create draft invoice

WRITE: create a DRAFT invoice for a customer. It is always created as a draft: it is not issued, not emailed, not charged and cannot trigger AutoPay until a person finalizes it in Invoiced. At least one line item is required. POST /invoices with draft=true.

Input parameters:

- `currency` (string)
- `customer_id` (integer, required): Invoiced customer id (invoiced_list_customers).
- `date` (string): Invoice date (default now).
- `due_date` (string): Due date (default: computed from the payment terms).
- `items` (array, required): Line items.
- `metadata` (object): Metadata key/values (max 10 keys, names up to 40 characters, values up to 255).
- `name` (string): Document title (default "Invoice").
- `notes` (string): Notes printed on the invoice.
- `number` (string): Invoice number (default: next in sequence).
- `payment_terms` (string): e.g. "NET 30".
- `purchase_order` (string)

### `invoiced_add_note` (~77 tokens)

Add note

WRITE: add an internal note to a customer or an invoice (give exactly one). Notes are internal; nothing is sent. POST /notes.

Input parameters:

- `customer_id` (integer): Customer to attach the note to.
- `invoice_id` (integer): Invoice to attach the note to.
- `notes` (string, required): The note text.

### `invoiced_create_task` (~111 tokens)

Create task

WRITE: create a collection task for a customer (a reminder to call, write, email or review). Nothing is sent to the customer. POST /tasks.

Input parameters:

- `action` (string, required): Kind of task.
- `customer_id` (integer, required): Customer the task is about.
- `due_date` (string): When it is due.
- `name` (string, required): Task name, e.g. "Call about overdue invoice".
- `user_id` (integer): Invoiced user to assign it to.

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the Invoiced MCP by usefulapi server?

Invoiced MCP by usefulapi is listed in the public MCP registry as io.usefulapi/invoiced. Read Invoiced customers, invoices, payments, subscriptions; create customers, draft invoices, notes. This page covers its hosted endpoint (https://invoiced.usefulapi.io/mcp).

### Is the Invoiced MCP by usefulapi server safe to use?

Invoiced MCP by usefulapi scores 64 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 Invoiced MCP by usefulapi server expose?

Invoiced MCP by usefulapi exposes 27 tools: invoiced_list_customers, invoiced_get_customer, invoiced_get_customer_balance, invoiced_list_contacts, invoiced_list_invoices, and 22 more. Their descriptions and schemas cost roughly 3,760 tokens of context every time the server is loaded.

### Does the Invoiced MCP by usefulapi server require authentication?

Yes. Invoiced MCP by usefulapi 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 Invoiced MCP by usefulapi server still maintained?

Invoiced MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 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://invoiced.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/invoiced/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-invoiced/invoiced.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-invoiced/invoiced.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-invoiced/invoiced