Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Swell 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.
What it does
Manage your Swell headless-commerce store — products, orders, customers, and subscriptions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-swell-mcp https://swell.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# swell_list_products, swell_get_product, swell_list_categories and 13 more
Swell costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 usefulapi-swell-mcp https://swell.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
16 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 products in the store, with MongoDB-style filtering, sorting, search, field selection, and expansion. Swell backend REST API: GET /products.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
| fields | string | no | Comma-separated fields to return, e.g. "name,price,active". |
| search | string | no | Free-text search across the model's searchable fields. |
Fetch a single product by its record id or its slug. Supports expand and fields. Swell backend REST API: GET /products/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Product id or slug. |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
| fields | string | no | Comma-separated fields to return, e.g. "name,price". |
List product categories, with filtering, sorting, search, and expansion. Swell backend REST API: GET /categories.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
| search | string | no | Free-text search across the model's searchable fields. |
List orders, with MongoDB-style filtering, sorting, search, and expansion. Swell backend REST API: GET /orders.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
| search | string | no | Free-text search across the model's searchable fields. |
Fetch a single order by its record id or its order number. Supports expand and fields. Swell backend REST API: GET /orders/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Order id or order number. |
| expand | string | no | Comma-separated related fields to expand, e.g. "items,account". |
| fields | string | no | Comma-separated fields to return. |
List customers. In Swell, customers are the accounts model — this queries GET /accounts, with filtering, sorting, search, and expansion.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
| search | string | no | Free-text search across the model's searchable fields. |
Fetch a single customer (Swell accounts model) by id. Supports expand and fields. Swell backend REST API: GET /accounts/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Customer (account) id. |
| expand | string | no | Comma-separated related fields to expand, e.g. "orders,subscriptions". |
| fields | string | no | Comma-separated fields to return. |
List shopping carts (including abandoned carts), with filtering, sorting, and expansion. Swell backend REST API: GET /carts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
List subscriptions, with filtering, sorting, and expansion. Swell backend REST API: GET /subscriptions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
Fetch a single subscription by id. Supports expand. Swell backend REST API: GET /subscriptions/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Subscription id. |
| expand | string | no | Comma-separated related fields to expand, e.g. "account,product". |
List invoices (typically subscription invoices), with filtering, sorting, and expansion. Swell backend REST API: GET /invoices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
List discount coupons, with filtering and sorting. Swell backend REST API: GET /coupons.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| collection | string | yes | Swell model/collection name, e.g. "products", "stock", "promotions", "giftcards". |
| limit | integer | no | Max records to return (1–1000, Swell default 15). |
| page | integer | no | Page number for pagination (default 1). |
| where | string | no | MongoDB-style filter as a JSON object string, e.g. {"active":true,"price":{"$gte":10}}. |
| sort | string | no | Sort expression, e.g. "date_created desc" or "name asc". |
| expand | string | no | Comma-separated related fields to expand, e.g. "variants,categories". |
| fields | string | no | Comma-separated fields to return, e.g. "name,price,active". |
| search | string | no | Free-text search across the model's searchable fields. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Product name (required). |
| price | number | no | Product price. |
| active | boolean | no | Whether the product is active/visible. |
| sku | string | no | Stock-keeping unit. |
| stock_level | number | no | Available stock quantity. |
| type | string | no | Product type, e.g. "standard", "subscription", "digital". |
| description | string | no | Product description. |
| fields | object | no | Any additional product fields, merged into the request body (e.g. attributes, options, images). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Product id to update (required). |
| fields | object | yes | Partial set of product attributes to update, e.g. {"price":19.99,"active":false}. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Order id to update (required). |
| fields | object | yes | Partial set of order attributes to update, e.g. {"status":"complete"} or fulfillment fields. |
- 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 Swell or to call it, at any volume.
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.
| 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 |
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.
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 |
|---|---|---|
| swell_list_products | no tags | |
| swell_get_product | untrusted-input | untrusted-input: keyword "fetch" |
| swell_list_categories | no tags | |
| swell_list_orders | no tags | |
| swell_get_order | untrusted-input | untrusted-input: keyword "fetch" |
| swell_list_customers | no tags | |
| swell_get_customer | untrusted-input | untrusted-input: keyword "fetch" |
| swell_list_carts | no tags | |
| swell_list_subscriptions | no tags | |
| swell_get_subscription | untrusted-input | untrusted-input: keyword "fetch" |
| swell_list_invoices | no tags | |
| swell_list_coupons | no tags | |
| swell_query | no tags | |
| swell_create_product | state-write | state-write: declares destructiveHint: true |
| swell_update_product | state-write | state-write: declares destructiveHint: true |
| swell_update_order | state-write | state-write: declares destructiveHint: 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.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
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.11.1.
No release note was published with this version.
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.
Any signed-in account that does not publish Swell can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.