io.usefulapi/swell
REMOTE · SWELL.USEFULAPI.IO · SCANNED SEP 20
Manage your Swell headless-commerce store — products, orders, customers, and subscriptions.
Available components
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 answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2225 tokens (~139/item across 16 items; 16 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
How do I install the io.usefulapi/swell MCP server?
io.usefulapi/swell 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'
{
"mcpServers": {
"io-usefulapi-swell": {
"url": "https://swell.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-swell": {
"type": "http",
"url": "https://swell.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-swell] url = "https://swell.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-swell": {
"type": "remote",
"url": "https://swell.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-swell --url 'https://swell.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-swell:
url: "https://swell.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-swell": {
"Transport": "http",
"Url": "https://swell.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-swell -t streamable-http -u 'https://swell.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-swell": {
"type": "http",
"url": "https://swell.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Aug 26 0
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 1 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ 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 20 Sept 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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 8da1d756e116f188131d48596947550c |
| SANs: usefulapi.io, swell.usefulapi.io, *.swell.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. | present | 57355 | 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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://swell.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://swell.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://swell.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://swell.usefulapi.io/mcp |
| Authorisation server | https://swell.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://swell.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/swell MCP server?
io.usefulapi/swell is an MCP server 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 io.usefulapi/swell MCP server safe to use?
io.usefulapi/swell scores 85 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 io.usefulapi/swell MCP server expose?
io.usefulapi/swell 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 io.usefulapi/swell MCP server require authentication?
Yes. io.usefulapi/swell 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 io.usefulapi/swell MCP server still maintained?
io.usefulapi/swell is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.