Channable MCP by usefulapi
REMOTE · CHANNABLE.USEFULAPI.IO
Read marketplace orders and returns; send shipment, cancellation and stock updates.
Available components
Last scanned (7 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.
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.
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
First indexed and scored.
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://channable.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 channable.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://channable.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/channable/ |
| http (plaintext) | http://channable.usefulapi.io/mcp | Inconclusive | 302 | http://channable.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 →
channable_cancel_order Cancel an order ~195
Seller-side cancellation: set an order to cancelled. Pass order_item_ids to cancel only some items (the order then becomes partial); omit it to cancel the whole order. Amazon, Cdiscount and Spartoo do not support partial cancellations. A buyer-side cancellation must be confirmed in the marketplace seller account instead. POST /v1/companies/{company}/projects/{project}/orders/{order_id}/cancel. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retried; if it times out, check the order in Channable before trying again.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| order_item_ids | array | – | Only these order items are cancelled (partial cancellation). Omit to cancel all. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
No output schema declared.
No examples provided.
channable_create_return Create a return for an order ~171
Manually create a return on the marketplace for products of an order. Only Fruugo, Otto, Veepee and Zalando support this. products lists the product ids (the item id of the order), the quantity and optionally accepted or rejected. POST /v1/companies/{company}/projects/{project}/orders/{order_id}/return. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retried; if it times out, check the order in Channable before trying again.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| products | array | yes | The products to return. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
No output schema declared.
No examples provided.
channable_get_order Get an order ~104
One order with its customer, addresses, items, status, fulfillments and event log. order_id is the Channable order id (the id field from channable_list_orders). GET /v2/companies/{company}/projects/{project}/orders/{order_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
No output schema declared.
No examples provided.
channable_get_order_statistics Get order statistics ~163
Order statistics of a project for a time frame: orders, ordered products, marketplace commission, shipping costs, revenue and daily revenue, per order connection and in total. Pass order_config_id (the order_config_id field of an order) for one order connection only. GET /v1/companies/{company}/projects/{project}/statistics/orders[/{order_config_id}].
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Last day. |
| order_config_id | integer | – | Only this order connection (the order_config_id of an order). |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| start_date | string | – | First day (yyyy-mm-dd or ISO 8601, UTC). |
No output schema declared.
No examples provided.
channable_get_return Get a return ~93
One return with its item, reason, customer, status and log. return_id is the id field from channable_list_returns. GET /v1/companies/{company}/projects/{project}/returns/{return_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| return_id | integer | yes | Channable return id. |
No output schema declared.
No examples provided.
channable_list_orders List orders ~335
List the marketplace orders of a project, newest first. Filters combine with AND; dates are read as UTC. Paged: pass next_offset as offset (total is the size of the page, not of all orders). Reply: orders, error_count (orders with an error), count, next_offset. GET /v2/companies/{company}/projects/{project}/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Orders created on or before this date. |
| errors | boolean | – | true = only orders with an error. |
| last_modified_after | string | – | Orders modified after this date. |
| last_modified_before | string | – | Orders modified before this date. |
| limit | integer | – | Results per page, 1-100 (default 100). |
| offset | integer | – | Skip this many results (default 0). Use next_offset from the previous reply. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| retrieved_at_end | string | – | Orders retrieved from the marketplace on or before this date. |
| retrieved_at_start | string | – | Orders retrieved from the marketplace on or after this date. |
| search | string | – | Free-text search (order ids, names, products). |
| start_date | string | – | Orders created on or after this date (yyyy-mm-dd or ISO 8601, UTC). |
| status | array | – | Only orders in one of these statuses: shipped, not_shipped, waiting, cancelled, processing, pending_shipment, pending_cancellation, cancellation_request, awaiting_confirmation, partial, manual. |
No output schema declared.
No examples provided.
channable_list_returns List returns ~254
List the returns of a project, newest first. Dates are read as UTC. Paged: pass next_offset as offset. Reply: returns, error_count, count, next_offset. GET /v1/companies/{company}/projects/{project}/returns.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Returns created on or before this date. |
| errors | boolean | – | true = only returns with an error. |
| last_modified_after | string | – | Returns modified after this date. |
| last_modified_before | string | – | Returns modified before this date. |
| limit | integer | – | Results per page, 1-100 (default 100). |
| offset | integer | – | Skip this many results (default 0). Use next_offset from the previous reply. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| retrieved_at_end | string | – | Returns retrieved on or before this date. |
| retrieved_at_start | string | – | Returns retrieved on or after this date. |
| search | string | – | Free-text search. |
| start_date | string | – | Returns created on or after this date (yyyy-mm-dd or ISO 8601, UTC). |
No output schema declared.
No examples provided.
channable_list_stock_updates List posted stock updates ~218
List the offers (product stock updates) that were posted to a project, newest first: id, stock, price, title, GTIN. Paged: pass next_offset as offset. Reply: offers, count, next_offset. GET /v1/companies/{company}/projects/{project}/offers.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Offers created on or before this date. |
| last_modified_after | string | – | Offers modified after this date. |
| last_modified_before | string | – | Offers modified before this date. |
| limit | integer | – | Results per page, 1-100 (default 100). |
| offset | integer | – | Skip this many results (default 0). Use next_offset from the previous reply. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| search | string | – | Free-text search (offer id, title, GTIN). |
| start_date | string | – | Offers created on or after this date (UTC). |
No output schema declared.
No examples provided.
channable_list_transporters List transporter codes ~145
Channable transporter codes for shipping updates. With no argument: all codes and labels (transporter_code is what channable_ship_order expects). With transporter_code: the marketplace-specific carriers behind that code. With channel (a marketplace such as bol, amazon, ebay): the carriers that marketplace supports. Give at most one of the two. GET /v1/transporters/all | /transporter/{code} | /channel/{channel}.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | A marketplace name, lowercase, e.g. bol, amazon, ebay, otto. |
| transporter_code | string | – | A Channable transporter code, e.g. DHL. |
No output schema declared.
No examples provided.
channable_mark_order_manual Mark an order as handled manually ~139
Tell Channable that you handle this order yourself: Channable takes no further action on it (no status updates to the marketplace). POST /v1/companies/{company}/projects/{project}/orders/{order_id}/manual. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retried; if it times out, check the order in Channable before trying again.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Channable order id. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
No output schema declared.
No examples provided.
channable_ship_order Mark an order as shipped ~307
Set an order to shipped, with tracking data. Give transporter as a Channable transporter code (channable_list_transporters lists them) and tracking_code. Pass order_item_ids to ship only some items (the order then becomes partial; repeat with the other items later); omit it to ship the whole order. Spartoo and Veepee do not support partial shipments. POST /v1/companies/{company}/projects/{project}/orders/{order_id}/shipment. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retried; if it times out, check the order in Channable before trying again.
| Name | Type | Req | Description |
|---|---|---|---|
| delivery_bill_id | string | – | Delivery bill id, if the marketplace asks for it. |
| order_id | integer | yes | Channable order id. |
| order_item_ids | array | – | Only these order items are shipped (partial shipment). Omit to ship all. |
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| return_tracking_code | string | – | Track and trace code of the return label. |
| return_transporter | string | – | Transporter code for the return label, if the marketplace asks for it. |
| tracking_code | string | – | Track and trace code of the parcel. |
| transporter | string | – | Channable transporter code, e.g. POSTNL, DHL, DPD. |
No output schema declared.
No examples provided.
channable_update_return_status Set the status of a return ~163
Set the status of a return: accepted, rejected, repaired, keeps, exchanged, cancelled. Depending on the status the customer does or does not get their money back (accepted and cancelled differ from rejected). POST /v1/companies/{company}/projects/{project}/returns/{return_id}/status. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retried; if it times out, check the order in Channable before trying again.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| return_id | integer | yes | Channable return id. |
| status | string | yes | The new return status. |
No output schema declared.
No examples provided.
channable_update_stock Update product stock on all marketplaces ~161
Set the stock of up to 50 offers. Each item is the offer id as the marketplaces know it, plus the WHOLE new stock value (not a delta). Channable passes the new stock to every marketplace of the project, which changes what customers can buy. POST /v1/companies/{company}/projects/{project}/stock_updates. Channable passes this change on to the marketplace. It cannot be undone through this API and the call is never retried; if it times out, check the order in Channable before trying again.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | – | Channable project id (Project settings). Default: the project chosen at login. |
| updates | array | yes | 1-50 stock updates. |
No output schema declared.
No examples provided.
How do I install the Channable MCP by usefulapi server?
Channable MCP by usefulapi is a hosted endpoint at https://channable.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 · channable.usefulapi.io
claude mcp add --transport http io-usefulapi-channable 'https://channable.usefulapi.io/mcp'
What is the Channable MCP by usefulapi server?
Channable MCP by usefulapi is listed in the public MCP registry as io.usefulapi/channable. Read marketplace orders and returns; send shipment, cancellation and stock updates. This page covers its hosted endpoint (https://channable.usefulapi.io/mcp).
Is the Channable MCP by usefulapi server safe to use?
Channable 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 Channable MCP by usefulapi server expose?
Channable MCP by usefulapi exposes 13 tools: channable_list_orders, channable_get_order, channable_ship_order, channable_cancel_order, channable_mark_order_manual, and 8 more. Their descriptions and schemas cost roughly 2,448 tokens of context every time the server is loaded.
Does the Channable MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Channable 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 Channable MCP by usefulapi server still maintained?
Channable 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.