PlentyONE MCP by usefulapi
REMOTE · PLENTYMARKETS.USEFULAPI.IO
Review PlentyONE orders, items, stock and contacts; add comments and update order status.
Available components
Last scanned (9 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.
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.
- 1 Nov 26 −45
- 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
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- New prompt “add_an_internal_order_note” functional
- New prompt “change_an_order_s_status” functional
- New prompt “find_stock_that_needs_attention” functional
- New prompt “review_a_customer_s_orders” functional
- New prompt “review_unpaid_orders” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.2 → 1.1.0 functional
- 30 Oct 26 60
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://plentymarkets.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 plentymarkets.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://plentymarkets.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/plentymarkets/ |
| http (plaintext) | http://plentymarkets.usefulapi.io/mcp | Inconclusive | 302 | http://plentymarkets.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 →
plentymarkets_add_comment ~126
WRITE: add an internal comment to an order, order item, contact, category or variation (an additive note, nothing is overwritten). By default the comment is NOT visible to the customer; only make it visible when the user explicitly asks. POST /rest/comments.
| Name | Type | Req | Description |
|---|---|---|---|
| reference_id | integer | yes | The id of the order, order item, contact, category or variation. |
| reference_type | string | yes | – |
| text | string | yes | The comment text. |
| visible_for_contact | boolean | – | Show the comment to the customer (default false: internal only). |
No output schema declared.
No examples provided.
plentymarkets_get_contact ~65
Get one contact by id (customer personal data). Add addresses or accounts with `with` (the relations documented for this single-contact route). GET /rest/accounts/contacts/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | – |
| with | array | – | – |
No output schema declared.
No examples provided.
plentymarkets_get_item ~66
Get one item by id: flags, manufacturer, texts, condition, age rating and the item-level settings. GET /rest/items/{itemId}.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | integer | yes | – |
| lang | string | – | Language of the texts, a two-letter code. |
No output schema declared.
No examples provided.
plentymarkets_get_order ~94
Get one order by id: status, amounts, dates, properties, order items, address relations. Add related data with `with` (addresses, comments, payments, documents, shippingPackages ...). GET /rest/orders/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| add_order_items | boolean | – | Include the order items (default true). |
| order_id | integer | yes | The order id. |
| with | array | – | – |
No output schema declared.
No examples provided.
plentymarkets_get_order_status_history ~50
The status changes of an order: which status, when, and by which user. GET /rest/orders/{orderId}/status-history.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | – |
No output schema declared.
No examples provided.
plentymarkets_list_categories ~152
List item categories (the category tree: id, parent, level, type, names with `with` details). GET /rest/categories.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Entries per page, 1 to 100 (default 50). When is_last_page is false, ask for the next page. |
| lang | string | – | – |
| level | integer | – | – |
| name | string | – | – |
| page | integer | – | Page number, from 1 (default 1). |
| parent_id | integer | – | – |
| type | string | – | – |
| with | array | – | details = names and texts, clients = the stores the category is active in, tags. |
No output schema declared.
No examples provided.
plentymarkets_list_comments ~71
The comments (internal notes) on an order, an order item, a contact or a category. GET /rest/comments/{referenceType}/{referenceValue}.
| Name | Type | Req | Description |
|---|---|---|---|
| reference_id | integer | yes | The id of the order, order item, contact or category. |
| reference_type | string | yes | – |
No output schema declared.
No examples provided.
plentymarkets_list_contacts ~311
List contacts (customers, suppliers, ...). Returns personal data of your customers (names, emails, addresses). Filter by email, name, number, type, postal code or town; `with` adds addresses, options (email, phone), accounts, orderSummary. GET /rest/accounts/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | A date, yyyy-mm-dd. |
| created_before | string | – | A date, yyyy-mm-dd. |
| string | – | An email address. | |
| full_text | string | – | Full text search over the contact data. |
| items_per_page | integer | – | Entries per page, 1 to 100 (default 25). When is_last_page is false, ask for the next page. |
| last_order_after | string | – | A date, yyyy-mm-dd. |
| last_order_before | string | – | A date, yyyy-mm-dd. |
| name | string | – | – |
| number | string | – | The contact number. |
| page | integer | – | Page number, from 1 (default 1). |
| postal_code | string | – | – |
| town | string | – | – |
| type_id | integer | – | Contact type: 1 customer, 2 interested party, 3 sales representative, 4 supplier, 5 manufacturer, 6 partner. |
| updated_after | string | – | A date, yyyy-mm-dd. |
| updated_before | string | – | A date, yyyy-mm-dd. |
| with | array | – | – |
No output schema declared.
No examples provided.
plentymarkets_list_items ~240
List items (the product containers) with filters. Prices, stock, barcodes and SKUs belong to the variations: use plentymarkets_list_variations for those. Returns {page, totalsCount, isLastPage, entries[]}. GET /rest/items.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Item id(s), comma separated. |
| items_per_page | integer | – | Entries per page, 1 to 100 (default 25). When is_last_page is false, ask for the next page. |
| lang | string | – | Language of the texts, a two-letter code (default: the system's). |
| manufacturer_id | integer | – | – |
| name | string | – | Item name (matches the name of the item). |
| page | integer | – | Page number, from 1 (default 1). |
| updated_from | string | – | Only items updated from this day on (yyyy-mm-dd). |
| updated_to | string | – | Only items updated up to this day (yyyy-mm-dd). |
| with | array | – | Related data: itemProperties, itemCrossSelling, variations, itemImages, itemShippingProfiles. |
No output schema declared.
No examples provided.
plentymarkets_list_manufacturers ~98
List the manufacturers (brands) of the items: id, name, address data. GET /rest/items/manufacturers.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Entries per page, 1 to 100 (default 50). When is_last_page is false, ask for the next page. |
| name | string | – | – |
| page | integer | – | Page number, from 1 (default 1). |
No output schema declared.
No examples provided.
plentymarkets_list_order_referrers ~58
The order referrers (sales channels: shop, eBay, Amazon, ...) with their ids, for the referrer_id filter of plentymarkets_list_orders. GET /rest/orders/referrers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plentymarkets_list_order_statuses ~136
The order statuses defined in the system (id and name per language), to translate a statusId. Optionally a range of status ids. GET /rest/orders/statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Entries per page, 1 to 100 (default 50). When is_last_page is false, ask for the next page. |
| language | string | – | Two-letter language code, for example en or de. |
| page | integer | – | Page number, from 1 (default 1). |
| status_id_from | number | – | – |
| status_id_to | number | – | – |
No output schema declared.
No examples provided.
plentymarkets_list_orders ~709
List orders (sales orders, returns, credit notes ...) with filters. Newest first with sort_by createdAt and sort_order desc. Returns {page, totalsCount, isLastPage, entries[]}; each entry has the id, typeId (1 = sales order), statusId, plentyId, createdAt, amounts and the order items unless add_order_items is false. GET /rest/orders.
| Name | Type | Req | Description |
|---|---|---|---|
| add_order_items | boolean | – | Include the order items (default true). false makes the page much smaller. |
| contact_id | integer | – | Only orders of this contact (customer). |
| created_from | string | – | A date (yyyy-mm-dd) or a date-time (2026-10-24T13:33:23+02:00). A bare date means the whole day. |
| created_to | string | – | A date (yyyy-mm-dd) or a date-time (2026-10-24T13:33:23+02:00). A bare date means the whole day. |
| external_order_id | string | – | The order id the marketplace or shop gave the order. |
| included_variation | integer | – | Only orders that contain this variation id. |
| items_per_page | integer | – | Entries per page, 1 to 100 (default 25). When is_last_page is false, ask for the next page. |
| order_ids | string | – | Specific order ids, comma separated. |
| order_type | string | – | Order type id(s), comma separated: 1 sales order, 2 delivery order, 3 returns, 4 credit note, 5 warranty, 6 repair, 7 offer, 8 advance order, 9 multi order, 10 multi credit note, 11 multi delivery, 1… |
| page | integer | – | Page number, from 1 (default 1). |
| paid_from | string | – | A date (yyyy-mm-dd) or a date-time (2026-10-24T13:33:23+02:00). A bare date means the whole day. |
| paid_to | string | – | A date (yyyy-mm-dd) or a date-time (2026-10-24T13:33:23+02:00). A bare date means the whole day. |
| payment_status | string | – | – |
| referrer_id | number | – | Only orders from this order referrer / marketplace (see plentymarkets_list_order_referrers). |
| sort_by | string | – | – |
| sort_order | string | – | – |
| status_from | number | – | Only orders in this status or a higher one (status ids are numbers like 3, 5.1, 7). |
| status_to | number | – | Only orders up to this status (combine with status_from for a range). |
| updated_from | string | – | A date (yyyy-mm-dd) or a date-time (2026-10-24T13:33:23+02:00). A bare date means the whole day. |
| updated_to | string | – | A date (yyyy-mm-dd) or a date-time (2026-10-24T13:33:23+02:00). A bare date means the whole day. |
| with | array | – | Related data to load, for example addresses, comments, payments, documents. |
No output schema declared.
No examples provided.
plentymarkets_list_sales_prices ~122
List the sales price configurations (price types such as retail or purchase price: id, type, names, which stores, countries and currencies they apply to). The prices of a variation: plentymarkets_list_variations with variationSalesPrices. GET /rest/items/sales_prices.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Entries per page, 1 to 100 (default 50). When is_last_page is false, ask for the next page. |
| page | integer | – | Page number, from 1 (default 1). |
No output schema declared.
No examples provided.
plentymarkets_list_stock ~199
List physical stock per variation and warehouse (physical stock, net stock, reserved, reorder level), optionally for one variation or changed since a date. Returns {page, totalsCount, isLastPage, entries[]}. GET /rest/stockmanagement/stock.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Entries per page, 1 to 200 (default 50). When is_last_page is false, ask for the next page. |
| page | integer | – | Page number, from 1 (default 1). |
| sort_by | string | – | – |
| sort_order | string | – | – |
| updated_from | string | – | Only stock changed from this date on. |
| updated_to | string | – | A date (yyyy-mm-dd) or a date-time (2026-10-24T13:33:23+02:00). A bare date means the whole day. |
| variation_id | integer | – | – |
No output schema declared.
No examples provided.
plentymarkets_list_variations ~321
Search variations (the sellable products: number, SKU, barcodes, prices, stock, categories). Filter by item, number, barcode, SKU, active flag, category, warehouse. Use `with` for the related data (variationSalesPrices, variationBarcodes, stock, variationCategories, images ...). GET /rest/items/variations.
| Name | Type | Req | Description |
|---|---|---|---|
| barcode | string | – | – |
| category_id | integer | – | – |
| id | integer | – | One variation id. |
| is_active | boolean | – | – |
| is_main | boolean | – | Only main variations. |
| item_id | integer | – | Only variations of this item. |
| item_name | string | – | – |
| items_per_page | integer | – | Entries per page, 1 to 100 (default 25). When is_last_page is false, ask for the next page. |
| lang | string | – | – |
| manufacturer_id | integer | – | – |
| number_exact | string | – | The exact variation number. |
| number_fuzzy | string | – | Variation numbers that contain this text. |
| page | integer | – | Page number, from 1 (default 1). |
| sku | string | – | – |
| stock_warehouse_id | integer | – | Only variations with physical stock in this warehouse. |
| supplier_id | integer | – | – |
| updated_from | string | – | Only variations updated from this day on (yyyy-mm-dd). |
| updated_to | string | – | Only variations updated up to this day (yyyy-mm-dd). |
| with | array | – | – |
No output schema declared.
No examples provided.
plentymarkets_list_warehouses ~39
List the warehouses (id, name, type, priority, address settings). GET /rest/stockmanagement/warehouses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plentymarkets_update_order_status ~110
WRITE: move an order to another status. This can trigger the event procedures configured in the system (customer emails, stock bookings, documents, shipping), so confirm the target status with the user first (plentymarkets_list_order_statuses has the ids). Only the status is sent. PUT /rest/orders/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | – |
| status_id | number | yes | The target status id, for example 5 or 7.2. |
No output schema declared.
No examples provided.
How do I install the PlentyONE MCP by usefulapi server?
PlentyONE MCP by usefulapi is a hosted endpoint at https://plentymarkets.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 · plentymarkets.usefulapi.io
claude mcp add --transport http io-usefulapi-plentymarkets 'https://plentymarkets.usefulapi.io/mcp'
What is the PlentyONE MCP by usefulapi server?
PlentyONE MCP by usefulapi is listed in the public MCP registry as io.usefulapi/plentymarkets. Review PlentyONE orders, items, stock and contacts; add comments and update order status. This page covers its hosted endpoint (https://plentymarkets.usefulapi.io/mcp).
Is the PlentyONE MCP by usefulapi server safe to use?
PlentyONE 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 PlentyONE MCP by usefulapi server expose?
PlentyONE MCP by usefulapi exposes 18 tools: plentymarkets_list_orders, plentymarkets_get_order, plentymarkets_get_order_status_history, plentymarkets_list_order_statuses, plentymarkets_list_order_referrers, and 13 more. Their descriptions and schemas cost roughly 2,967 tokens of context every time the server is loaded.
Does the PlentyONE MCP by usefulapi server require authentication?
Its publisher declares no required credentials for PlentyONE 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 PlentyONE MCP by usefulapi server still maintained?
PlentyONE 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 PlentyONE MCP by usefulapi server?
VerifyMCP ran 4 checks on PlentyONE 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 PlentyONE 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.