Recharge MCP by usefulapi
REMOTE · RECHARGE.USEFULAPI.IO
Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 2 Nov 26 −59
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “cancel_or_reactivate_a_subscription” functional
- New prompt “find_failed_charges_with_the_customers_behind_them” functional
- New prompt “look_up_a_customer_s_subscriptions_and_next_charge” functional
- New prompt “see_which_charges_are_scheduled_soon” functional
- New prompt “skip_a_scheduled_charge” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 0
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 0
- Server version: 1.26.0 → 1.28.0 functional
- 27 Oct 26 0
- Server version: 1.25.0 → 1.26.0 functional
- 25 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.3 → 1.23.0 functional
- Server version: 1.22.0 → 1.22.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.21.0 → 1.22.0 functional
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.18.0 → 1.20.0 functional
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 5 Nov 2026 · Probed https://recharge.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 recharge.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recharge.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/recharge/ |
| http (plaintext) | http://recharge.usefulapi.io/mcp | Inconclusive | 302 | http://recharge.usefulapi.io/mcp |
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 →
recharge_activate_subscription Activate subscription ~59
REACTIVATES a cancelled subscription — resumes future charges. This MODIFIES live data. Recharge REST: POST /subscriptions/{id}/activate (no body). Returns { subscription }.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Subscription id to reactivate. |
No output schema declared.
No examples provided.
recharge_cancel_customer_subscription Cancel subscription ~106
CANCELS an active subscription — stops all future charges. This MODIFIES live data. A `cancellation_reason` is required. Recharge REST: POST /subscriptions/{id}/cancel with JSON body { cancellation_reason, cancellation_reason_comments? }. Returns { subscription }.
| Name | Type | Req | Description |
|---|---|---|---|
| cancellation_reason | string | yes | Reason for cancelling (required by Recharge). |
| cancellation_reason_comments | string | – | Optional free-text detail about the cancellation. |
| id | integer | yes | Subscription id to cancel. |
No output schema declared.
No examples provided.
recharge_get_charge Get charge ~49
Get a single charge by id, including line items, totals, status, scheduled date, and customer/address. Recharge REST: GET /charges/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Charge id. |
No output schema declared.
No examples provided.
recharge_get_customer Get customer ~48
Get a single customer by id, including contact details, Shopify customer id, and subscription/charge counts. Recharge REST: GET /customers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Customer id. |
No output schema declared.
No examples provided.
recharge_get_order Get order ~51
Get a single order by id, including line items, totals, status, and the charge/subscription it came from. Recharge REST: GET /orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Order id. |
No output schema declared.
No examples provided.
recharge_get_store Get store ~35
Get the Recharge store/shop info — name, domain, currency, timezone, and account settings. Recharge REST: GET /store.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recharge_get_subscription Get subscription ~49
Get a single subscription by id, including product, quantity, price, charge interval, and next charge date. Recharge REST: GET /subscriptions/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Subscription id. |
No output schema declared.
No examples provided.
recharge_list_addresses List addresses ~270
List customer addresses with optional filters (customer, ids, created/updated date ranges). Returns { addresses }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Filter to addresses created on/before this date (ISO 8601). |
| created_at_min | string | – | Filter to addresses created on/after this date (ISO 8601). |
| cursor | string | – | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
| customer_id | integer | – | Filter by customer id. |
| ids | string | – | Comma-separated list of address ids to fetch. |
| limit | integer | – | Max results per page (1-250, default 50). |
| updated_at_max | string | – | Filter to addresses updated on/before this date (ISO 8601). |
| updated_at_min | string | – | Filter to addresses updated on/after this date (ISO 8601). |
No output schema declared.
No examples provided.
recharge_list_charges List charges ~450
List charges with optional filters (customer, address, status, ids, purchase item, scheduled/created/updated date ranges) and sorting. Returns { charges }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /charges.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | integer | – | Filter by address id. |
| created_at_max | string | – | Filter to charges created on/before this date (ISO 8601). |
| created_at_min | string | – | Filter to charges created on/after this date (ISO 8601). |
| cursor | string | – | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
| customer_id | integer | – | Filter by customer id. |
| ids | string | – | Comma-separated list of charge ids to fetch. |
| limit | integer | – | Max results per page (1-250, default 50). |
| purchase_item_id | integer | – | Filter to charges containing this purchase item (subscription/onetime line item) id. |
| scheduled_at | string | – | Filter to charges scheduled on this date (ISO 8601). |
| scheduled_at_max | string | – | Filter to charges scheduled on/before this date (ISO 8601). |
| scheduled_at_min | string | – | Filter to charges scheduled on/after this date (ISO 8601). |
| sort_by | string | – | Sort order: id-asc | id-desc | updated_at-asc | updated_at-desc | scheduled_at-asc | scheduled_at-desc. |
| status | string | – | Filter by charge status: success | queued | error | refunded | partially_refunded | skipped | pending_manual_payment | pending. |
| updated_at_max | string | – | Filter to charges updated on/before this date (ISO 8601). |
| updated_at_min | string | – | Filter to charges updated on/after this date (ISO 8601). |
No output schema declared.
No examples provided.
recharge_list_customers List customers ~307
List customers with optional filters (email, ids, created/updated date ranges) and sorting. Returns { customers }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| created_at_max | string | – | Filter to customers created on/before this date (ISO 8601). |
| created_at_min | string | – | Filter to customers created on/after this date (ISO 8601). |
| cursor | string | – | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
| string | – | Filter by customer email. | |
| ids | string | – | Comma-separated list of customer ids to fetch. |
| limit | integer | – | Max results per page (1-250, default 50). |
| sort_by | string | – | Sort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc. |
| updated_at_max | string | – | Filter to customers updated on/before this date (ISO 8601). |
| updated_at_min | string | – | Filter to customers updated on/after this date (ISO 8601). |
No output schema declared.
No examples provided.
recharge_list_onetimes List one-times ~280
List one-time (non-recurring) line items with optional filters (customer, address, created/updated date ranges). Returns { onetimes }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /onetimes.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | integer | – | Filter by address id. |
| created_at_max | string | – | Filter to one-times created on/before this date (ISO 8601). |
| created_at_min | string | – | Filter to one-times created on/after this date (ISO 8601). |
| cursor | string | – | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
| customer_id | integer | – | Filter by customer id. |
| limit | integer | – | Max results per page (1-250, default 50). |
| updated_at_max | string | – | Filter to one-times updated on/before this date (ISO 8601). |
| updated_at_min | string | – | Filter to one-times updated on/after this date (ISO 8601). |
No output schema declared.
No examples provided.
recharge_list_orders List orders ~411
List orders with optional filters (customer, address, subscription, status, ids, created/updated/scheduled date ranges) and sorting. Returns { orders }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /orders.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | integer | – | Filter by address id. |
| created_at_max | string | – | Filter to orders created on/before this date (ISO 8601). |
| created_at_min | string | – | Filter to orders created on/after this date (ISO 8601). |
| cursor | string | – | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
| customer_id | integer | – | Filter by customer id. |
| ids | string | – | Comma-separated list of order ids to fetch. |
| limit | integer | – | Max results per page (1-250, default 50). |
| scheduled_at_max | string | – | Filter to orders scheduled on/before this date (ISO 8601). |
| scheduled_at_min | string | – | Filter to orders scheduled on/after this date (ISO 8601). |
| sort_by | string | – | Sort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc. |
| status | string | – | Filter by order status, e.g. success | queued | error | refunded | skipped | cancelled. |
| subscription_id | integer | – | Filter by subscription id. |
| updated_at_max | string | – | Filter to orders updated on/before this date (ISO 8601). |
| updated_at_min | string | – | Filter to orders updated on/after this date (ISO 8601). |
No output schema declared.
No examples provided.
recharge_list_products List products ~165
List Recharge products (subscription rules / discounts per product) with optional id filter. Returns { products }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /products.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
| ids | string | – | Comma-separated list of product ids to fetch. |
| limit | integer | – | Max results per page (1-250, default 50). |
No output schema declared.
No examples provided.
recharge_list_subscriptions List subscriptions ~344
List subscriptions with optional filters (customer, address, status, ids, created/updated date ranges) and sorting. Returns { subscriptions }. Pagination is cursor-based: pass `limit` (default 50, max 250) and read `next_cursor` / `previous_cursor` from the response. IMPORTANT: when paging with `cursor`, Recharge accepts ONLY `limit` alongside it — omit every other filter on cursor requests. Recharge REST: GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | integer | – | Filter by address id. |
| created_at_max | string | – | Filter to subscriptions created on/before this date (ISO 8601). |
| created_at_min | string | – | Filter to subscriptions created on/after this date (ISO 8601). |
| cursor | string | – | Pagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests. |
| customer_id | integer | – | Filter by customer id. |
| ids | string | – | Comma-separated list of subscription ids to fetch. |
| limit | integer | – | Max results per page (1-250, default 50). |
| sort_by | string | – | Sort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc. |
| status | string | – | Filter by subscription status, e.g. active | cancelled | expired. |
| updated_at_max | string | – | Filter to subscriptions updated on/before this date (ISO 8601). |
| updated_at_min | string | – | Filter to subscriptions updated on/after this date (ISO 8601). |
No output schema declared.
No examples provided.
recharge_skip_charge Skip charge ~105
SKIPS a scheduled charge — prevents it from processing on its scheduled date. This MODIFIES live billing data. Some stores require the specific line items to skip via `purchase_item_ids`. Recharge REST: POST /charges/{id}/skip with JSON body { purchase_item_ids? }. Returns { charge }.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Charge id to skip. |
| purchase_item_ids | array | – | The subscription/onetime line item ids to skip (some stores require this). |
No output schema declared.
No examples provided.
How do I install the Recharge MCP by usefulapi server?
Recharge MCP by usefulapi is a hosted endpoint at https://recharge.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 · recharge.usefulapi.io
claude mcp add --transport http io-usefulapi-recharge 'https://recharge.usefulapi.io/mcp'
What is the Recharge MCP by usefulapi server?
Recharge MCP by usefulapi is listed in the public MCP registry as io.usefulapi/recharge. Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions. This page covers its hosted endpoint (https://recharge.usefulapi.io/mcp).
Is the Recharge MCP by usefulapi server safe to use?
Recharge MCP by usefulapi scores 18 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 Recharge MCP by usefulapi server expose?
Recharge MCP by usefulapi exposes 15 tools: recharge_get_store, recharge_list_subscriptions, recharge_get_subscription, recharge_list_customers, recharge_get_customer, and 10 more. Their descriptions and schemas cost roughly 2,729 tokens of context every time the server is loaded.
Does the Recharge MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Recharge MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Recharge MCP by usefulapi server still maintained?
Recharge MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.