Seal Subscriptions MCP by usefulapi
REMOTE · SEAL-SUBSCRIPTIONS.USEFULAPI.IO
Manage Seal Subscriptions on Shopify: subscriptions, billing attempts, items, discounts, rules.
Available components
Last scanned (15 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 Usability84
- 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 3206 tokens (~118/item across 27 items; 27 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 28 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.2.0 → 1.2.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://seal-subscriptions.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 seal-subscriptions.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://seal-subscriptions.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://seal-subscriptions.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://seal-subscriptions.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://seal-subscriptions.usefulapi.io/mcp |
| Authorisation server | https://seal-subscriptions.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://seal-subscriptions.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/seal-subscriptions/ |
| http (plaintext) | http://seal-subscriptions.usefulapi.io/mcp | Inconclusive | 302 | http://seal-subscriptions.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 →
sealsubscriptions_add_items Add items to subscription ~86
WRITE: Add products to a subscription. Prices are in the subscription's currency and change what the customer pays on the next charge. An item with one_time=true is removed after the next renewal. PUT /subscription action=add_items.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_append_rule_product_variants Add products to subscription rule ~66
WRITE: Add products or variants to a subscription rule without touching the ones already linked. PUT /subscription-rule/append-product-variants.
| Name | Type | Req | Description |
|---|---|---|---|
| product_variants | array | yes | Products/variants to add. |
| rule_id | integer | yes | Subscription rule id. |
No output schema declared.
No examples provided.
sealsubscriptions_apply_discount_code Apply discount code ~92
WRITE: Apply a Shopify discount code to an auto-charging subscription (not to recurring-invoice subscriptions); it lowers what the customer pays on the next charges. PUT /subscription-discount-code action=apply.
| Name | Type | Req | Description |
|---|---|---|---|
| discount_code | string | yes | The discount code as the customer would type it. |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_cancel_customer_subscription Cancel subscription ~88
WRITE: Cancel a subscription now: all future charges and shipments stop and the customer may get Seal's cancellation email. It can be brought back with sealsubscriptions_reactivate_subscription. For a later cancellation use sealsubscriptions_schedule_cancellation. PUT /subscription action=cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_create_charge_now Charge subscription now ~124
WRITE: CHARGES THE CUSTOMER'S PAYMENT METHOD IMMEDIATELY for the next billing attempt of the subscription and creates a Shopify order; it does not wait for the scheduled date. Only call it when the user clearly asked for an immediate charge. With reset_schedule=true the later attempts are rebuilt from today. PUT /subscription-create-charge-now.
| Name | Type | Req | Description |
|---|---|---|---|
| reset_schedule | boolean | – | Rebuild the rest of the schedule after this charge (default false). |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_delete_billing_attempt Delete billing attempt ~112
WRITE: Delete a billing attempt that has not been processed. Seal keeps 65 days of attempts scheduled, so a deleted one is recreated within hours unless the schedule is moved first (see sealsubscriptions_reschedule_billing_attempt). DELETE /subscription-billing-attempt.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_attempt_id | integer | yes | Billing attempt id (billing_attempts[].id from sealsubscriptions_get_subscription). |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_edit_items Edit subscription items ~87
WRITE: Change existing items of a subscription: variant, quantity (> 0), price (>= 0), SKU, one-time flag, properties. Changes what the customer pays on the next charge. PUT /subscription action=edit_items.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_edit_subscription Edit subscription ~358
WRITE: Edit a subscription's schedule and details: delivery and billing interval (a billing interval longer than the delivery interval makes it prepaid), min/max number of payments, note attributes (an empty list removes them), delivery method and price, and the shipping address. Only the fields you pass change. To change items use the item tools. PUT /subscription action=edit.
| Name | Type | Req | Description |
|---|---|---|---|
| automatically_update_product_prices | boolean | – | When switching between prepaid and not prepaid, reprice the items. |
| billing_interval | string | – | Billing interval, e.g. "8 week". Longer than delivery_interval = prepaid. |
| billing_max_cycles | integer | – | Maximum number of payments (0 = unlimited). |
| billing_min_cycles | integer | – | Minimum number of payments. |
| delivery_interval | string | – | Delivery interval, e.g. "4 week" or "1 month". |
| delivery_method_code | string | – | – |
| delivery_method_presentment_title | string | – | – |
| delivery_method_title | string | – | – |
| delivery_price | number | – | – |
| note_attributes | array | – | Replaces all note attributes. |
| s_address1 | string | – | – |
| s_address2 | string | – | – |
| s_city | string | – | – |
| s_company | string | – | – |
| s_country | string | – | – |
| s_country_code | string | – | – |
| s_first_name | string | – | – |
| s_last_name | string | – | – |
| s_phone | string | – | – |
| s_province | string | – | – |
| s_province_code | string | – | – |
| s_zip | string | – | – |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_edit_subscription_rule Edit subscription rule ~148
WRITE: Edit a subscription rule: its name, the plan selector label (`options`, e.g. "Deliver every") and the products it applies to. product_variants REPLACES all products and variants linked to the rule: to add some without removing the others use sealsubscriptions_append_rule_product_variants. PUT /subscription-rule.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| options | string | – | Label for the plan selector, e.g. "Deliver every". |
| product_variants | array | – | The complete new list of products/variants (replaces the current list; an empty list unlinks every product). |
| rule_id | integer | yes | Subscription rule id. |
No output schema declared.
No examples provided.
sealsubscriptions_get_subscription Get subscription ~89
One subscription with everything Seal knows: customer, shipping and billing address, status, intervals, delivery method, items with discounts, billing attempts (with status and error messages), fulfillment orders, invoices, tags and the activity log. Private customer links are removed. GET /subscription?id=.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_get_subscription_rule Get subscription rule ~53
One subscription rule by id, with its products, variants and selling plans. GET /subscription-rule?id=.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | integer | yes | Subscription rule id (from sealsubscriptions_list_subscription_rules). |
No output schema declared.
No examples provided.
sealsubscriptions_list_subscription_rules List subscription rules ~76
List the subscription rules (plans) of the shop: name, payment type, the products and variants they apply to and their selling plans. GET /subscription-rules.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 50 per page. Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
sealsubscriptions_list_subscriptions List subscriptions ~171
List or search the shop's subscriptions (50 per page): status, customer, interval, total value, shipping address and card brand/last digits. Search by customer email, first or last name; filter by status; optionally include the items and the billing attempts of each. GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1); 50 per page. Pass the previous reply's next_page. |
| query | string | – | Search text: customer email, first name or last name. |
| status | string | – | Only subscriptions in this status (default: all). |
| with_billing_attempts | boolean | – | Include each subscription's billing attempts (default false). |
| with_items | boolean | – | Include each subscription's items (default false). |
No output schema declared.
No examples provided.
sealsubscriptions_list_subscriptions_by_billing_date List subscriptions by billing date ~168
Subscriptions that have at least one billing attempt scheduled between two UTC date-times: the way to see what will be charged tomorrow or this week. Each subscription carries a cursor; pass the last one's cursor as `cursor` to get the next page. GET /subscriptions-by-billing-date.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor of the last subscription of the previous page. |
| from_datetime | string | yes | Start of the period in UTC, yyyy-mm-ddThh:mm:ss, e.g. 2030-12-24T00:00:00. |
| to_datetime | string | yes | End of the period in UTC, yyyy-mm-ddThh:mm:ss, e.g. 2030-12-24T23:59:59. |
No output schema declared.
No examples provided.
sealsubscriptions_list_webhooks List webhooks ~33
List the webhooks registered for this shop through the API (topic and address). GET /webhooks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sealsubscriptions_pause_subscription Pause subscription ~64
WRITE: Pause an active subscription: no further charges or shipments until it is resumed. Undo with sealsubscriptions_resume_subscription. PUT /subscription action=pause.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_process_charge Process a specific charge ~105
WRITE: CHARGES THE CUSTOMER'S PAYMENT METHOD NOW for one specific billing attempt (for example a failed or upcoming one) and creates a Shopify order. Only call it when the user clearly asked for that charge. PUT /subscription-process-charge.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_attempt_id | integer | yes | Billing attempt id (billing_attempts[].id from sealsubscriptions_get_subscription). |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_reactivate_subscription Reactivate subscription ~76
WRITE: Reactivate a cancelled subscription (the effect is the same as resume; use this for cancelled ones). Charges restart on the schedule, so the customer may be billed. PUT /subscription action=reactivate.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_remove_discount_code Remove discount code ~103
WRITE: Remove a discount code from a subscription. Use the discount code id from the subscription's items[].discount_codes[].id (a uuid), not the code text. DELETE /subscription-discount-code.
| Name | Type | Req | Description |
|---|---|---|---|
| discount_code_id | string | yes | Discount code id (a uuid) from sealsubscriptions_get_subscription → items[].discount_codes[].id. |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_remove_items Remove items from subscription ~68
WRITE: Remove items from a subscription by item id. The customer stops receiving and paying for them. PUT /subscription action=remove_items.
| Name | Type | Req | Description |
|---|---|---|---|
| item_ids | array | yes | – |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_reschedule_billing_attempt Reschedule billing attempt ~183
WRITE: Move a billing attempt that has not been processed yet to another date and time. With reset_schedule=true the later attempts are rebuilt from the new date. PUT /subscription-billing-attempt action=reschedule.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_attempt_id | integer | yes | Billing attempt id (billing_attempts[].id from sealsubscriptions_get_subscription). |
| date | string | yes | New date, yyyy-mm-dd. |
| reset_schedule | boolean | – | Rebuild the rest of the schedule after this attempt (default false). |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
| time | string | yes | New time, hh:mm (24-hour), in the given timezone. |
| timezone | string | yes | UTC offset of the date and time, e.g. +00:00 or -04:00. |
No output schema declared.
No examples provided.
sealsubscriptions_reschedule_fulfillment_order Reschedule fulfillment order ~148
WRITE: Move a fulfillment order of a prepaid subscription to another date and time. PUT /subscription-fulfillment-order action=reschedule.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | New date, yyyy-mm-dd. |
| fulfillment_order_id | integer | yes | Fulfillment order id (fulfillment_orders[].id from sealsubscriptions_get_subscription). |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
| time | string | yes | New time, hh:mm (24-hour), in the given timezone. |
| timezone | string | yes | UTC offset of the date and time, e.g. +00:00 or -04:00. |
No output schema declared.
No examples provided.
sealsubscriptions_resume_subscription Resume subscription ~54
WRITE: Resume a paused subscription so charges and shipments continue on the schedule. PUT /subscription action=resume.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_schedule_cancellation Schedule subscription cancellation ~122
WRITE: Schedule the cancellation of a subscription for a future date and time (it stays active until then). PUT /subscription-schedule-cancellation.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Cancellation date, yyyy-mm-dd. |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
| time | string | yes | Cancellation time, hh:mm (24-hour), in the given timezone. |
| timezone | string | yes | UTC offset of the date and time, e.g. +00:00 or -04:00. |
No output schema declared.
No examples provided.
sealsubscriptions_send_payment_method_update_email Email customer to update payment method ~86
WRITE: SENDS AN EMAIL TO THE CUSTOMER of the subscription with a link to update their payment method (for example after failed charges). Only call it when the user clearly asked to contact the customer. PUT /subscription action=send_payment_method_update_email.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_skip_billing_attempt Skip billing attempt ~97
WRITE: Skip one upcoming billing attempt so the customer is not charged for that cycle. Undo with sealsubscriptions_unskip_billing_attempt. PUT /subscription-billing-attempt action=skip.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_attempt_id | integer | yes | Billing attempt id (billing_attempts[].id from sealsubscriptions_get_subscription). |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
sealsubscriptions_unskip_billing_attempt Unskip billing attempt ~89
WRITE: Bring back a skipped billing attempt, so it is charged on its date again. PUT /subscription-billing-attempt action=unskip.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_attempt_id | integer | yes | Billing attempt id (billing_attempts[].id from sealsubscriptions_get_subscription). |
| subscription_id | integer | yes | The subscription's `id` (not its `internal_id`). |
No output schema declared.
No examples provided.
How do I install the Seal Subscriptions MCP by usefulapi server?
Seal Subscriptions MCP by usefulapi is a hosted endpoint at https://seal-subscriptions.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 · seal-subscriptions.usefulapi.io
claude mcp add --transport http io-usefulapi-seal-subscriptions 'https://seal-subscriptions.usefulapi.io/mcp'
What is the Seal Subscriptions MCP by usefulapi server?
Seal Subscriptions MCP by usefulapi is listed in the public MCP registry as io.usefulapi/seal-subscriptions. Manage Seal Subscriptions on Shopify: subscriptions, billing attempts, items, discounts, rules. This page covers its hosted endpoint (https://seal-subscriptions.usefulapi.io/mcp).
Is the Seal Subscriptions MCP by usefulapi server safe to use?
Seal Subscriptions 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 Seal Subscriptions MCP by usefulapi server expose?
Seal Subscriptions MCP by usefulapi exposes 27 tools: sealsubscriptions_list_subscriptions, sealsubscriptions_list_subscriptions_by_billing_date, sealsubscriptions_get_subscription, sealsubscriptions_list_subscription_rules, sealsubscriptions_get_subscription_rule, and 22 more. Their descriptions and schemas cost roughly 2,946 tokens of context every time the server is loaded.
Does the Seal Subscriptions MCP by usefulapi server require authentication?
Yes. Seal Subscriptions 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 Seal Subscriptions MCP by usefulapi server still maintained?
Seal Subscriptions 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.