Skip to content

Recharge MCP by usefulapi

io.usefulapi/rechargeusefulapi.iostreamable-httpv1.41.4Scanned

Read subscriptions, customers, charges, orders; skip charges, cancel or activate subscriptions.

15 tools: 3 can delete or cancel things and 12 only read.

Tools: 3 delete, 0 irreversible, 0 write, 12 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Recharge MCP by usefulapi can do

The Recharge MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (3 tools: recharge_skip_charge, recharge_cancel_customer_subscription and recharge_activate_subscription). 12 tools only read.

2 tools read private data (recharge_list_customers and recharge_get_customer); 1 tool brings in text other people can write (recharge_list_customers).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.41.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 3Claude Code: deny
  • recharge_activate_subscriptionREACTIVATES a cancelled subscription — resumes future charges.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    REACTIVATES a cancelled subscription — resumes future charges. This MODIFIES live data. Recharge REST: POST /subscriptions/{id}/activate (no body). Returns { subscription }.

    Annotations the server declares

    • title: Activate subscription
    • destructiveHint: true
  • recharge_cancel_customer_subscriptionCANCELS an active subscription — stops all future charges.No findings

    Why it is in this group

    • The name "recharge_cancel_customer_subscription" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Cancel subscription
    • destructiveHint: true
  • recharge_skip_chargeSKIPS a scheduled charge — prevents it from processing on its scheduled date.No findings

    Why it is in this group

    • The name "recharge_skip_charge" says "charge": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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 }.

    Annotations the server declares

    • title: Skip charge
    • destructiveHint: true
Only reads 12Show 12 read-only tools
  • recharge_get_chargeGet a single charge by id, including line items, totals, status, scheduled date, and customer/address.No findings

    Why it is in this group

    • The name "recharge_get_charge" says "get": a word for reading.
    Description, as the server wrote it
    Get a single charge by id, including line items, totals, status, scheduled date, and customer/address. Recharge REST: GET /charges/{id}.

    Annotations the server declares

    • title: Get charge
    • readOnlyHint: true
  • recharge_get_customerGet a single customer by id, including contact details, Shopify customer id, and subscription/charge counts.Reads private dataNo findings

    Why it is in this group

    • The name "recharge_get_customer" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    Description, as the server wrote it
    Get a single customer by id, including contact details, Shopify customer id, and subscription/charge counts. Recharge REST: GET /customers/{id}.

    Annotations the server declares

    • title: Get customer
    • readOnlyHint: true
  • recharge_get_orderGet a single order by id, including line items, totals, status, and the charge/subscription it came from.No findings

    Why it is in this group

    • The name "recharge_get_order" says "get": a word for reading.
    Description, as the server wrote it
    Get a single order by id, including line items, totals, status, and the charge/subscription it came from. Recharge REST: GET /orders/{id}.

    Annotations the server declares

    • title: Get order
    • readOnlyHint: true
  • recharge_get_storeGet the Recharge store/shop info — name, domain, currency, timezone, and account settings.No findings

    Why it is in this group

    • The name "recharge_get_store" says "get": a word for reading.
    Description, as the server wrote it
    Get the Recharge store/shop info — name, domain, currency, timezone, and account settings. Recharge REST: GET /store.

    Annotations the server declares

    • title: Get store
    • readOnlyHint: true
  • recharge_get_subscriptionGet a single subscription by id, including product, quantity, price, charge interval, and next charge date.No findings

    Why it is in this group

    • The name "recharge_get_subscription" says "get": a word for reading.
    Description, as the server wrote it
    Get a single subscription by id, including product, quantity, price, charge interval, and next charge date. Recharge REST: GET /subscriptions/{id}.

    Annotations the server declares

    • title: Get subscription
    • readOnlyHint: true
  • recharge_list_addressesList customer addresses with optional filters (customer, ids, created/updated date ranges).No findings

    Why it is in this group

    • The name "recharge_list_addresses" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List addresses
    • readOnlyHint: true
  • recharge_list_chargesList charges with optional filters (customer, address, status, ids, purchase item, scheduled/created/updated date ranges) and sorting.No findings

    Why it is in this group

    • The name "recharge_list_charges" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List charges
    • readOnlyHint: true
  • recharge_list_customersList customers with optional filters (email, ids, created/updated date ranges) and sorting.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "recharge_list_customers" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List customers
    • readOnlyHint: true
  • recharge_list_onetimesList one-time (non-recurring) line items with optional filters (customer, address, created/updated date ranges).No findings

    Why it is in this group

    • The name "recharge_list_onetimes" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List one-times
    • readOnlyHint: true
  • recharge_list_ordersList orders with optional filters (customer, address, subscription, status, ids, created/updated/scheduled date ranges) and sorting.No findings

    Why it is in this group

    • The name "recharge_list_orders" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List orders
    • readOnlyHint: true
  • recharge_list_productsList Recharge products (subscription rules / discounts per product) with optional id filter.No findings

    Why it is in this group

    • The name "recharge_list_products" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List products
    • readOnlyHint: true
  • recharge_list_subscriptionsList subscriptions with optional filters (customer, address, status, ids, created/updated date ranges) and sorting.No findings

    Why it is in this group

    • The name "recharge_list_subscriptions" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List subscriptions
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://recharge.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://recharge.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://recharge.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://recharge.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.41.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__recharge__recharge_get_store",
      "mcp__recharge__recharge_list_subscriptions",
      "mcp__recharge__recharge_get_subscription",
      "mcp__recharge__recharge_list_customers",
      "mcp__recharge__recharge_get_customer",
      "mcp__recharge__recharge_list_charges",
      "mcp__recharge__recharge_get_charge",
      "mcp__recharge__recharge_list_orders",
      "mcp__recharge__recharge_get_order",
      "mcp__recharge__recharge_list_onetimes",
      "mcp__recharge__recharge_list_products",
      "mcp__recharge__recharge_list_addresses"
    ],
    "ask": [],
    "deny": [
      "mcp__recharge__recharge_skip_charge",
      "mcp__recharge__recharge_cancel_customer_subscription",
      "mcp__recharge__recharge_activate_subscription"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as recharge. Review it before you use it.

Capability tags behind 2 rules
  • mcp__recharge__recharge_list_customers private-data, untrusted-input
  • mcp__recharge__recharge_get_customer private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/recharge/verify?hash=1e938396447bdd4625aa6d44f93b1c9e1f523c90b1c562692020fecda82de1d2" | jq -e '.changed == false'

Pinned hash 1e938396447b, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/recharge/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/recharge
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/recharge.svg)](https://radar.anlyon.com/servers/io.usefulapi/recharge)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

Recharge MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Recharge MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Recharge MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: recharge_skip_charge, recharge_cancel_customer_subscription and recharge_activate_subscription.

Can the Recharge MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Recharge MCP by usefulapi have?

15 tools: 3 destructive, 12 read. recharge_skip_charge, recharge_cancel_customer_subscription, recharge_activate_subscription, recharge_get_store, recharge_list_subscriptions, recharge_get_subscription, recharge_list_customers, recharge_get_customer and 7 more.

Does the Recharge MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Recharge MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Recharge MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.