Smartrr MCP by usefulapi
REMOTE · SMARTRR.USEFULAPI.IO
Manage Smartrr subscriptions on Shopify: customers, orders, bills; pause, resume, cancel.
Available components
Last scanned (13 minutes ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 Oct 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 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 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
- 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 & 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 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
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.
- 25 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.3 functional
- 24 Oct 26 62
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 25 Oct 2026 · Probed https://smartrr.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 smartrr.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://smartrr.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://smartrr.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://smartrr.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://smartrr.usefulapi.io/mcp |
| Authorisation server | https://smartrr.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://smartrr.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/smartrr/ |
| http (plaintext) | http://smartrr.usefulapi.io/mcp | Inconclusive | 302 | http://smartrr.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 →
smartrr_cancel_customer_subscription Cancel a customer's subscription ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Smartrr customer id (`custRel.id`). |
| reason_id | string | yes | Cancellation reason id from smartrr_list_cancellation_reasons. |
| subscription_id | string | yes | Smartrr subscription id (`id`, a UUID). |
No output schema declared.
No examples provided.
smartrr_get_analytics Get subscription analytics ~61
Active subscription count and active subscriber count for each day in a date range. GET /vendor/analytics-simple.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last day of the range. |
| start_date | string | yes | First day of the range. |
No output schema declared.
No examples provided.
smartrr_get_bill_history Get bill history ~66
The audit trail of one bill: every status change, retry and error. GET /vendor/bill/{billId}/history.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | integer | yes | Smartrr bill id (numeric `id` in smartrr_list_bills). |
No output schema declared.
No examples provided.
smartrr_get_order Get order ~75
One order by its Shopify order id (the `shopifyId` field in smartrr_list_orders, passed as shown). GET /vendor/orders/{shopifyId}.
| Name | Type | Req | Description |
|---|---|---|---|
| shopify_order_id | string | yes | The order's Shopify id (`shopifyId` in smartrr_list_orders). |
No output schema declared.
No examples provided.
smartrr_get_subscription Get subscription ~110
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| shopify_subscription_id | string | yes | The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions). |
No output schema declared.
No examples provided.
smartrr_get_subscription_bills List a subscription's bills ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions). |
| sort | string | – | Sort by creation date (default: Smartrr's own order). |
No output schema declared.
No examples provided.
smartrr_get_subscription_events Get subscription history ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| shopify_subscription_id | string | yes | The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions). |
No output schema declared.
No examples provided.
smartrr_get_subscription_orders List a subscription's orders ~133
Orders generated by one subscription, by its Shopify subscription id. GET /vendor/purchase-state/{shopifySubscriptionId}/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The subscription's Shopify id (`shopifyId` in smartrr_list_subscriptions). |
| sort | string | – | Sort by creation date (default: Smartrr's own order). |
No output schema declared.
No examples provided.
smartrr_list_bills List bills ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
smartrr_list_cancellation_reasons List cancellation reasons ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smartrr_list_customer_subscriptions List a customer's subscriptions ~138
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | 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. |
No output schema declared.
No examples provided.
smartrr_list_customers List customers ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
smartrr_list_orders List orders ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
smartrr_list_selling_plan_groups List subscription programs ~48
The store's subscription programs (selling plan groups) and their plans: name, options, delivery and billing frequency, discounts. GET /vendor/selling-plan-group.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
smartrr_list_subscriptions List subscriptions ~261
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
smartrr_pause_subscription Pause a subscription ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Smartrr customer id (`custRel.id`). |
| subscription_id | string | yes | Smartrr subscription id (`id`, a UUID). |
| unpause_date | string | yes | When the subscription resumes. |
No output schema declared.
No examples provided.
smartrr_resume_subscription Resume a subscription ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Smartrr customer id (`custRel.id`). |
| next_billing_date | string | yes | The next billing date after reactivation. |
| subscription_id | string | yes | Smartrr subscription id (`id`, a UUID). |
No output schema declared.
No examples provided.
smartrr_retry_bill Retry a failed bill ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_id | integer | yes | Smartrr bill id (numeric `id` in smartrr_list_bills). |
| confirm | boolean | yes | Must be true: confirms the customer's saved payment method should be charged now. |
No output schema declared.
No examples provided.
smartrr_set_next_billing_date Set next billing date ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Smartrr customer id (`custRel.id`). |
| date | string | yes | The new next billing date. |
| subscription_id | string | yes | Smartrr subscription id (`id`, a UUID). |
No output schema declared.
No examples provided.
smartrr_skip_order Skip a subscription order ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Smartrr customer id (`custRel.id`). |
| date | string | – | The scheduled order date to skip (default: the next order). |
| subscription_id | string | yes | Smartrr subscription id (`id`, a UUID). |
No output schema declared.
No examples provided.
smartrr_unskip_order Unskip a subscription order ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | Smartrr customer id (`custRel.id`). |
| date | string | – | The skipped order date to restore (default: the earliest skipped one). |
| subscription_id | string | yes | Smartrr subscription id (`id`, a UUID). |
No output schema declared.
No examples provided.
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.
remote · smartrr.usefulapi.io
claude mcp add --transport http io-usefulapi-smartrr 'https://smartrr.usefulapi.io/mcp'
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.