IdoSell MCP by usefulapi
REMOTE · IDOSELL.USEFULAPI.IO
Search orders, products, stock, customers and returns; set order status in IdoSell.
Available components
Last scanned (1 hour 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 −48
- 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 65
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://idosell.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 idosell.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | 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://idosell.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/idosell/ |
| http (plaintext) | http://idosell.usefulapi.io/mcp | Inconclusive | 302 | http://idosell.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 →
idosell_get_order_packages Get order parcels ~48
Get the parcels (shipments) of orders: courier, tracking numbers and status. API: GET /orders/packages.
| Name | Type | Req | Description |
|---|---|---|---|
| order_serial_numbers | array | yes | Order serial numbers. |
No output schema declared.
No examples provided.
idosell_get_orders Get orders by id ~66
Get orders by order ids or serial numbers (give at least one). Use idosell_search_orders for filters. API: GET /orders/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| orders_ids | array | – | Order ids. |
| serial_numbers | array | – | Order serial numbers (max 100). |
No output schema declared.
No examples provided.
idosell_get_product_stocks Get product stock levels ~69
Get stock quantities per warehouse and size for products. API: GET /products/stocks.
| Name | Type | Req | Description |
|---|---|---|---|
| ident_type | string | yes | What the values in products are: panel id, index, external code or producer code. |
| products | array | yes | Product identifiers of the given type. |
No output schema declared.
No examples provided.
idosell_get_shop_config Get shop configuration ~54
Get the panel configuration: owner company data, languages, base currency, warehouses (stocks) and shops with their ids. Good first call to learn shop ids and warehouse ids. API: GET /system/config.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
idosell_list_brands List brands ~69
List the brands (producers) of the shop with ids and names. API: GET /products/brands.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1 to 100. |
| page | integer | – | Page number, counting from 0 (default 0). |
No output schema declared.
No examples provided.
idosell_list_categories List product categories ~75
List the product categories of the shop with ids and names. API: GET /products/categories.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these category ids. |
| limit | integer | – | Results per page, 1 to 100. |
| page | integer | – | Page number, counting from 0 (default 0). |
No output schema declared.
No examples provided.
idosell_list_couriers List couriers ~94
List the couriers available for a country, and whether each one handles pickup points. API: GET /couriers/couriers.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | Country code, ISO 3166-1 alpha-2. |
| limit | integer | – | Results per page, 1 to 100. |
| page | integer | – | Page number, counting from 0 (default 0). |
No output schema declared.
No examples provided.
idosell_list_order_statuses List order statuses ~36
List the order statuses configured in the panel, with their ids and names. API: GET /orders/statuses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
idosell_list_returns List returns ~104
List returns issued for orders, filterable by order serial number, return id or status id. API: GET /returns/returns.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1 to 100. |
| order_serial_number | integer | – | Order serial number. |
| page | integer | – | Page number, counting from 0 (default 0). |
| return_ids | array | – | Return ids. |
| status | integer | – | Return status id. |
No output schema declared.
No examples provided.
idosell_search_customers Search customers ~122
Find customer accounts by text (name, e-mail, login), ids or active state. Returns contact data, addresses, balances and consents. API: GET /clients/clients.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | true = only active accounts, false = only inactive. |
| customer_ids | array | – | Customer numbers. |
| limit | integer | – | Results per page, 1 to 100. |
| page | integer | – | Page number, counting from 0 (default 0). |
| text | string | – | Text searched in customer data. |
No output schema declared.
No examples provided.
idosell_search_orders Search orders ~215
Search orders by status, date range, customer, order ids or serial numbers. Returns order details with products, payments, dispatch data and the customer. Read-only (a POST search). API: POST /orders/orders/search.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | – | Customer e-mail address. |
| customer_login | string | – | Customer login. |
| date_from | string | – | Range start, YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. |
| date_to | string | – | Range end, YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. |
| date_type | string | – | Which date the range applies to (default add = order placed). |
| limit | integer | – | Results per page, 1 to 100. |
| orders_ids | array | – | Order ids. |
| page | integer | – | Page number, counting from 0 (default 0). |
| serial_numbers | array | – | Order serial numbers (max 100). |
| statuses | array | – | Only orders in these statuses. |
No output schema declared.
No examples provided.
idosell_search_products Search products ~177
Search products by text, code, availability, visibility or promotion. Returns prices, stock summary, images and categories. Read-only (a POST search). API: POST /products/products/search.
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | true = only available products, false = only unavailable. |
| code_part | string | – | Product code, or a part of it (producer, external or panel code). |
| in_promotion | boolean | – | true = only products in promotion. |
| limit | integer | – | Results per page, 1 to 100. |
| page | integer | – | Page number, counting from 0 (default 0). |
| product_ids | array | – | Product ids. |
| text | string | – | Text found in the name or description. |
| visible | boolean | – | true = only products visible in the shop. |
No output schema declared.
No examples provided.
idosell_set_order_status Set order status ~89
WRITE: change the status of one order (for example to packed, ready or canceled). Setting the same status again has no further effect. The panel may send customer e-mails for some status changes. API: PUT /orders/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| order_serial_number | integer | yes | Order serial number (from idosell_search_orders). |
| status | string | yes | The new order status. |
No output schema declared.
No examples provided.
How do I install the IdoSell MCP by usefulapi server?
IdoSell MCP by usefulapi is a hosted endpoint at https://idosell.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 · idosell.usefulapi.io
claude mcp add --transport http io-usefulapi-idosell 'https://idosell.usefulapi.io/mcp'
What is the IdoSell MCP by usefulapi server?
IdoSell MCP by usefulapi is listed in the public MCP registry as io.usefulapi/idosell. Search orders, products, stock, customers and returns; set order status in IdoSell. This page covers its hosted endpoint (https://idosell.usefulapi.io/mcp).
Is the IdoSell MCP by usefulapi server safe to use?
IdoSell 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 IdoSell MCP by usefulapi server expose?
IdoSell MCP by usefulapi exposes 13 tools: idosell_get_shop_config, idosell_search_orders, idosell_get_orders, idosell_list_order_statuses, idosell_get_order_packages, and 8 more. Their descriptions and schemas cost roughly 1,218 tokens of context every time the server is loaded.
Does the IdoSell MCP by usefulapi server require authentication?
Its publisher declares no required credentials for IdoSell 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 IdoSell MCP by usefulapi server still maintained?
IdoSell 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.
What did VerifyMCP test on the IdoSell MCP by usefulapi server?
VerifyMCP ran 4 checks on IdoSell MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about IdoSell MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.