MCP server for minia2a.uk — discover and call 1,600+ x402 pay-per-call APIs with USDC payments.
Nothing to run from here
Awtomic MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
21
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read Awtomic subscriptions, customers and billing attempts; pause, skip, reschedule, cancel.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http awtomic-mcp-by-usefulapi https://awtomic.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# awtomic_list_subscriptions, awtomic_get_subscription, awtomic_list_customer_subscriptions and 18 more
Awtomic MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 598 servers
usefulapi598 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http awtomic-mcp-by-usefulapi https://awtomic.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Items per page, 1-100 (default 100). |
| cursor | string | no | Paging cursor: the next_cursor of the previous reply. Omit for the first page. |
| reverse | boolean | no | Read in reverse order. |
One subscription contract with its lines (products, quantities, prices). Needs the customer id and the subscription id. GET /customers/{customerId}/subscriptions/{subscriptionId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | no | Include the subscription lines (larger reply). Default false. |
| limit | integer | no | Items per page, 1-100 (default 100). |
| cursor | string | no | Paging cursor: the next_cursor of the previous reply. Omit for the first page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| limit | integer | no | Items per page, 1-100 (default 20). |
| cursor | string | no | Paging cursor: the next_cursor of the previous reply. Omit for the first page. |
| reverse | boolean | no | Read in reverse order (newest first or oldest first, as Awtomic defines it). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subscription_id | string | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
The Shopify order that started a subscription (id, name, creation date). GET /customers/{customerId}/subscriptions/{subscriptionId}/origin-order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
Fulfillment status and the fulfillment orders (status, fulfill-at date) of a subscription's origin order. GET /customers/{customerId}/subscriptions/{subscriptionId}/origin-order/fulfillments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
A customer: name, email, phone, orders count, amount spent, customer-since date, Awtomic overrides and the ids of their subscription contracts. GET /customers/{customerId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too. |
A customer's saved addresses and which one is the default. GET /customers/{customerId}/address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | Shopify customer id (the number in the Shopify admin customer URL, e.g. 6012345678901). A gid://shopify/Customer/… id is accepted too. |
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.
No parameter schema on file.
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| selling_plan_group_id | string | yes | Selling plan group id (gId or numeric id) from awtomic_list_selling_plan_groups. |
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/{sub
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
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}/sub
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| next_billing_date | string | no | 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. |
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}/subscr
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| skip_event_id | string | yes | The skipEventId from awtomic_skip_next_order. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| next_billing_date | string | yes | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| interval | string | yes | Interval unit. |
| interval_count | integer | yes | Number of interval units between orders (2 + WEEK = every 2 weeks). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| confirm_cancel | boolean | yes | Must be true: you confirm the user asked to cancel this shopper's subscription. |
| reason | string | no | Short reason code for Awtomic's analytics, e.g. too_expensive. |
| details | string | no | Free-text details of why the subscription is cancelled. |
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 th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| confirm_charge | boolean | yes | Must be true: you confirm the customer is charged now. |
| manual_retry | boolean | no | Retry a failed billing attempt. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | string | yes | 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 | yes | Shopify subscription contract id (the SubscriptionId of a subscription, e.g. 1234567890). A gid://shopify/SubscriptionContract/… id is accepted too. |
| confirm_send | boolean | yes | Must be true: you confirm the user asked to email this customer now. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Awtomic MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.15.2 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digesta3a372eef8e31a323bb583c70607124f0c1bd7cde92532521f326508ee61a07c
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| awtomic_list_subscriptions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_subscription | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_list_customer_subscriptions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_list_billing_attempts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_successful_billing_count | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_origin_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_origin_order_fulfillments | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_customer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_customer_addresses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_customer_payment_methods | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_list_selling_plan_groups | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_get_selling_plan_group | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| awtomic_pause_subscription | external-sink | external-sink: keyword "sms", declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_reactivate_subscription | external-sink | external-sink: keyword "sms", declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_skip_next_order | external-sink | external-sink: keyword "sms", declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_undo_skip | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_set_next_billing_date | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_update_frequency | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_cancel_customer_subscription | external-sink | external-sink: keyword "sms", declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_order_now | external-sink | external-sink: keyword "sms", declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| awtomic_send_payment_update_email | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digesta3a372eef8e31a32
Scanned2026-11-07
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.15.2.
1.15.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Awtomic MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.