# Awtomic MCP by usefulapi (remote · awtomic.usefulapi.io)

Read Awtomic subscriptions, customers and billing attempts; pause, skip, reschedule, cancel.

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

## Components

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

## Channel facts

- Endpoint: `https://awtomic.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3668 tokens (~174/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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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 Awtomic MCP by usefulapi server?

Awtomic MCP by usefulapi is a hosted endpoint at https://awtomic.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-awtomic 'https://awtomic.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-awtomic": {
      "type": "http",
      "url": "https://awtomic.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 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.3

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

First indexed and scored.

## MCP tools (21)

### `awtomic_list_subscriptions` (~113 tokens)

List shop subscriptions

List the shop's subscription contracts (id, status, next billing date and more), 100 per page by default. Use reverse to read the newest first. Pass next_cursor back as cursor for the next page. GET /subscriptions.

Input parameters:

- `cursor` (string): Paging cursor: the next_cursor of the previous reply. Omit for the first page.
- `limit` (integer): Items per page, 1-100 (default 100).
- `reverse` (boolean): Read in reverse order.

### `awtomic_get_subscription` (~132 tokens)

Get subscription

One subscription contract with its lines (products, quantities, prices). Needs the customer id and the subscription id. GET /customers/{customerId}/subscriptions/{subscriptionId}.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_list_customer_subscriptions` (~158 tokens)

List a customer's subscriptions

List one customer's subscriptions (id, status, next billing date). Set expand_lines to include each subscription's lines; that makes the reply much larger. GET /customers/{customerId}/subscriptions.

Input parameters:

- `cursor` (string): Paging cursor: the next_cursor of the previous reply. Omit for the first page.
- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `expand_lines` (boolean): Include the subscription lines (larger reply). Default false.
- `limit` (integer): Items per page, 1-100 (default 100).

### `awtomic_list_billing_attempts` (~218 tokens)

List billing attempts

A subscription's billing attempts: status (SUCCESS or FAILURE), error code and message, amount, currency and dates. Use it to see why a renewal failed. GET /customers/{customerId}/subscriptions/{subscriptionId}/billing-attempts.

Input parameters:

- `cursor` (string): Paging cursor: the next_cursor of the previous reply. Omit for the first page.
- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `limit` (integer): Items per page, 1-100 (default 20).
- `reverse` (boolean): Read in reverse order (newest first or oldest first, as Awtomic defines it).
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_get_successful_billing_count` (~92 tokens)

Get successful billing count

How many billing attempts of a subscription succeeded, including those made before a migration from another subscription app. GET /subscriptions/{subscriptionId}/total-successful-billing-count.

Input parameters:

- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_get_origin_order` (~129 tokens)

Get subscription origin order

The Shopify order that started a subscription (id, name, creation date). GET /customers/{customerId}/subscriptions/{subscriptionId}/origin-order.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_get_origin_order_fulfillments` (~143 tokens)

Get origin order fulfillments

Fulfillment status and the fulfillment orders (status, fulfill-at date) of a subscription's origin order. GET /customers/{customerId}/subscriptions/{subscriptionId}/origin-order/fulfillments.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_get_customer` (~94 tokens)

Get customer

A customer: name, email, phone, orders count, amount spent, customer-since date, Awtomic overrides and the ids of their subscription contracts. GET /customers/{customerId}.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.

### `awtomic_get_customer_addresses` (~76 tokens)

Get customer addresses

A customer's saved addresses and which one is the default. GET /customers/{customerId}/address.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.

### `awtomic_get_customer_payment_methods` (~114 tokens)

Get customer payment methods

A customer's payment methods on file: type (card, Shop Pay, PayPal), card brand, last digits, expiry and whether it was revoked. Never the full card number. Use it to spot expired cards before a renewal. GET /customers/{customerId}/payment-methods.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.

### `awtomic_list_selling_plan_groups` (~61 tokens)

List selling plan groups

The shop's selling plan groups (subscription plans): name, summary, options, position and whether it is a prepaid plan. Use the ids with awtomic_get_selling_plan_group. GET /shops/selling-plan-groups.

### `awtomic_get_selling_plan_group` (~82 tokens)

Get selling plan group

One selling plan group with its selling plans (name, prepaid orders, gift support) and the products it applies to. GET /shops/selling-plan-groups/{sellingPlanGroupId}.

Input parameters:

- `selling_plan_group_id` (string, required): Selling plan group id (gId or numeric id) from awtomic_list_selling_plan_groups.

### `awtomic_pause_subscription` (~193 tokens)

Pause subscription

WRITE: pause a subscription so it is not billed or shipped until it is reactivated (awtomic_reactivate_subscription). A subscription in dunning is taken out of dunning. Awtomic runs the shop's own automations for this event, so the customer may get an email or SMS and webhooks may fire. Awtomic pauses it on its side even if Shopify rejects the pause. POST /customers/{customerId}/subscriptions/{subscriptionId}/pause.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_reactivate_subscription` (~241 tokens)

Reactivate subscription

WRITE: reactivate a paused or cancelled subscription, so billing resumes. A cancelled prepaid subscription cannot be reactivated. Without next_billing_date Awtomic works it out from the subscription's interval; the customer is charged on that date. Awtomic runs the shop's own automations for this event, so the customer may get an email or SMS and webhooks may fire. POST /customers/{customerId}/subscriptions/{subscriptionId}/reactivate.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `next_billing_date` (string): A date yyyy-mm-dd (read in the shop's time zone, shop renewal billing time applies) or an ISO 8601 date-time with a timezone. Must be later than the end of today.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_skip_next_order` (~201 tokens)

Skip next order

WRITE: skip a subscription's next order. The subscription must be active; Awtomic moves the next billing date by one interval (each call skips one more order, so do not repeat it). The reply has skipEventId: pass it to awtomic_undo_skip to undo. Awtomic runs the shop's own automations for this event, so the customer may get an email or SMS and webhooks may fire. POST /customers/{customerId}/subscriptions/{subscriptionId}/skip.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_undo_skip` (~188 tokens)

Undo skip

WRITE: undo a skipped order, restoring the billing date from before the skip. Needs the skipEventId returned by awtomic_skip_next_order; Awtomic refuses (409) when the skip can no longer be undone. POST /customers/{customerId}/subscriptions/{subscriptionId}/next-billing-date with eventType UNDO_SKIP.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `skip_event_id` (string, required): The skipEventId from awtomic_skip_next_order.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_set_next_billing_date` (~220 tokens)

Set next billing date

WRITE: change when a subscription is next billed. The date must be later than the end of today. A paused subscription is reactivated by this call, and one in dunning is taken out of dunning. The customer is charged on the new date. POST /customers/{customerId}/subscriptions/{subscriptionId}/next-billing-date.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `next_billing_date` (string, required): A date yyyy-mm-dd (read in the shop's time zone, shop renewal billing time applies) or an ISO 8601 date-time with a timezone. Must be later than the end of today.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_update_frequency` (~176 tokens)

Update subscription frequency

WRITE: change how often a subscription is billed and delivered, for example every 2 WEEK or every 1 MONTH. Changes every future order of that subscription. POST /customers/{customerId}/subscriptions/{subscriptionId}/frequency.

Input parameters:

- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `interval` (string, required): Interval unit.
- `interval_count` (integer, required): Number of interval units between orders (2 + WEEK = every 2 weeks).
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_cancel_customer_subscription` (~300 tokens)

Cancel a customer's subscription

WRITE: cancel one shopper's subscription contract in Awtomic. Billing and shipping stop; a cancelled non-prepaid subscription can be brought back with awtomic_reactivate_subscription. This cancels the shop's customer subscription, not your usefulapi plan. Awtomic runs the shop's own automations for this event, so the customer may get an email or SMS and webhooks may fire. Awtomic cancels it on its side even if Shopify rejects the cancel. Only use it when the user explicitly asks to cancel this subscription, and confirm_cancel must be true. A cancelled prepaid subscription cannot be reactivated. POST /customers/{customerId}/subscriptions/{subscriptionId}/cancel.

Input parameters:

- `confirm_cancel` (boolean, required): Must be true: you confirm the user asked to cancel this shopper's subscription.
- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `details` (string): Free-text details of why the subscription is cancelled.
- `reason` (string): Short reason code for Awtomic's analytics, e.g. too_expensive.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_order_now` (~267 tokens)

Charge and order now

WRITE: bill the customer's saved payment method and create the subscription's next order immediately, instead of waiting for the billing date. THIS CHARGES THE CUSTOMER. Awtomic refuses (409 ORDER_RECENTLY_PLACED) if the latest billing attempt is pending or succeeded under 10 minutes ago. Set manual_retry only to retry a failed billing attempt. Only use it when the user explicitly asks to place this order now, and confirm_charge must be true. Awtomic runs the shop's own automations for this event, so the customer may get an email or SMS and webhooks may fire. POST /customers/{customerId}/subscriptions/{subscriptionId}/order-now.

Input parameters:

- `confirm_charge` (boolean, required): Must be true: you confirm the customer is charged now.
- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `manual_retry` (boolean): Retry a failed billing attempt.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

### `awtomic_send_payment_update_email` (~194 tokens)

Email customer to update payment method

WRITE: make Shopify email the customer a link to update their payment method for this subscription. This SENDS AN EMAIL TO THE CUSTOMER each time it is called. Use it for failed payments or expired cards, only when the user asks, and confirm_send must be true. POST /customers/{customerId}/subscriptions/{subscriptionId}/send-customer-payment-email.

Input parameters:

- `confirm_send` (boolean, required): Must be true: you confirm the user asked to email this customer now.
- `customer_id` (string, required): Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
- `subscription_id` (string, required): Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

## Diagnostics

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

## Score history

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

## Common questions

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

Awtomic MCP by usefulapi is listed in the public MCP registry as io.usefulapi/awtomic. Read Awtomic subscriptions, customers and billing attempts; pause, skip, reschedule, cancel. This page covers its hosted endpoint (https://awtomic.usefulapi.io/mcp).

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

Awtomic MCP by usefulapi scores 62 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 Awtomic MCP by usefulapi server expose?

Awtomic MCP by usefulapi exposes 21 tools: awtomic_list_subscriptions, awtomic_get_subscription, awtomic_list_customer_subscriptions, awtomic_list_billing_attempts, awtomic_get_successful_billing_count, and 16 more. Their descriptions and schemas cost roughly 3,392 tokens of context every time the server is loaded.

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

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

Awtomic 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://awtomic.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/awtomic/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-awtomic/awtomic.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-awtomic/awtomic.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-awtomic/awtomic