Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Awtomic MCP by usefulapi

REMOTE · AWTOMIC.USEFULAPI.IO

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

62 Trust /100

Last scanned (48 minutes ago)

Scores higher than 46% of remote servers

Reachable. Last reached 25 Oct 2026.

Category E-commerce

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
Changelog

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 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.0.3 functional
  • 24 Oct 26 62

    First indexed and scored.

Diagnostics

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://awtomic.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 awtomic.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://awtomic.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://awtomic.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://awtomic.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://awtomic.usefulapi.io/mcp
Authorisation server https://awtomic.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://awtomic.usefulapi.io/mcp Redirected 302 https://usefulapi.io/awtomic/
http (plaintext) http://awtomic.usefulapi.io/mcp Inconclusive 302 http://awtomic.usefulapi.io/mcp
MCP tools · 21 exposed · ~3,392 tokens

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 →

Tool Tokens
awtomic_cancel_customer_subscription ~300

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.

NameTypeReqDescription
confirm_cancelbooleanyesMust be true: you confirm the user asked to cancel this shopper's subscription.
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
detailsstring–Free-text details of why the subscription is cancelled.
reasonstring–Short reason code for Awtomic's analytics, e.g. too_expensive.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_get_customer ~94

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

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_get_customer_addresses ~76

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

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_get_customer_payment_methods ~114

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.

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_get_origin_order ~129

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

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_get_origin_order_fulfillments ~143

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

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_get_selling_plan_group ~82

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}.

NameTypeReqDescription
selling_plan_group_idstringyesSelling plan group id (gId or numeric id) from awtomic_list_selling_plan_groups.

No output schema declared.

No examples provided.

awtomic_get_subscription ~132

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

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_get_successful_billing_count ~92

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.

NameTypeReqDescription
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_list_billing_attempts ~218

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.

NameTypeReqDescription
cursorstring–Paging cursor: the next_cursor of the previous reply. Omit for the first page.
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
limitinteger–Items per page, 1-100 (default 20).
reverseboolean–Read in reverse order (newest first or oldest first, as Awtomic defines it).
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_list_customer_subscriptions ~158

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.

NameTypeReqDescription
cursorstring–Paging cursor: the next_cursor of the previous reply. Omit for the first page.
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
expand_linesboolean–Include the subscription lines (larger reply). Default false.
limitinteger–Items per page, 1-100 (default 100).

No output schema declared.

No examples provided.

awtomic_list_selling_plan_groups ~61

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

awtomic_list_subscriptions ~113

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.

NameTypeReqDescription
cursorstring–Paging cursor: the next_cursor of the previous reply. Omit for the first page.
limitinteger–Items per page, 1-100 (default 100).
reverseboolean–Read in reverse order.

No output schema declared.

No examples provided.

awtomic_order_now ~267

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.

NameTypeReqDescription
confirm_chargebooleanyesMust be true: you confirm the customer is charged now.
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
manual_retryboolean–Retry a failed billing attempt.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_pause_subscription ~193

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.

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_reactivate_subscription ~241

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.

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
next_billing_datestring–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_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_send_payment_update_email ~194

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.

NameTypeReqDescription
confirm_sendbooleanyesMust be true: you confirm the user asked to email this customer now.
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_set_next_billing_date ~220

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.

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
next_billing_datestringyesA 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_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_skip_next_order ~201

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.

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_undo_skip ~188

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.

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
skip_event_idstringyesThe skipEventId from awtomic_skip_next_order.
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

awtomic_update_frequency ~176

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.

NameTypeReqDescription
customer_idstringyesShopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too.
intervalstringyesInterval unit.
interval_countintegeryesNumber of interval units between orders (2 + WEEK = every 2 weeks).
subscription_idstringyesShopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too.

No output schema declared.

No examples provided.

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.

remote · awtomic.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-awtomic 'https://awtomic.usefulapi.io/mcp'
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.