io.usefulapi/ecwid
REMOTE · ECWID.USEFULAPI.IO · SCANNED SEP 20
Read store products, orders, customers, categories and coupons; adjust inventory and update orders.
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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1393 tokens (~116/item across 12 items; 12 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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/ecwid MCP server?
io.usefulapi/ecwid is a hosted endpoint at https://ecwid.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 · ecwid.usefulapi.io
claude mcp add --transport http io-usefulapi-ecwid 'https://ecwid.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-ecwid": {
"url": "https://ecwid.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-ecwid": {
"type": "http",
"url": "https://ecwid.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-ecwid] url = "https://ecwid.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-ecwid": {
"type": "remote",
"url": "https://ecwid.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-ecwid --url 'https://ecwid.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-ecwid:
url: "https://ecwid.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-ecwid": {
"Transport": "http",
"Url": "https://ecwid.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-ecwid -t streamable-http -u 'https://ecwid.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-ecwid": {
"type": "http",
"url": "https://ecwid.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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −13
- Stability: pass → 0.03 functional
- 12 Sept 26 +58
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Destructive annotations: pass functional
- 11 Sept 26 +10
- Transport: unverified → pass ▲ security
- 10 Sept 26 0
- Transport: fail → unverified ▼ security
- 26 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
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://ecwid.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 | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 39348e8a1d69d6ae1397c9ab47532ee3 |
| SANs: usefulapi.io, ecwid.usefulapi.io, *.ecwid.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 ecwid.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://ecwid.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://ecwid.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://ecwid.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://ecwid.usefulapi.io/mcp |
| Authorisation server | https://ecwid.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ecwid.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://ecwid.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 →
ecwid_adjust_product_inventory Adjust product inventory ~98
ADJUSTS a product's in-stock quantity by a delta — this MODIFIES live store data. Positive increases stock, negative decreases it. Ecwid REST: PUT /products/{productId}/inventory with JSON body {quantityDelta}. Returns {updateCount, warning?}.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | Product id to adjust. |
| quantity_delta | integer | yes | Change in stock quantity — positive increases stock, negative decreases. |
No output schema declared.
No examples provided.
ecwid_get_category Get category ~50
Get a single category by id, including its name, parent, product ids, and images. Ecwid REST: GET /categories/{categoryId}.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | yes | Category id. |
No output schema declared.
No examples provided.
ecwid_get_customer Get customer ~48
Get a single customer by id, including contact details, addresses, and customer group. Ecwid REST: GET /customers/{customerId}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | integer | yes | Customer id. |
No output schema declared.
No examples provided.
ecwid_get_order Get order ~59
Get a single order by its order number, including line items, totals, customer, and payment/fulfillment status. Ecwid REST: GET /orders/{orderNumber}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_number | – | yes | Order number (the store-visible order id). |
No output schema declared.
No examples provided.
ecwid_get_product Get product ~52
Get a single product by its id, including price, stock, options, images, and category assignments. Ecwid REST: GET /products/{productId}.
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | integer | yes | Product id. |
No output schema declared.
No examples provided.
ecwid_get_store_profile Get store profile ~41
Get the store's profile — general info (store id, name, currency), company details, and settings. Ecwid REST: GET /profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ecwid_list_categories List categories ~102
List the store's product categories, optionally scoped to a parent category and including hidden ones. Returns a paged collection. Ecwid REST: GET /categories.
| Name | Type | Req | Description |
|---|---|---|---|
| hidden_categories | boolean | – | Include hidden (disabled) categories when true. |
| limit | integer | – | Max results per page (1-100). |
| offset | integer | – | Pagination offset. |
| parent | integer | – | List only subcategories of this parent category id (0 = root). |
No output schema declared.
No examples provided.
ecwid_list_discount_coupons List discount coupons ~141
List the store's discount coupons with optional filters (coupon code, discount type, availability). Returns a paged collection. Ecwid REST: GET /discount_coupons.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | – | Filter by availability, e.g. ACTIVE | PAUSED | EXPIRED | COMPLETE. |
| coupon_code | string | – | Filter by exact coupon code. |
| discount_type | string | – | Filter by discount type, e.g. ABS | PERCENT | SHIPPING | ABS_AND_SHIPPING | PERCENT_AND_SHIPPING. |
| limit | integer | – | Max results per page (1-100). |
| offset | integer | – | Pagination offset. |
No output schema declared.
No examples provided.
ecwid_search_customers Search customers ~121
Search / list the store's customers with optional filters (keyword, email, name, customer group). Returns a paged collection. Ecwid REST: GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_group_id | integer | – | Filter by customer group id. |
| string | – | Filter by customer email. | |
| keyword | string | – | Full-text search term (name, email…). |
| limit | integer | – | Max results per page (1-100). |
| name | string | – | Filter by customer name. |
| offset | integer | – | Pagination offset. |
No output schema declared.
No examples provided.
ecwid_search_orders Search orders ~265
Search / list the store's orders with optional filters (keyword, customer email/id, payment & fulfillment status, coupon, created-date range). Returns a paged collection. Ecwid REST: GET /orders.
| Name | Type | Req | Description |
|---|---|---|---|
| coupon_code | string | – | Filter by applied coupon code. |
| created_from | string | – | Filter to orders created on/after this date (YYYY-MM-DD or Unix timestamp). |
| created_to | string | – | Filter to orders created on/before this date (YYYY-MM-DD or Unix timestamp). |
| customer_id | integer | – | Filter by customer id. |
| string | – | Filter by customer email. | |
| fulfillment_status | string | – | Filter by fulfillment status: AWAITING_PROCESSING | PROCESSING | SHIPPED | DELIVERED | WILL_NOT_DELIVER | RETURNED | READY_FOR_PICKUP | OUT_FOR_DELIVERY. |
| keyword | string | – | Full-text search term (order number, customer name, email…). |
| limit | integer | – | Max results per page (1-100). |
| offset | integer | – | Pagination offset. |
| payment_status | string | – | Filter by payment status: AWAITING_PAYMENT | PAID | CANCELLED | REFUNDED | PARTIALLY_REFUNDED | INCOMPLETE. |
No output schema declared.
No examples provided.
ecwid_search_products Search products ~242
Search / list the store's products with optional filters (keyword, SKU, category, stock, price range) and sorting. Returns a paged collection ({total, count, offset, limit, items}). Ecwid REST: GET /products.
| Name | Type | Req | Description |
|---|---|---|---|
| category | integer | – | Filter to products in this category id (0 = root). |
| enabled | boolean | – | Filter to enabled (true) or disabled (false) products. |
| inStock | boolean | – | Filter to in-stock (true) or out-of-stock (false) products. |
| keyword | string | – | Full-text search term (matches title, description, SKU…). |
| limit | integer | – | Max results per page (1-100). |
| offset | integer | – | Pagination offset. |
| priceFrom | number | – | Minimum price (inclusive). |
| priceTo | number | – | Maximum price (inclusive). |
| sku | string | – | Filter by exact product SKU. |
| sortBy | string | – | Sort order: RELEVANCE | PRICE_ASC | PRICE_DESC | NAME_ASC | NAME_DESC | ADDED_TIME_ASC | ADDED_TIME_DESC | UPDATED_TIME_ASC | UPDATED_TIME_DESC. |
No output schema declared.
No examples provided.
ecwid_update_order Update order ~174
UPDATES an order — its payment status, fulfillment status, and/or tracking number. This MODIFIES live store data and may trigger customer notifications. Ecwid REST: PUT /orders/{orderNumber}. Provide only the fields you want to change. Returns {updateCount}.
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment_status | string | – | New fulfillment status: AWAITING_PROCESSING | PROCESSING | SHIPPED | DELIVERED | WILL_NOT_DELIVER | RETURNED | READY_FOR_PICKUP | OUT_FOR_DELIVERY. |
| order_number | – | yes | Order number to update. |
| payment_status | string | – | New payment status: AWAITING_PAYMENT | PAID | CANCELLED | REFUNDED | PARTIALLY_REFUNDED | INCOMPLETE. |
| tracking_number | string | – | Shipping tracking number to record on the order. |
No output schema declared.
No examples provided.
What is the io.usefulapi/ecwid MCP server?
io.usefulapi/ecwid is an MCP server listed in the public MCP registry as io.usefulapi/ecwid. Read store products, orders, customers, categories and coupons; adjust inventory and update orders. This page covers its hosted endpoint (https://ecwid.usefulapi.io/mcp).
Is the io.usefulapi/ecwid MCP server safe to use?
io.usefulapi/ecwid scores 76 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/ecwid MCP server expose?
io.usefulapi/ecwid exposes 12 tools: ecwid_get_store_profile, ecwid_search_products, ecwid_get_product, ecwid_search_orders, ecwid_get_order, and 7 more. Their descriptions and schemas cost roughly 1,393 tokens of context every time the server is loaded.
Does the io.usefulapi/ecwid MCP server require authentication?
Yes. io.usefulapi/ecwid 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/ecwid MCP server still maintained?
io.usefulapi/ecwid 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.