# Smartrr MCP by usefulapi (remote · smartrr.usefulapi.io)

Manage Smartrr subscriptions on Shopify: customers, orders, bills; pause, resume, cancel.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `smartrr.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-smartrr/smartrr.md), [page](https://verifymcp.io/servers/io-usefulapi-smartrr/smartrr)

## Channel facts

- Endpoint: `https://smartrr.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2953 tokens (~140/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Smartrr MCP by usefulapi server?

Smartrr MCP by usefulapi is a hosted endpoint at https://smartrr.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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-smartrr 'https://smartrr.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-smartrr": {
      "url": "https://smartrr.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-smartrr": {
      "type": "http",
      "url": "https://smartrr.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-smartrr]
url = "https://smartrr.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-smartrr": {
      "type": "remote",
      "url": "https://smartrr.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-smartrr --url 'https://smartrr.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-smartrr:
    url: "https://smartrr.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-smartrr": {
      "Transport": "http",
      "Url": "https://smartrr.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-smartrr -t streamable-http -u 'https://smartrr.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-smartrr": {
      "type": "http",
      "url": "https://smartrr.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.1.3

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (21)

### `smartrr_list_subscriptions` (~261 tokens)

List subscriptions

List customer subscriptions (Smartrr 'purchase states') with status, next billing date, selling plan, line items, shipping address, discounts and the customer (id, email, name). Filter by status, next billing date or creation date. The ids you need for the other tools: `id` (subscription id), `custRel.id` (customer id) and `shopifyId` (Shopify subscription id). GET /vendor/purchase-state.

Input parameters:

- `created_after` (string): Only subscriptions created on or after this date.
- `created_before` (string): Only subscriptions created on or before this date.
- `next_billing_after` (string): Only subscriptions whose next billing date is on or after this date.
- `next_billing_before` (string): Only subscriptions whose next billing date is on or before this date.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort by creation date (default: Smartrr's own order).
- `status` (string): Only subscriptions in this status.

### `smartrr_get_subscription` (~110 tokens)

Get subscription

One subscription by its Shopify subscription id (the `shopifyId` field from smartrr_list_subscriptions, passed exactly as shown): status, schedule, next billing date, line items, discounts, shipping address, customer and payment method (brand, last digits and expiry only). GET /vendor/purchase-state/{shopifySubscriptionId}.

Input parameters:

- `shopify_subscription_id` (string, required): The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions).

### `smartrr_list_customer_subscriptions` (~138 tokens)

List a customer's subscriptions

List the subscriptions of one customer, by Smartrr customer id (`custRel.id` from smartrr_list_subscriptions, or `id` from smartrr_list_customers). GET /vendor/customer/{customerRelationshipId}/purchase-state/.

Input parameters:

- `customer_id` (string, required): Smartrr customer id.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Results per page, 1-100 (default 25).
- `status` (string): Only subscriptions in this status.

### `smartrr_get_subscription_events` (~91 tokens)

Get subscription history

The 250 most recent events on a subscription (pause, skip, cancel, activate, billing attempts and failures, line-item and address changes, discounts) with who did it. GET /vendor/purchase-state/{shopifySubscriptionId}/events.

Input parameters:

- `shopify_subscription_id` (string, required): The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions).

### `smartrr_get_subscription_orders` (~133 tokens)

List a subscription's orders

Orders generated by one subscription, by its Shopify subscription id. GET /vendor/purchase-state/{shopifySubscriptionId}/orders.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Results per page, 1-100 (default 25).
- `shopify_subscription_id` (string, required): The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions).
- `sort` (string): Sort by creation date (default: Smartrr's own order).

### `smartrr_get_subscription_bills` (~156 tokens)

List a subscription's bills

Billing attempts of one subscription (amount, status pending/processing/succeeded/failed/canceled, billing date, retry count, error), by its Shopify subscription id. GET /vendor/purchase-state/{shopifySubscriptionId}/bills.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Results per page, 1-100 (default 25).
- `shopify_subscription_id` (string, required): The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions).
- `sort` (string): Sort by creation date (default: Smartrr's own order).

### `smartrr_list_customers` (~154 tokens)

List customers

List Smartrr customers (subscribers) with email, name, phone, order count, total spent and custom attributes. Search by email fragment or filter by Shopify customer id. GET /vendor/customer-relationship.

Input parameters:

- `email` (string): Customers whose email contains this text.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Results per page, 1-100 (default 25).
- `shopify_customer_id` (string): Only the customer with this Shopify customer id.
- `sort` (string): Sort by creation date (default: Smartrr's own order).

### `smartrr_list_orders` (~185 tokens)

List orders

List orders Smartrr has synced from Shopify (subscription and one-time) with totals, status, financial and fulfillment status, tracking, items and customer. Filter by processed date or order label (e.g. #1001). GET /vendor/order.

Input parameters:

- `order_label` (string): Orders whose Shopify order label contains this text, e.g. #1001.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Results per page, 1-100 (default 25).
- `processed_after` (string): Only orders processed on or after this date.
- `processed_before` (string): Only orders processed on or before this date.
- `sort` (string): Sort by creation date (default: Smartrr's own order).

### `smartrr_get_order` (~75 tokens)

Get order

One order by its Shopify order id (the `shopifyId` field in smartrr_list_orders, passed as shown). GET /vendor/orders/{shopifyId}.

Input parameters:

- `shopify_order_id` (string, required): The order's Shopify id (`shopifyId` in smartrr_list_orders).

### `smartrr_list_bills` (~212 tokens)

List bills

List billing attempts across all subscriptions with amount, status (pending, processing, succeeded, failed, canceled), billing date, retry count, error and the subscription and customer. Filter by billing date; `status` filters the returned page only (use page_size 100 and next_page to cover more). Bill ids are numbers. GET /vendor/bill.

Input parameters:

- `billing_after` (string): Only bills with a billing date on or after this date.
- `billing_before` (string): Only bills with a billing date on or before this date.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `page_size` (integer): Results per page, 1-100 (default 25).
- `sort` (string): Sort by creation date (default: Smartrr's own order).
- `status` (string): Keep only bills in this status (applied to the fetched page, not server-side).

### `smartrr_get_bill_history` (~66 tokens)

Get bill history

The audit trail of one bill: every status change, retry and error. GET /vendor/bill/{billId}/history.

Input parameters:

- `bill_id` (integer, required): Smartrr bill id (numeric `id` in smartrr_list_bills).

### `smartrr_list_selling_plan_groups` (~48 tokens)

List subscription programs

The store's subscription programs (selling plan groups) and their plans: name, options, delivery and billing frequency, discounts. GET /vendor/selling-plan-group.

### `smartrr_list_cancellation_reasons` (~57 tokens)

List cancellation reasons

The cancellation reasons configured in Smartrr (id, type, text, action, retention discount). Use an `id` as reason_id when cancelling a subscription. GET /vendor/cancellation-reasons.

### `smartrr_get_analytics` (~61 tokens)

Get subscription analytics

Active subscription count and active subscriber count for each day in a date range. GET /vendor/analytics-simple.

Input parameters:

- `end_date` (string, required): Last day of the range.
- `start_date` (string, required): First day of the range.

### `smartrr_pause_subscription` (~133 tokens)

Pause a subscription

WRITE: pause a customer's subscription until a date: no orders or charges are created while it is paused, then it resumes on that date. Reverse it with smartrr_resume_subscription. Takes the customer id and subscription id from smartrr_list_subscriptions. PUT /vendor/customer/{customerId}/purchase-state/{subscriptionId}/pause.

Input parameters:

- `customer_id` (string, required): Smartrr customer id (`custRel.id`).
- `subscription_id` (string, required): Smartrr subscription id (`id`, a UUID).
- `unpause_date` (string, required): When the subscription resumes.

### `smartrr_resume_subscription` (~120 tokens)

Resume a subscription

WRITE: reactivate a paused or cancelled subscription; the customer will be billed on next_billing_date and every cycle after. Customer-facing: it restarts charges to the customer's card. PUT /vendor/customer/{customerId}/purchase-state/{subscriptionId}/activate.

Input parameters:

- `customer_id` (string, required): Smartrr customer id (`custRel.id`).
- `next_billing_date` (string, required): The next billing date after reactivation.
- `subscription_id` (string, required): Smartrr subscription id (`id`, a UUID).

### `smartrr_cancel_customer_subscription` (~170 tokens)

Cancel a customer's subscription

WRITE, DESTRUCTIVE: cancel a customer's subscription in the merchant's store (this is the customer's Smartrr subscription, not your usefulapi plan). It stops all future orders and charges; the reason may trigger Smartrr's configured cancellation emails or actions. It can be undone only with smartrr_resume_subscription. Get reason_id from smartrr_list_cancellation_reasons. PUT /vendor/customer/{customerId}/purchase-state/{subscriptionId}/cancel.

Input parameters:

- `customer_id` (string, required): Smartrr customer id (`custRel.id`).
- `reason_id` (string, required): Cancellation reason id from smartrr_list_cancellation_reasons.
- `subscription_id` (string, required): Smartrr subscription id (`id`, a UUID).

### `smartrr_skip_order` (~138 tokens)

Skip a subscription order

WRITE: skip one scheduled order of a subscription (no order and no charge for that cycle; the schedule moves on). `date` is the scheduled order date to skip; omit it to skip the next one. Reverse with smartrr_unskip_order. PUT /vendor/customer/{customerId}/purchase-state/{subscriptionId}/skip.

Input parameters:

- `customer_id` (string, required): Smartrr customer id (`custRel.id`).
- `date` (string): The scheduled order date to skip (default: the next order).
- `subscription_id` (string, required): Smartrr subscription id (`id`, a UUID).

### `smartrr_unskip_order` (~124 tokens)

Unskip a subscription order

WRITE: restore a previously skipped order of a subscription, so it is billed and shipped again. `date` is the skipped order date; omit it to restore the earliest skip. PUT /vendor/customer/{customerId}/purchase-state/{subscriptionId}/unskip.

Input parameters:

- `customer_id` (string, required): Smartrr customer id (`custRel.id`).
- `date` (string): The skipped order date to restore (default: the earliest skipped one).
- `subscription_id` (string, required): Smartrr subscription id (`id`, a UUID).

### `smartrr_set_next_billing_date` (~113 tokens)

Set next billing date

WRITE: change the date on which a subscription is next billed and its order created. Customer-facing: the customer is charged on the new date. PUT /vendor/customer/{customerId}/purchase-state/{subscriptionId}/next-billing-date.

Input parameters:

- `customer_id` (string, required): Smartrr customer id (`custRel.id`).
- `date` (string, required): The new next billing date.
- `subscription_id` (string, required): Smartrr subscription id (`id`, a UUID).

### `smartrr_retry_bill` (~140 tokens)

Retry a failed bill

WRITE, CHARGES THE CUSTOMER: retry a billing attempt now. If it succeeds the customer's saved payment method is charged for the bill amount and the order is created. Check the bill with smartrr_list_bills first; do not retry a succeeded bill. Not idempotent: each call can charge again. Requires confirm=true. POST /vendor/bill/{billId}/retry.

Input parameters:

- `bill_id` (integer, required): Smartrr bill id (numeric `id` in smartrr_list_bills).
- `confirm` (boolean, required): Must be true: confirms the customer's saved payment method should be charged now.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-smartrr/smartrr#diagnostics

## Score history

- 2026-10-25: 63
- 2026-10-24: 62

## Common questions

### What is the Smartrr MCP by usefulapi server?

Smartrr MCP by usefulapi is listed in the public MCP registry as io.usefulapi/smartrr. Manage Smartrr subscriptions on Shopify: customers, orders, bills; pause, resume, cancel. This page covers its hosted endpoint (https://smartrr.usefulapi.io/mcp).

### Is the Smartrr MCP by usefulapi server safe to use?

Smartrr 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 Smartrr MCP by usefulapi server expose?

Smartrr MCP by usefulapi exposes 21 tools: smartrr_list_subscriptions, smartrr_get_subscription, smartrr_list_customer_subscriptions, smartrr_get_subscription_events, smartrr_get_subscription_orders, and 16 more. Their descriptions and schemas cost roughly 2,685 tokens of context every time the server is loaded.

### Does the Smartrr MCP by usefulapi server require authentication?

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

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

## Links

- Remote endpoint: https://smartrr.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/smartrr/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-smartrr/smartrr.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-smartrr/smartrr.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-smartrr/smartrr