io.usefulapi/chargebee
REMOTE · CHARGEBEE.USEFULAPI.IO · SCANNED SEP 20
Read Chargebee customers, subscriptions, invoices, items, transactions, credit notes and coupons.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1045 tokens (~80/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the io.usefulapi/chargebee MCP server?
io.usefulapi/chargebee is a hosted endpoint at https://chargebee.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 · chargebee.usefulapi.io
claude mcp add --transport http io-usefulapi-chargebee 'https://chargebee.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-chargebee": {
"url": "https://chargebee.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-chargebee": {
"type": "http",
"url": "https://chargebee.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-chargebee] url = "https://chargebee.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-chargebee": {
"type": "remote",
"url": "https://chargebee.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-chargebee --url 'https://chargebee.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-chargebee:
url: "https://chargebee.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-chargebee": {
"Transport": "http",
"Url": "https://chargebee.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-chargebee -t streamable-http -u 'https://chargebee.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-chargebee": {
"type": "http",
"url": "https://chargebee.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://chargebee.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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | afd18281e166b6f20e09c7a0b335f6b8 |
| SANs: usefulapi.io, chargebee.usefulapi.io, *.chargebee.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 chargebee.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://chargebee.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://chargebee.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://chargebee.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://chargebee.usefulapi.io/mcp |
| Authorisation server | https://chargebee.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chargebee.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://chargebee.usefulapi.io/mcp | Inconclusive | 401 |
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 →
chargebee_create_customer Create customer ~124
Creates a customer in Chargebee (additive). Chargebee auto-generates the id unless you pass one. Chargebee API: POST /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name. |
| string | – | Customer email address. | |
| first_name | string | – | Customer first name. |
| id | string | – | Optional custom customer id (Chargebee auto-generates if omitted). |
| last_name | string | – | Customer last name. |
| locale | string | – | Locale, e.g. fr-CA. |
| phone | string | – | Phone number. |
No output schema declared.
No examples provided.
chargebee_get_customer Get customer ~40
Retrieve a single customer by id. Chargebee API: GET /customers/{customer_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Chargebee customer id. |
No output schema declared.
No examples provided.
chargebee_get_invoice Get invoice ~41
Retrieve a single invoice by id. Chargebee API: GET /invoices/{invoice_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | Chargebee invoice id. |
No output schema declared.
No examples provided.
chargebee_get_subscription Get subscription ~40
Retrieve a single subscription by id. Chargebee API: GET /subscriptions/{subscription_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | Chargebee subscription id. |
No output schema declared.
No examples provided.
chargebee_list_coupons List coupons ~60
List coupons. Chargebee API: GET /coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
No output schema declared.
No examples provided.
chargebee_list_credit_notes List credit notes ~84
List credit notes. Filter by customer. Chargebee API: GET /credit_notes.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only credit notes of this customer (→ customer_id[is]). |
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
No output schema declared.
No examples provided.
chargebee_list_customers List customers ~106
List customers, newest first. Filter by email or creation time. Chargebee API: GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | integer | – | Unix timestamp; only customers created after this (→ created_at[after]). |
| string | – | Exact email to match (→ email[is]). | |
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
No output schema declared.
No examples provided.
chargebee_list_invoices List invoices ~99
List invoices. Filter by customer or status. Chargebee API: GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only invoices of this customer (→ customer_id[is]). |
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
| status | string | – | Invoice status filter (→ status[is]). |
No output schema declared.
No examples provided.
chargebee_list_item_prices List item prices ~89
List Product Catalog 2.0 item prices. Filter by item. Chargebee API: GET /item_prices.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | – | Only prices of this item (→ item_id[is]). |
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
No output schema declared.
No examples provided.
chargebee_list_items List items ~88
List Product Catalog 2.0 items (plans, addons, charges). Filter by type. Chargebee API: GET /items.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
| type | string | – | Item type filter (→ type[is]). |
No output schema declared.
No examples provided.
chargebee_list_subscriptions List subscriptions ~98
List subscriptions. Filter by customer or status. Chargebee API: GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only subscriptions of this customer (→ customer_id[is]). |
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
| status | string | – | Subscription status filter (→ status[is]). |
No output schema declared.
No examples provided.
chargebee_list_transactions List transactions ~83
List payment/refund transactions. Filter by customer. Chargebee API: GET /transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | – | Only transactions of this customer (→ customer_id[is]). |
| limit | integer | – | Max results per page (Chargebee max 100). |
| offset | string | – | Opaque pagination token from a previous response's `next_offset`. |
No output schema declared.
No examples provided.
chargebee_update_customer Update customer ~93
Updates a customer's details in Chargebee. Chargebee API: POST /customers/{customer_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name. |
| customer_id | string | yes | Chargebee customer id to update. |
| string | – | Customer email address. | |
| first_name | string | – | Customer first name. |
| last_name | string | – | Customer last name. |
| phone | string | – | Phone number. |
No output schema declared.
No examples provided.
What is the io.usefulapi/chargebee MCP server?
io.usefulapi/chargebee is an MCP server listed in the public MCP registry as io.usefulapi/chargebee. Read Chargebee customers, subscriptions, invoices, items, transactions, credit notes and coupons. This page covers its hosted endpoint (https://chargebee.usefulapi.io/mcp).
Is the io.usefulapi/chargebee MCP server safe to use?
io.usefulapi/chargebee scores 86 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 io.usefulapi/chargebee MCP server expose?
io.usefulapi/chargebee exposes 13 tools: chargebee_list_customers, chargebee_get_customer, chargebee_list_subscriptions, chargebee_get_subscription, chargebee_list_invoices, and 8 more. Their descriptions and schemas cost roughly 1,045 tokens of context every time the server is loaded.
Does the io.usefulapi/chargebee MCP server require authentication?
Yes. io.usefulapi/chargebee 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 io.usefulapi/chargebee MCP server still maintained?
io.usefulapi/chargebee is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.