Skip to content

MCP servers › io.usefulapi › invoiced

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.usefulapi/invoiced

Read Invoiced customers, invoices, payments, subscriptions; create customers, draft invoices, notes. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedPricing: freemium · AI-classifiedversion 1.3.4JavaScriptstreamable HTTP27 tools

Summary

io.usefulapi/invoiced is a remote MCP server listed in the official MCP registry at version 1.3.4. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 27 tools, 0 resources and 1 prompt.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Repository
public
Tools
27
Described as changing data
4 of 27 toolsAI-classified
Mainly works on
accounts and data in outside web servicesAI-classified
Topic
finance-and-paymentsAI-classified
Pricing
freemiumAI-classified
Last tested
2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (invoiced_create_customer, invoiced_create_draft_invoice, invoiced_add_note, invoiced_create_task). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

  • 4 tools are described as changing something (invoiced_create_customer, invoiced_create_draft_invoice, invoiced_add_note, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.3.4, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-11 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-10-11 to 2026-10-22; 3 in the 90 days before the 2026-10-23 snapshot.
Most recent 3 versions
  • 1.3.4 · 2026-10-22
  • 1.3.3 · 2026-10-21
  • 1.0.0 · 2026-10-11
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.3.4 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
27tools
0resources
1prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

4 of 27 tools are described as changing something (creating, editing, deleting, sending or running).

  • invoiced_list_customersreads or searches

    “List customers (accounts receivable debtors): name, number, email, payment terms, currency, autopay and chasing settings, owner.”

    Publisher declares: read-only yes · destructive no · open-world yes

    8 inputs
    • open_balanceboolean“true = only customers with an open balance; false = only those without.”
    • payment_sourceboolean“true = only customers with a saved payment method.”
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • metadataobject“Exact-match filters on metadata keys, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_get_customerreads or searches

    “One customer by id: contact details, address, terms, currency, autopay, chasing cadence, credit hold/limit, parent customer, metadata.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • customer_idintegerrequired“Invoiced customer id (numeric; not the customer number).”
  • invoiced_get_customer_balancereads or searches

    “A customer's current balance: total outstanding, past due, and available credit, in the customer's currency (or `currency`).”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • customer_idintegerrequired“Invoiced customer id.”
    • currencystring“3-letter currency code (default: the customer's currency).”
  • invoiced_list_contactsreads or searches

    “List the contacts of one customer: name, title, email, phone, whether primary (copied on communications) and SMS-enabled.”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs, 1 required
    • customer_idintegerrequired“Invoiced customer id.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_list_invoicesreads or searches

    “List invoices with number, customer, status (draft, not_sent, sent, viewed, past_due, pending, paid, voided), dates, totals, balance and line items.”

    Publisher declares: read-only yes · destructive no · open-world yes

    10 inputs
    • customer_idinteger“Only this customer's invoices.”
    • paidboolean“true = only paid invoices; false = only unpaid.”
    • start_datestring“Invoices dated on or after this date or date-time.”
    • end_datestring“Invoices dated on or before this date (a bare date includes the whole day).”
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • metadataobject“Exact-match filters on metadata keys, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_get_invoicereads or searches

    “One invoice by id: status, dates, payment terms, totals, balance, line items, discounts, taxes, ship-to, payment and PDF links.”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs, 1 required
    • invoice_idintegerrequired“Invoiced invoice id (numeric; find it with invoiced_list_invoices).”
    • expandarray“Relations to expand into full objects.”
  • invoiced_get_invoice_payment_planreads or searches

    “The payment plan (installments with dates, amounts and balances, and approval status) attached to an invoice.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • invoice_idintegerrequired“Invoiced invoice id.”
  • invoiced_list_paymentsreads or searches

    “List payments received: customer, date, amount, unapplied balance, method (check, wire, ACH, card, ...), reference, whether matched or voided.”

    Publisher declares: read-only yes · destructive no · open-world yes

    8 inputs
    • customer_idinteger“Only this customer's payments.”
    • start_datestring“Payments dated on or after this date or date-time.”
    • end_datestring“Payments dated on or before this date (a bare date includes the whole day).”
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_get_paymentreads or searches

    “One payment by id, including which invoices and credit notes it was applied to (`applied_to`).”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • payment_idintegerrequired“Invoiced payment id.”
  • invoiced_list_credit_notesreads or searches

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

    Publisher declares: read-only yes · destructive no · open-world yes

    9 inputs
    • customer_idinteger“Only this customer's credit notes.”
    • start_datestring“Credit notes dated on or after this date or date-time.”
    • end_datestring“Credit notes dated on or before this date (a bare date includes the whole day).”
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • metadataobject“Exact-match filters on metadata keys, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_get_credit_notereads or searches

    “One credit note by id with line items, totals and balance.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • credit_note_idintegerrequired“Invoiced credit note id.”
  • invoiced_list_estimatesreads or searches

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

    Publisher declares: read-only yes · destructive no · open-world yes

    9 inputs
    • customer_idinteger“Only this customer's estimates.”
    • start_datestring“Estimates dated on or after this date or date-time.”
    • end_datestring“Estimates dated on or before this date (a bare date includes the whole day).”
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • metadataobject“Exact-match filters on metadata keys, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
Show 15 more tools
  • invoiced_get_estimatereads or searches

    “One estimate by id with line items, totals, deposit and approval state.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • estimate_idintegerrequired“Invoiced estimate id.”
  • invoiced_list_itemsreads or searches

    “List the item catalog (products and services): id, name, currency, unit cost, type, taxable.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_get_itemreads or searches

    “One catalog item by its id (a string such as "delivery").”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • item_idstringrequired“Catalog item id (from invoiced_list_items).”
  • invoiced_list_tax_ratesreads or searches

    “List tax rates: id, name, value, whether a percentage, whether inclusive, currency.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_list_plansreads or searches

    “List subscription plans: id, name, currency, amount, pricing mode, billing interval, tiers.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_get_planreads or searches

    “One subscription plan by its id (a string).”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • plan_idstringrequired“Plan id (from invoiced_list_plans).”
  • invoiced_list_subscriptionsreads or searches

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

    Publisher declares: read-only yes · destructive no · open-world yes

    9 inputs
    • customer_idinteger“Only this customer's subscriptions.”
    • canceledboolean“true = only canceled subscriptions; false = only not canceled.”
    • finishedboolean“true = only finished subscriptions; false = only unfinished.”
    • updated_afterstring“Only records updated after this date or date-time.”
    • filterobject“Exact-match filters on object columns, e.g.”
    • metadataobject“Exact-match filters on metadata keys, e.g.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_get_subscriptionreads or searches

    “One subscription by id with plan, add-ons, billing period, contract terms, recurring total and MRR.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input, 1 required
    • subscription_idintegerrequired“Invoiced subscription id.”
  • invoiced_list_notesreads or searches

    “List collection notes, newest first, for one customer or one invoice (give exactly one), or all notes when neither is given.”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs
    • customer_idinteger“Only this customer's notes.”
    • invoice_idinteger“Only this invoice's notes.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_list_tasksreads or searches

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

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • customer_idinteger“Only this customer's tasks.”
    • completeboolean“true = only completed tasks; false = only open tasks.”
    • sortstring“Sort, "<column> asc|desc", e.g.”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_list_eventsreads or searches

    “The activity feed, newest first: event type (such as invoice.paid, customer.created), time, the object it concerns and who did it.”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs
    • related_object_typestring“Object type such as customer or invoice; with related_object_id: only events about this object.”
    • related_object_idinteger“Id of the object (needs related_object_type).”
    • pageinteger“Page number, from 1 (default 1).”
    • per_pageinteger“Results per page, 1-100 (default 25).”
  • invoiced_create_customercreates or changes datadescribed as changing data

    “WRITE: create a customer in Invoiced.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    17 inputs, 1 required
    • namestringrequired“Customer name.”
    • numberstring“Customer number (default: generated).”
    • emailstring
    • typestring“Default company.”
    • payment_termsstring“e.g.”
    • currencystring
    • attention_tostring
    • address1string
    • address2string
    • citystring
    • statestring
    • postal_codestring
    • countrystring
    • phonestring
    • tax_idstring
    • notesstring“Private notes.”
    • metadataobject“Metadata key/values (max 10 keys, names up to 40 characters, values up to 255).”
  • invoiced_create_draft_invoicecreates or changes datadescribed as changing data

    “WRITE: create a DRAFT invoice for a customer.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    11 inputs, 2 required
    • customer_idintegerrequired“Invoiced customer id (invoiced_list_customers).”
    • itemsarrayrequired“Line items.”
    • namestring“Document title (default "Invoice").”
    • numberstring“Invoice number (default: next in sequence).”
    • currencystring
    • datestring“Invoice date (default now).”
    • due_datestring“Due date (default: computed from the payment terms).”
    • payment_termsstring“e.g.”
    • purchase_orderstring
    • notesstring“Notes printed on the invoice.”
    • metadataobject“Metadata key/values (max 10 keys, names up to 40 characters, values up to 255).”
  • invoiced_add_notecreates or changes datadescribed as changing data

    “WRITE: add an internal note to a customer or an invoice (give exactly one).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • customer_idinteger“Customer to attach the note to.”
    • invoice_idinteger“Invoice to attach the note to.”
    • notesstringrequired“The note text.”
  • invoiced_create_taskcreates or changes datadescribed as changing data

    “WRITE: create a collection task for a customer (a reminder to call, write, email or review).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs, 3 required
    • namestringrequired“Task name, e.g.”
    • actionstringrequired“Kind of task.”
    • customer_idintegerrequired“Customer the task is about.”
    • user_idinteger“Invoiced user to assign it to.”
    • due_datestring“When it is due.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 27 tools
Says what it returns
85% of 27 tools
States limits, defaults or errors
48% of 27 tools
Says when to use it
15% of 27 tools
Items covered per tool
2.5 of 4 on average

Counted from the listing

Parameters with a description
90% of 133
Tools with a description
100% of 27
Typical description length
152 characters

The tool set

Counted from the listing

Tools
27
Size of the list
about 7,812 tokens for an agent to load (characters ÷ 4)
Naming
27 of 27 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 27 of 27 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://invoiced.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "invoiced": {
      "url": "https://invoiced.usefulapi.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "invoiced": {
      "type": "http",
      "url": "https://invoiced.usefulapi.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"invoiced","type":"http","url":"https://invoiced.usefulapi.io/mcp"}'
Claude Code
claude mcp add --transport http invoiced https://invoiced.usefulapi.io/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://invoiced.usefulapi.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint invoiced.usefulapi.io/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23
Repository github.com/m190/usefulapi-mcpOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.usefulapi · 341 servers
GitHub owner
a personal account (m190)
Repository
github.com/m190/usefulapi-mcp
Stars
0
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/invoiced

Answered from the data above

Is io.usefulapi/invoiced safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 4 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.usefulapi/invoiced free to use?

Its website (usefulapi.io/invoiced/) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does io.usefulapi/invoiced need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/invoiced been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.usefulapi/invoiced do?

It lists 27 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can io.usefulapi/invoiced change or delete data?

4 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.usefulapi/invoiced publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.usefulapi/invoiced?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 13
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 464 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 27 tools, 0 resources, 1 prompt.
  4. 1,611 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
freemium
read from usefulapi.io/invoiced/ · 2026-10-23

“Free $0 50 tool calls / month”

Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
prompts, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/invoiced: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.usefulapi/invoiced

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/invoiced)](https://protocolprobe.com/mcp/servers/io.usefulapi/invoiced)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology