Swell MCP by usefulapi
REMOTE · SWELL.USEFULAPI.IO
Manage your Swell headless-commerce store — products, orders, customers, and subscriptions.
Available components
Last scanned (5 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_subscriptions_invoices_and_coupons” functional
- New prompt “count_abandoned_carts_and_look_at_customers” functional
- New prompt “create_or_update_products_and_update_orders” functional
- New prompt “find_products_that_are_inactive_or_hidden” functional
- New prompt “review_orders_and_revenue_for_a_period” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.1 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.1 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
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 5 Nov 2026 · Probed https://swell.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 swell.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://swell.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/swell/ |
| http (plaintext) | http://swell.usefulapi.io/mcp | Inconclusive | 302 | http://swell.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 →
swell_create_product Create a product ~170
MUTATES LIVE STORE DATA. Create a new product in the store. Provide the common fields directly (name is required); anything else goes in `fields`, which is merged into the request body. Swell backend REST API: POST /products.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Whether the product is active/visible. |
| description | string | – | Product description. |
| fields | object | – | Any additional product fields, merged into the request body (e.g. attributes, options, images). |
| name | string | yes | Product name (required). |
| price | number | – | Product price. |
| sku | string | – | Stock-keeping unit. |
| stock_level | number | – | Available stock quantity. |
| type | string | – | Product type, e.g. "standard", "subscription", "digital". |
No output schema declared.
No examples provided.
swell_get_customer Get a customer ~91
Fetch a single customer (Swell `accounts` model) by id. Supports `expand` and `fields`. Swell backend REST API: GET /accounts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "orders,subscriptions". |
| fields | string | – | Comma-separated fields to return. |
| id | string | yes | Customer (account) id. |
No output schema declared.
No examples provided.
swell_get_order Get an order ~89
Fetch a single order by its record id or its order number. Supports `expand` and `fields`. Swell backend REST API: GET /orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "items,account". |
| fields | string | – | Comma-separated fields to return. |
| id | string | yes | Order id or order number. |
No output schema declared.
No examples provided.
swell_get_product Get a product ~95
Fetch a single product by its record id or its slug. Supports `expand` and `fields`. Swell backend REST API: GET /products/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| fields | string | – | Comma-separated fields to return, e.g. "name,price". |
| id | string | yes | Product id or slug. |
No output schema declared.
No examples provided.
swell_get_subscription Get a subscription ~63
Fetch a single subscription by id. Supports `expand`. Swell backend REST API: GET /subscriptions/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "account,product". |
| id | string | yes | Subscription id. |
No output schema declared.
No examples provided.
swell_list_carts List carts ~150
List shopping carts (including abandoned carts), with filtering, sorting, and expansion. Swell backend REST API: GET /carts.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_list_categories List categories ~162
List product categories, with filtering, sorting, search, and expansion. Swell backend REST API: GET /categories.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| search | string | – | Free-text search across the model's searchable fields. |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_list_coupons List coupons ~122
List discount coupons, with filtering and sorting. Swell backend REST API: GET /coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_list_customers List customers ~170
List customers. In Swell, customers are the `accounts` model — this queries GET /accounts, with filtering, sorting, search, and expansion.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| search | string | – | Free-text search across the model's searchable fields. |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_list_invoices List invoices ~149
List invoices (typically subscription invoices), with filtering, sorting, and expansion. Swell backend REST API: GET /invoices.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_list_orders List orders ~164
List orders, with MongoDB-style filtering, sorting, search, and expansion. Swell backend REST API: GET /orders.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| search | string | – | Free-text search across the model's searchable fields. |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_list_products List products ~193
List products in the store, with MongoDB-style filtering, sorting, search, field selection, and expansion. Swell backend REST API: GET /products.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| fields | string | – | Comma-separated fields to return, e.g. "name,price,active". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| search | string | – | Free-text search across the model's searchable fields. |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_list_subscriptions List subscriptions ~144
List subscriptions, with filtering, sorting, and expansion. Swell backend REST API: GET /subscriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_query Query any collection (read-only) ~263
Power tool: read-only (GET only) access to ANY Swell model not covered by a dedicated tool — e.g. stock, promotions, giftcards, payments, shipments, settings. Supply the collection name plus the usual list params (limit, page, where, sort, expand, fields, search). Swell backend REST API: GET /{collection}.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | Swell model/collection name, e.g. "products", "stock", "promotions", "giftcards". |
| expand | string | – | Comma-separated related fields to expand, e.g. "variants,categories". |
| fields | string | – | Comma-separated fields to return, e.g. "name,price,active". |
| limit | integer | – | Max records to return (1–1000, Swell default 15). |
| page | integer | – | Page number for pagination (default 1). |
| search | string | – | Free-text search across the model's searchable fields. |
| sort | string | – | Sort expression, e.g. "date_created desc" or "name asc". |
| where | string | – | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
No output schema declared.
No examples provided.
swell_update_order Update an order ~109
MUTATES A LIVE ORDER. Partially update an existing order by id — e.g. change status, fulfillment, or notes. Provide the id plus a `fields` object of attributes to change, e.g. {"status":"complete"}. Swell backend REST API: PUT /orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Partial set of order attributes to update, e.g. {"status":"complete"} or fulfillment fields. |
| id | string | yes | Order id to update (required). |
No output schema declared.
No examples provided.
swell_update_product Update a product ~91
MUTATES LIVE STORE DATA. Partially update an existing product by id. Provide the id plus a `fields` object of attributes to change. Swell backend REST API: PUT /products/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | yes | Partial set of product attributes to update, e.g. {"price":19.99,"active":false}. |
| id | string | yes | Product id to update (required). |
No output schema declared.
No examples provided.
How do I install the Swell MCP by usefulapi server?
Swell MCP by usefulapi is a hosted endpoint at https://swell.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 · swell.usefulapi.io
claude mcp add --transport http io-usefulapi-swell 'https://swell.usefulapi.io/mcp'
What is the Swell MCP by usefulapi server?
Swell MCP by usefulapi is listed in the public MCP registry as io.usefulapi/swell. Manage your Swell headless-commerce store, products, orders, customers, and subscriptions. This page covers its hosted endpoint (https://swell.usefulapi.io/mcp).
Is the Swell MCP by usefulapi server safe to use?
Swell MCP by usefulapi scores 18 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 Swell MCP by usefulapi server expose?
Swell MCP by usefulapi exposes 16 tools: swell_list_products, swell_get_product, swell_list_categories, swell_list_orders, swell_get_order, and 11 more. Their descriptions and schemas cost roughly 2,225 tokens of context every time the server is loaded.
Does the Swell MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Swell MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Swell MCP by usefulapi server still maintained?
Swell MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Swell MCP by usefulapi server?
VerifyMCP ran 4 checks on Swell MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Swell MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.