# IdoSell MCP by usefulapi (remote · idosell.usefulapi.io)

Search orders, products, stock, customers and returns; set order status in IdoSell.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `idosell.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-idosell/idosell.md), [page](https://verifymcp.io/servers/io-usefulapi-idosell/idosell)

## Channel facts

- Endpoint: `https://idosell.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-06.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-idosell 'https://idosell.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-idosell": {
      "url": "https://idosell.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-idosell": {
      "type": "http",
      "url": "https://idosell.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-idosell]
url = "https://idosell.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-idosell": {
      "type": "remote",
      "url": "https://idosell.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-idosell --url 'https://idosell.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-idosell:
    url: "https://idosell.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-idosell": {
      "Transport": "http",
      "Url": "https://idosell.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-idosell -t streamable-http -u 'https://idosell.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-idosell": {
      "type": "http",
      "url": "https://idosell.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-06 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-02 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 65)

First indexed and scored.

## MCP tools (13)

### `idosell_get_shop_config` (~54 tokens)

Get shop configuration

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.

### `idosell_search_orders` (~215 tokens)

Search orders

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.

Input parameters:

- `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.

### `idosell_get_orders` (~66 tokens)

Get orders by id

Get orders by order ids or serial numbers (give at least one). Use idosell_search_orders for filters. API: GET /orders/orders.

Input parameters:

- `orders_ids` (array): Order ids.
- `serial_numbers` (array): Order serial numbers (max 100).

### `idosell_list_order_statuses` (~36 tokens)

List order statuses

List the order statuses configured in the panel, with their ids and names. API: GET /orders/statuses.

### `idosell_get_order_packages` (~48 tokens)

Get order parcels

Get the parcels (shipments) of orders: courier, tracking numbers and status. API: GET /orders/packages.

Input parameters:

- `order_serial_numbers` (array, required): Order serial numbers.

### `idosell_search_products` (~177 tokens)

Search products

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.

Input parameters:

- `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.

### `idosell_get_product_stocks` (~69 tokens)

Get product stock levels

Get stock quantities per warehouse and size for products. API: GET /products/stocks.

Input parameters:

- `ident_type` (string, required): What the values in products are: panel id, index, external code or producer code.
- `products` (array, required): Product identifiers of the given type.

### `idosell_list_categories` (~75 tokens)

List product categories

List the product categories of the shop with ids and names. API: GET /products/categories.

Input parameters:

- `ids` (array): Only these category ids.
- `limit` (integer): Results per page, 1 to 100.
- `page` (integer): Page number, counting from 0 (default 0).

### `idosell_list_brands` (~69 tokens)

List brands

List the brands (producers) of the shop with ids and names. API: GET /products/brands.

Input parameters:

- `limit` (integer): Results per page, 1 to 100.
- `page` (integer): Page number, counting from 0 (default 0).

### `idosell_search_customers` (~122 tokens)

Search customers

Find customer accounts by text (name, e-mail, login), ids or active state. Returns contact data, addresses, balances and consents. API: GET /clients/clients.

Input parameters:

- `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.

### `idosell_list_returns` (~104 tokens)

List returns

List returns issued for orders, filterable by order serial number, return id or status id. API: GET /returns/returns.

Input parameters:

- `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.

### `idosell_list_couriers` (~94 tokens)

List couriers

List the couriers available for a country, and whether each one handles pickup points. API: GET /couriers/couriers.

Input parameters:

- `country_code` (string, required): Country code, ISO 3166-1 alpha-2.
- `limit` (integer): Results per page, 1 to 100.
- `page` (integer): Page number, counting from 0 (default 0).

### `idosell_set_order_status` (~89 tokens)

Set order status

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.

Input parameters:

- `order_serial_number` (integer, required): Order serial number (from idosell_search_orders).
- `status` (string, required): The new order status.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-idosell/idosell#diagnostics

## Score history

- 2026-11-06: 18
- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 66
- 2026-10-31: 65

## Common questions

### 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 6 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.

## Links

- Remote endpoint: https://idosell.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/idosell/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-idosell/idosell.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-idosell/idosell/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-idosell/idosell.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-idosell/idosell