Home / MCP registry index / io.usefulapi/chargeover

ChargeOver MCP by usefulapi

io.usefulapi/chargeover in the official MCP registry. Endpoint https://chargeover.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read ChargeOver customers, invoices, transactions, subscriptions, reports; create customers, quotes.

We read its 25 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http chargeover https://chargeover.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "chargeover": {
      "url": "https://chargeover.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"chargeover","type":"http","url":"https://chargeover.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

chargeover_list_customers chargeover_list_contacts chargeover_list_invoices chargeover_list_transactions chargeover_list_quotes chargeover_list_subscriptions chargeover_list_items chargeover_list_notes chargeover_list_usage chargeover_list_coupons chargeover_get_customer chargeover_get_contact chargeover_get_invoice chargeover_get_transaction chargeover_get_quote chargeover_get_subscription chargeover_get_item chargeover_list_reports chargeover_get_report chargeover_run_report chargeover_create_customer chargeover_update_customer chargeover_create_contact chargeover_create_note chargeover_create_quote

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 6e8fe67885754aaa. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-chargeover/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-chargeover)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.