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.

ChargeOver MCP by usefulapi

REMOTE · CHARGEOVER.USEFULAPI.IO

Read ChargeOver customers, invoices, transactions, subscriptions, reports; create customers, quotes.

63 Trust /100

Last scanned (23 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 16 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 Usability78
  • 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 4223 tokens (~168/item across 25 items; 25 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 26 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.

  • 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 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 59

    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 16 Oct 2026 · Probed https://chargeover.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 chargeover.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://chargeover.usefulapi.io/.well-known/oauth-protected-resource/mcp"

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

Protected resource metadata

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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://chargeover.usefulapi.io/mcp Redirected 302 https://usefulapi.io/chargeover/
http (plaintext) http://chargeover.usefulapi.io/mcp Inconclusive 302 http://chargeover.usefulapi.io/mcp
MCP tools · 25 exposed · ~4,020 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
chargeover_create_contact ~143

WRITE: add a contact (person) to an existing customer. No email is sent by this call. Returns the new user_id. POST /user.

NameTypeReqDescription
customer_idintegeryesThe customer the contact belongs to.
emailstring–Email address.
external_keystring–Your own unique id for the contact.
first_namestring–First name.
last_namestring–Last name.
mobilestring–Mobile number.
namestring–Full name (alternative to first_name and last_name).
phonestring–Phone number.
titlestring–Job title.

No output schema declared.

No examples provided.

chargeover_create_customer ~321

WRITE: create a new customer (no charge, no invoice, no email is sent by this call). Returns the new customer_id. Add a primary contact with the superuser_* fields. Use chargeover_list_customers first to avoid a duplicate (external_key is unique). POST /customer.

NameTypeReqDescription
bill_addr1string–Billing address line 1.
bill_addr2string–Billing address line 2.
bill_citystring–Billing city.
bill_countrystring–Billing country.
bill_postcodestring–Billing postal code.
bill_statestring–Billing state/province.
companystringyesCompany / customer name.
external_keystring–Your own unique id for the customer (cannot be reused by default, even after deletion).
parent_customer_idinteger–Parent customer id, to create a child customer.
ship_addr1string–Shipping address line 1.
ship_addr2string–Shipping address line 2.
ship_citystring–Shipping city.
ship_countrystring–Shipping country.
ship_postcodestring–Shipping postal code.
ship_statestring–Shipping state/province.
superuser_emailstring–Primary contact email address.
superuser_first_namestring–Primary contact first name.
superuser_last_namestring–Primary contact last name.
superuser_phonestring–Primary contact phone number.

No output schema declared.

No examples provided.

chargeover_create_note ~120

WRITE: add a note to a customer, subscription, invoice, contact, quote or item (shown in the ChargeOver UI to the team; never sent to the customer). Returns the note id. POST /note.

NameTypeReqDescription
context_idintegeryesThe id of that record (customer_id, package_id, invoice_id, user_id, quote_id or item_id).
context_strstringyesWhat the note is attached to (billing_package = a subscription, user = a contact).
notestringyesThe note text.

No output schema declared.

No examples provided.

chargeover_create_quote ~251

WRITE: create a quote (a proposal) for an existing customer. Nothing is billed and no email is sent: the quote stays open until someone sends or accepts it in ChargeOver. Each line refers to an existing item (chargeover_list_items). paycycle: one = one-time invoice, mon = monthly, 2mn = every 2 months, qtr = quarterly, six = every 6 months, yrl = yearly, 2yr, 3yr, 1wk = weekly, 2wk. Returns the new quote_id. POST /quote.

NameTypeReqDescription
customer_idintegeryesThe customer the quote is for.
datestring–A date as YYYY-MM-DD.
external_keystring–Your own unique id for the quote.
line_itemsarrayyesAt least one line.
memostring–Memo shown to the customer on the quote.
nicknamestring–Nickname of the quote.
paycyclestringyesBilling cycle of the quote.
refnumberstring–Your reference number for the quote.
validuntil_datestring–Quote valid until, YYYY-MM-DD.

No output schema declared.

No examples provided.

chargeover_get_contact ~54

Get one contact (user) by user_id: name, email, phone, username, the customers they belong to. GET /user/{user_id}.

NameTypeReqDescription
idintegeryesThe user_id (a number).

No output schema declared.

No examples provided.

chargeover_get_customer ~54

Get one customer by customer_id: company, status, addresses, primary contact, terms, balance fields, custom fields. GET /customer/{customer_id}.

NameTypeReqDescription
idintegeryesThe customer_id (a number).

No output schema declared.

No examples provided.

chargeover_get_invoice ~54

Get one invoice by invoice_id: status, line items, totals, balance, payments and credits applied, billing address. GET /invoice/{invoice_id}.

NameTypeReqDescription
idintegeryesThe invoice_id (a number).

No output schema declared.

No examples provided.

chargeover_get_item ~55

Get one item (product, service or discount) by item_id: name, type, SKU, pricing tiers per currency. GET /item/{item_id}.

NameTypeReqDescription
idintegeryesThe item_id (a number).

No output schema declared.

No examples provided.

chargeover_get_quote ~55

Get one quote by quote_id: status, line items, totals, memo, links to the invoice or subscription it became. GET /quote/{quote_id}.

NameTypeReqDescription
idintegeryesThe quote_id (a number).

No output schema declared.

No examples provided.

chargeover_get_report ~71

A report's name, its available_filters (field names and allowed operators), available_columns and default_columns. Read this before chargeover_run_report to know which filters and columns to use. GET /_report/{report_id}.

NameTypeReqDescription
report_idintegeryesThe report_id from chargeover_list_reports.

No output schema declared.

No examples provided.

chargeover_get_subscription ~55

Get one subscription (package) by package_id: status, payment cycle, pay method, next invoice date, line items. GET /package/{package_id}.

NameTypeReqDescription
idintegeryesThe package_id (a number).

No output schema declared.

No examples provided.

chargeover_get_transaction ~63

Get one transaction (payment, refund or credit that already happened) by transaction_id: amount, method, status, the invoices it was applied to, related refunds. GET /transaction/{transaction_id}.

NameTypeReqDescription
idintegeryesThe transaction_id (a number).

No output schema declared.

No examples provided.

chargeover_list_contacts ~186

List contacts (the people at customers; the API calls them users). Filterable fields: user_id, external_key, first_name, last_name, email, phone, user_type_id, username, customers.customer_id (contacts of one customer). Paged: pass next_offset as offset. GET /user.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_coupons ~166

List coupons (code, description, type, enabled, linked discount item). Filterable fields: none documented; the list is small. Paged: pass next_offset as offset. GET /coupon.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_customers ~229

List customers (companies that are billed). Filterable fields: customer_id, parent_customer_id, bill_state, ship_state, bill_country, ship_country, external_key, token, company, superuser_id, superuser_email, customer_status_state (a = active, i = inactive), customer_status_str (active-current, active-overdue, inactive-manual, inactive-activity), custom_1..custom_50, write_datetime, mod_datetime. Paged: pass next_offset as offset. GET /customer.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_invoices ~259

List invoices with status, totals, credits, payments and balance. Filterable fields: invoice_id, refnumber, customer_id, invoice_status_str (open-unpaid, open-overdue, open-collections, closed-void, closed-paid), invoice_status_state (o = open, c = closed), package_id, package_token, date, currency_id, total, balance, subtotal, token, bill_state, bill_country, line_items.item_id, write_datetime, mod_datetime. Paged: pass next_offset as offset. GET /invoice.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
include_line_itemsboolean–true = include each record's line items (bigger reply). Default false.
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_items ~195

List items: the products, services and discounts that go on invoices, quotes and subscriptions, with their pricing tiers. Filterable fields: item_id, name, external_key, accounting_sku, item_type (service or discount), custom_1, custom_2, custom_3. Paged: pass next_offset as offset. GET /item.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_notes ~176

List notes attached to customers, subscriptions, invoices, contacts, quotes and items. Filterable fields: context_str (customer, billing_package, invoice, user, quote, item), context_id. Paged: pass next_offset as offset. GET /note.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_quotes ~224

List quotes (proposals for a customer or lead; the list has no line items, get one quote for those). Filterable fields: quote_id, customer_id, brand_id, currency_id, refnumber, token, external_key, date, bill_state, bill_country, quote_status_str (open-new, open-sent, closed-won, closed-lost), quote_status_state (o = open, c = closed). Paged: pass next_offset as offset. GET /quote.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_reports ~35

List the account's saved reports (report_id and name). Run one with chargeover_run_report. GET /_report.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

chargeover_list_subscriptions ~286

List subscriptions (the API calls them packages): recurring billing plans of customers. Filterable fields: package_id, customer_id, token, brand_id, paymethod, paycycle (mon, qtr, yrl...), nickname, package_status_state (a active, c cancelled, e expired, s suspended), package_status_str (active-trial, active-current, active-overdue, canceled-nonpayment, canceled-manual, expired-expired, expired-trial, suspended-suspended), external_key, write_datetime, mod_datetime, cancel_datetime, line_items.item_id, customer.superuser_email, customer.users.email. Paged: pass next_offset as offset. GET /package.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
include_line_itemsboolean–true = include each record's line items (bigger reply). Default false.
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_transactions ~255

List transactions (payments, refunds and credits that already happened; this tool only reads them). Filterable fields: transaction_id, customer_id, gateway_id, currency_id, creditcard_id, ach_id, tokenized_id, token, external_key, gateway_status, gateway_transid, amount, fee, transaction_type, transaction_method, transaction_detail, transaction_datetime, transaction_status.state, transaction_status.str, applied_to.invoice_id, applied_to.package_id. Paged: pass next_offset as offset. GET /transaction.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
include_applied_toboolean–true = include the invoices each transaction was applied to (bigger reply). Default false.
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_list_usage ~171

List usage (metered billing) data points recorded against subscription line items. Filterable fields: line_item_id, external_key, from (date), to (date). Paged: pass next_offset as offset. GET /usage.

NameTypeReqDescription
filtersarray–Filters, all combined with AND. Example: [{field:'customer_id',op:'EQUALS',value:12},{field:'date',op:'GTE',value:'2026-01-01'}].
limitinteger–Records per page, 1-500 (default 50).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.

No output schema declared.

No examples provided.

chargeover_run_report ~241

Run a saved report and return its rows (read only; nothing is changed). Filters use the report's own field names from chargeover_get_report, for example [{field:'transaction_transaction_date',op:'GTE',value:'2026-01-01'}]. Operators vary by field (dates GTE/LTE/EQUALS, ids EQUALS, strings CONTAINS/DOES_NOT_CONTAIN). To page (offset > 0) an order is required. Max 1000 rows per page. POST /_report/{report_id}/_action/reportData.

NameTypeReqDescription
columnsarray–Column names to return (default: the report's default columns).
filtersarray–Report filters (combined with AND).
limitinteger–Rows per page, 1-1000 (default 100).
offsetinteger–Records to skip (default 0). Use next_offset from the previous reply.
orderstring–Sort as field:ASC or field:DESC, for example invoice_id:DESC.
report_idintegeryesThe report_id from chargeover_list_reports.

No output schema declared.

No examples provided.

chargeover_update_customer ~301

WRITE: change fields of an existing customer; send only the fields to change. Cannot touch payment methods, balances or status. Replaces the previous values of the fields you send. PUT /customer/{customer_id}.

NameTypeReqDescription
bill_addr1string–Billing address line 1.
bill_addr2string–Billing address line 2.
bill_citystring–Billing city.
bill_countrystring–Billing country.
bill_postcodestring–Billing postal code.
bill_statestring–Billing state/province.
companystring–New company / customer name.
customer_idintegeryesThe customer_id to update.
external_keystring–Your own unique id for the customer (cannot be reused by default, even after deletion).
ship_addr1string–Shipping address line 1.
ship_addr2string–Shipping address line 2.
ship_citystring–Shipping city.
ship_countrystring–Shipping country.
ship_postcodestring–Shipping postal code.
ship_statestring–Shipping state/province.
superuser_emailstring–Primary contact email address.
superuser_first_namestring–Primary contact first name.
superuser_last_namestring–Primary contact last name.
superuser_phonestring–Primary contact phone number.

No output schema declared.

No examples provided.

Install

How do I install the ChargeOver MCP by usefulapi server?

ChargeOver MCP by usefulapi is a hosted endpoint at https://chargeover.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 · chargeover.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-chargeover 'https://chargeover.usefulapi.io/mcp'
Common questions

What is the ChargeOver MCP by usefulapi server?

ChargeOver MCP by usefulapi is listed in the public MCP registry as io.usefulapi/chargeover. Read ChargeOver customers, invoices, transactions, subscriptions, reports; create customers, quotes. This page covers its hosted endpoint (https://chargeover.usefulapi.io/mcp).

Is the ChargeOver MCP by usefulapi server safe to use?

ChargeOver MCP by usefulapi scores 63 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 ChargeOver MCP by usefulapi server expose?

ChargeOver MCP by usefulapi exposes 25 tools: chargeover_list_customers, chargeover_list_contacts, chargeover_list_invoices, chargeover_list_transactions, chargeover_list_quotes, and 20 more. Their descriptions and schemas cost roughly 4,020 tokens of context every time the server is loaded.

Does the ChargeOver MCP by usefulapi server require authentication?

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

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