Skip to content

Swell MCP by usefulapi

io.usefulapi/swellusefulapi.iostreamable-httpv1.40.4Scanned

Manage your Swell headless-commerce store — products, orders, customers, and subscriptions.

16 tools: 3 can delete or cancel things and 13 only read.

Tools: 3 delete, 0 irreversible, 0 write, 13 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Swell MCP by usefulapi can do

The Swell MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (3 tools: swell_create_product, swell_update_product and swell_update_order). 13 tools only read.

2 tools read private data (swell_list_products and swell_list_orders).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Deletes or cancels 3Claude Code: deny
  • swell_create_productMUTATES LIVE STORE DATA.No findings

    Why it is in this group

    • The name "swell_create_product" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a product
    • destructiveHint: true
  • swell_update_orderMUTATES A LIVE ORDER.No findings

    Why it is in this group

    • The name "swell_update_order" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update an order
    • destructiveHint: true
  • swell_update_productMUTATES LIVE STORE DATA.No findings

    Why it is in this group

    • The name "swell_update_product" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Update a product
    • destructiveHint: true
Only reads 13Show 13 read-only tools
  • swell_get_customerFetch a single customer (Swell `accounts` model) by id.No findings

    Why it is in this group

    • The name "swell_get_customer" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single customer (Swell `accounts` model) by id. Supports `expand` and `fields`. Swell backend REST API: GET /accounts/{id}.

    Annotations the server declares

    • title: Get a customer
    • readOnlyHint: true
  • swell_get_orderFetch a single order by its record id or its order number.No findings

    Why it is in this group

    • The name "swell_get_order" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single order by its record id or its order number. Supports `expand` and `fields`. Swell backend REST API: GET /orders/{id}.

    Annotations the server declares

    • title: Get an order
    • readOnlyHint: true
  • swell_get_productFetch a single product by its record id or its slug.No findings

    Why it is in this group

    • The name "swell_get_product" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single product by its record id or its slug. Supports `expand` and `fields`. Swell backend REST API: GET /products/{id}.

    Annotations the server declares

    • title: Get a product
    • readOnlyHint: true
  • swell_get_subscriptionFetch a single subscription by id.No findings

    Why it is in this group

    • The name "swell_get_subscription" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single subscription by id. Supports `expand`. Swell backend REST API: GET /subscriptions/{id}.

    Annotations the server declares

    • title: Get a subscription
    • readOnlyHint: true
  • swell_list_cartsList shopping carts (including abandoned carts), with filtering, sorting, and expansion.No findings

    Why it is in this group

    • The name "swell_list_carts" says "list": a word for reading.
    Description, as the server wrote it
    List shopping carts (including abandoned carts), with filtering, sorting, and expansion. Swell backend REST API: GET /carts.

    Annotations the server declares

    • title: List carts
    • readOnlyHint: true
  • swell_list_categoriesList product categories, with filtering, sorting, search, and expansion.No findings

    Why it is in this group

    • The name "swell_list_categories" says "list": a word for reading.
    Description, as the server wrote it
    List product categories, with filtering, sorting, search, and expansion. Swell backend REST API: GET /categories.

    Annotations the server declares

    • title: List categories
    • readOnlyHint: true
  • swell_list_couponsList discount coupons, with filtering and sorting.No findings

    Why it is in this group

    • The name "swell_list_coupons" says "list": a word for reading.
    Description, as the server wrote it
    List discount coupons, with filtering and sorting. Swell backend REST API: GET /coupons.

    Annotations the server declares

    • title: List coupons
    • readOnlyHint: true
  • swell_list_customersList customers.No findings

    Why it is in this group

    • The name "swell_list_customers" says "list": a word for reading.
    Description, as the server wrote it
    List customers. In Swell, customers are the `accounts` model — this queries GET /accounts, with filtering, sorting, search, and expansion.

    Annotations the server declares

    • title: List customers
    • readOnlyHint: true
  • swell_list_invoicesList invoices (typically subscription invoices), with filtering, sorting, and expansion.No findings

    Why it is in this group

    • The name "swell_list_invoices" says "list": a word for reading.
    Description, as the server wrote it
    List invoices (typically subscription invoices), with filtering, sorting, and expansion. Swell backend REST API: GET /invoices.

    Annotations the server declares

    • title: List invoices
    • readOnlyHint: true
  • swell_list_ordersList orders, with MongoDB-style filtering, sorting, search, and expansion.Reads private dataNo findings

    Why it is in this group

    • The name "swell_list_orders" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "db": it reads databases.
    Description, as the server wrote it
    List orders, with MongoDB-style filtering, sorting, search, and expansion. Swell backend REST API: GET /orders.

    Annotations the server declares

    • title: List orders
    • readOnlyHint: true
  • swell_list_productsList products in the store, with MongoDB-style filtering, sorting, search, field selection, and expansion.Reads private dataNo findings

    Why it is in this group

    • The name "swell_list_products" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "db": it reads databases.
    Description, as the server wrote it
    List products in the store, with MongoDB-style filtering, sorting, search, field selection, and expansion. Swell backend REST API: GET /products.

    Annotations the server declares

    • title: List products
    • readOnlyHint: true
  • swell_list_subscriptionsList subscriptions, with filtering, sorting, and expansion.No findings

    Why it is in this group

    • The name "swell_list_subscriptions" says "list": a word for reading.
    Description, as the server wrote it
    List subscriptions, with filtering, sorting, and expansion. Swell backend REST API: GET /subscriptions.

    Annotations the server declares

    • title: List subscriptions
    • readOnlyHint: true
  • swell_queryPower tool: read-only (GET only) access to ANY Swell model not covered by a dedicated tool — e.g.No findings

    Why it is in this group

    • The name "swell_query" says "query": a word for reading.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Query any collection (read-only)
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://swell.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://swell.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://swell.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://swell.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http swell https://swell.usefulapi.io/mcp
claude mcp add --transport http swell https://swell.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__swell__swell_list_products",
      "mcp__swell__swell_get_product",
      "mcp__swell__swell_list_categories",
      "mcp__swell__swell_list_orders",
      "mcp__swell__swell_get_order",
      "mcp__swell__swell_list_customers",
      "mcp__swell__swell_get_customer",
      "mcp__swell__swell_list_carts",
      "mcp__swell__swell_list_subscriptions",
      "mcp__swell__swell_get_subscription",
      "mcp__swell__swell_list_invoices",
      "mcp__swell__swell_list_coupons",
      "mcp__swell__swell_query"
    ],
    "ask": [],
    "deny": [
      "mcp__swell__swell_create_product",
      "mcp__swell__swell_update_product",
      "mcp__swell__swell_update_order"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as swell. Review it before you use it.

Capability tags behind 2 rules
  • mcp__swell__swell_list_products private-data
  • mcp__swell__swell_list_orders private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/swell/verify?hash=33a603979f15c602ad29cd1b1343701ef7126c4f9f3c2aa86661a38a2210b7e9" | jq -e '.changed == false'

Pinned hash 33a603979f15, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/swell/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/swell
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/swell.svg)](https://radar.anlyon.com/servers/io.usefulapi/swell)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

Swell MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Swell MCP by usefulapi safe?

No scan can promise that. What its definitions show: 16 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Swell MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: swell_create_product, swell_update_product and swell_update_order.

Can the Swell MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Swell MCP by usefulapi have?

16 tools: 3 destructive, 13 read. swell_create_product, swell_update_product, swell_update_order, swell_list_products, swell_get_product, swell_list_categories, swell_list_orders, swell_get_order and 8 more.

Does the Swell MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Swell MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Swell MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.