Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Invoiced MCP by usefulapi

REMOTE · INVOICED.USEFULAPI.IO

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

64 Trust /100

Last scanned (55 minutes ago)

Scores higher than 46% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security78
Transport & Reachability0
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 +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.

  • 14 Oct 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • 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 functional
  • 13 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 60

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Probed https://invoiced.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of invoiced.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 302

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://invoiced.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://invoiced.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://invoiced.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://invoiced.usefulapi.io/mcp
Authorisation server https://invoiced.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://invoiced.usefulapi.io/mcp Redirected 302 https://usefulapi.io/invoiced/
http (plaintext) http://invoiced.usefulapi.io/mcp Inconclusive 302 http://invoiced.usefulapi.io/mcp
MCP tools · 27 exposed · ~3,760 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
invoiced_add_note ~77

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

NameTypeReqDescription
customer_idinteger–Customer to attach the note to.
invoice_idinteger–Invoice to attach the note to.
notesstringyesThe note text.

No output schema declared.

No examples provided.

invoiced_create_customer ~214

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.

NameTypeReqDescription
address1string––
address2string––
attention_tostring––
citystring––
countrystring––
currencystring––
emailstring––
metadataobject–Metadata key/values (max 10 keys, names up to 40 characters, values up to 255).
namestringyesCustomer name.
notesstring–Private notes.
numberstring–Customer number (default: generated).
payment_termsstring–e.g. "NET 30".
phonestring––
postal_codestring––
statestring––
tax_idstring––
typestring–Default company.

No output schema declared.

No examples provided.

invoiced_create_draft_invoice ~231

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.

NameTypeReqDescription
currencystring––
customer_idintegeryesInvoiced customer id (invoiced_list_customers).
datestring–Invoice date (default now).
due_datestring–Due date (default: computed from the payment terms).
itemsarrayyesLine items.
metadataobject–Metadata key/values (max 10 keys, names up to 40 characters, values up to 255).
namestring–Document title (default "Invoice").
notesstring–Notes printed on the invoice.
numberstring–Invoice number (default: next in sequence).
payment_termsstring–e.g. "NET 30".
purchase_orderstring––

No output schema declared.

No examples provided.

invoiced_create_task ~111

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

NameTypeReqDescription
actionstringyesKind of task.
customer_idintegeryesCustomer the task is about.
due_datestring–When it is due.
namestringyesTask name, e.g. "Call about overdue invoice".
user_idinteger–Invoiced user to assign it to.

No output schema declared.

No examples provided.

invoiced_get_credit_note ~46

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

NameTypeReqDescription
credit_note_idintegeryesInvoiced credit note id.

No output schema declared.

No examples provided.

invoiced_get_customer ~66

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

NameTypeReqDescription
customer_idintegeryesInvoiced customer id (numeric; not the customer number).

No output schema declared.

No examples provided.

invoiced_get_customer_balance ~74

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

NameTypeReqDescription
currencystring–3-letter currency code (default: the customer's currency).
customer_idintegeryesInvoiced customer id.

No output schema declared.

No examples provided.

invoiced_get_estimate ~46

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

NameTypeReqDescription
estimate_idintegeryesInvoiced estimate id.

No output schema declared.

No examples provided.

invoiced_get_invoice ~99

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}.

NameTypeReqDescription
expandarray–Relations to expand into full objects.
invoice_idintegeryesInvoiced invoice id (numeric; find it with invoiced_list_invoices).

No output schema declared.

No examples provided.

invoiced_get_invoice_payment_plan ~67

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.

NameTypeReqDescription
invoice_idintegeryesInvoiced invoice id.

No output schema declared.

No examples provided.

invoiced_get_item ~47

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

NameTypeReqDescription
item_idstringyesCatalog item id (from invoiced_list_items).

No output schema declared.

No examples provided.

invoiced_get_payment ~55

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

NameTypeReqDescription
payment_idintegeryesInvoiced payment id.

No output schema declared.

No examples provided.

invoiced_get_plan ~43

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

NameTypeReqDescription
plan_idstringyesPlan id (from invoiced_list_plans).

No output schema declared.

No examples provided.

invoiced_get_subscription ~51

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

NameTypeReqDescription
subscription_idintegeryesInvoiced subscription id.

No output schema declared.

No examples provided.

invoiced_list_contacts ~125

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

NameTypeReqDescription
customer_idintegeryesInvoiced customer id.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".

No output schema declared.

No examples provided.

invoiced_list_credit_notes ~247

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

NameTypeReqDescription
customer_idinteger–Only this customer's credit notes.
end_datestring–Credit notes dated on or before this date (a bare date includes the whole day).
filterobject–Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
metadataobject–Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".
start_datestring–Credit notes dated on or after this date or date-time.
updated_afterstring–Only records updated after this date or date-time.

No output schema declared.

No examples provided.

invoiced_list_customers ~247

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.

NameTypeReqDescription
filterobject–Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
metadataobject–Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
open_balanceboolean–true = only customers with an open balance; false = only those without.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
payment_sourceboolean–true = only customers with a saved payment method.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".
updated_afterstring–Only records updated after this date or date-time.

No output schema declared.

No examples provided.

invoiced_list_estimates ~253

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

NameTypeReqDescription
customer_idinteger–Only this customer's estimates.
end_datestring–Estimates dated on or before this date (a bare date includes the whole day).
filterobject–Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
metadataobject–Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".
start_datestring–Estimates dated on or after this date or date-time.
updated_afterstring–Only records updated after this date or date-time.

No output schema declared.

No examples provided.

invoiced_list_events ~143

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.

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

No output schema declared.

No examples provided.

invoiced_list_invoices ~292

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.

NameTypeReqDescription
customer_idinteger–Only this customer's invoices.
end_datestring–Invoices dated on or before this date (a bare date includes the whole day).
filterobject–Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
metadataobject–Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
paidboolean–true = only paid invoices; false = only unpaid.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".
start_datestring–Invoices dated on or after this date or date-time.
updated_afterstring–Only records updated after this date or date-time.

No output schema declared.

No examples provided.

invoiced_list_items ~173

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.

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

No output schema declared.

No examples provided.

invoiced_list_notes ~125

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.

NameTypeReqDescription
customer_idinteger–Only this customer's notes.
invoice_idinteger–Only this invoice's notes.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).

No output schema declared.

No examples provided.

invoiced_list_payments ~228

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

NameTypeReqDescription
customer_idinteger–Only this customer's payments.
end_datestring–Payments dated on or before this date (a bare date includes the whole day).
filterobject–Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".
start_datestring–Payments dated on or after this date or date-time.
updated_afterstring–Only records updated after this date or date-time.

No output schema declared.

No examples provided.

invoiced_list_plans ~158

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

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

No output schema declared.

No examples provided.

invoiced_list_subscriptions ~246

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

NameTypeReqDescription
canceledboolean–true = only canceled subscriptions; false = only not canceled.
customer_idinteger–Only this customer's subscriptions.
filterobject–Exact-match filters on object columns, e.g. {"paid": false, "currency": "usd"}. Booleans are sent as 1/0.
finishedboolean–true = only finished subscriptions; false = only unfinished.
metadataobject–Exact-match filters on metadata keys, e.g. {"account-rep": "Jan"}.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".
updated_afterstring–Only records updated after this date or date-time.

No output schema declared.

No examples provided.

invoiced_list_tasks ~138

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

NameTypeReqDescription
completeboolean–true = only completed tasks; false = only open tasks.
customer_idinteger–Only this customer's tasks.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
per_pageinteger–Results per page, 1-100 (default 25).
sortstring–Sort, "<column> asc|desc", e.g. "date desc".

No output schema declared.

No examples provided.

invoiced_list_tax_rates ~158

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

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

No output schema declared.

No examples provided.

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.

remote · invoiced.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-invoiced 'https://invoiced.usefulapi.io/mcp'
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.