Inventory Planner MCP by usefulapi
REMOTE · INVENTORY-PLANNER.USEFULAPI.IO
Read Inventory Planner forecasts, replenishment and purchase orders; create draft purchase orders.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 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 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 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
- 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 & 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1789 tokens (~162/item across 11 items; 11 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 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
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.
- 17 Oct 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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
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 17 Oct 2026 · Probed https://inventory-planner.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 inventory-planner.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 | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://inventory-planner.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://inventory-planner.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://inventory-planner.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://inventory-planner.usefulapi.io/mcp |
| Authorisation server | https://inventory-planner.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://inventory-planner.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/inventory-planner/ |
| http (plaintext) | http://inventory-planner.usefulapi.io/mcp | Inconclusive | 302 | http://inventory-planner.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 →
inventoryplanner_create_draft_purchase_order Create a draft purchase order ~200
WRITE: create a purchase order with status "draft" in Inventory Planner (POST /api/v1/purchase-orders). A draft is only a plan inside Inventory Planner: it is NOT sent to the vendor, NOT saved to any connected system and moves no stock or money. Purchase orders only (no transfers or assembly orders). Each line item is a variant id plus the quantity to order (replenishment).
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| expected_date | string | – | Expected delivery date, e.g. 2026-11-15 or 2026-11-15T10:00:00+01:00. |
| items | array | yes | – |
| notes | string | – | – |
| reference | string | – | Your PO reference. |
| vendor | string | yes | The vendor name, as it appears in Inventory Planner. |
| warehouse | string | yes | The destination warehouse, as it appears in Inventory Planner. |
No output schema declared.
No examples provided.
inventoryplanner_get_purchase_order Get purchase order ~77
One purchase order, transfer or assembly order by id, with its header fields (reference, status, vendor, warehouse, dates, addresses, totals, notes) and line items. GET /api/v1/purchase-orders/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | – |
| purchase_order_id | string | yes | Inventory Planner id. |
No output schema declared.
No examples provided.
inventoryplanner_get_purchase_order_connections Get purchase order connection status ~81
Whether and how a purchase order was saved to connected systems (ERP, accounting): per connection the status (success, error, run, queued), save_po flag and the PO's id and reference there. Read-only. GET /api/v1/purchase-orders/{id}/connections.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_order_id | string | yes | Inventory Planner id. |
No output schema declared.
No examples provided.
inventoryplanner_get_purchase_order_stock_update Get purchase order stock update (preview) ~107
The stock updates a purchase order has computed: per warehouse (wh) the items with stock_before, delta and error. for_destination false reads the source warehouse of a transfer. Read-only: nothing is pushed. GET /api/v1/purchase-orders/{id}/stock-update.
| Name | Type | Req | Description |
|---|---|---|---|
| for_destination | boolean | – | true (default) = the destination warehouse; false = the source warehouse (transfers only). |
| purchase_order_id | string | yes | Inventory Planner id. |
No output schema declared.
No examples provided.
inventoryplanner_get_variant Get variant ~75
One variant by its Inventory Planner id, with the metrics named in `fields` (default: id,sku,lead_time,review_period,replenishment,oos,under_value). GET /api/v1/variants/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | – |
| variant_id | string | yes | Inventory Planner id. |
No output schema declared.
No examples provided.
inventoryplanner_get_variant_vendor Get a variant's vendor terms ~101
One vendor's terms for a variant: cost_price, landing_cost_price, vendor_reference, vendor_name, vendor_packaging (MOQ), uom_ordering. vendor_id is the vendor name in lowercase. GET /api/v1/variants/{id}/vendors/{vendor_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| variant_id | string | yes | Inventory Planner id. |
| vendor_id | string | yes | The vendor name in lowercase, as listed by inventoryplanner_list_variant_vendors. |
No output schema declared.
No examples provided.
inventoryplanner_list_purchase_order_items List purchase order line items ~128
The line items of a purchase order: variant id, sku, title, ordered quantity (replenishment), received quantity and received_history, cost price, tax, discount and stock snapshots. GET /api/v1/purchase-orders/{id}/items.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | – |
| limit | integer | – | Results per page, 1-1000 (default 25). |
| page | integer | – | Page number, counting from 0 (default 0). Pass the previous reply's next_page. |
| purchase_order_id | string | yes | Inventory Planner id. |
No output schema declared.
No examples provided.
inventoryplanner_list_purchase_orders List purchase orders (and transfers, assembly orders) ~286
List stock orders: purchase orders, transfers and assembly orders (the `type` field is "po"/empty, "transfer" or "assembly"). Filter with `filters`, e.g. {"status": "OPEN", "vendor": "Acme", "expected_date_lt": "2026-11-01"}. Default fields: id,reference,status,type,vendor,warehouse,source,created_date,expected_date,received_date,currency,total,total_ordered,total_received. GET /api/v1/purchase-orders.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | – |
| filters | object | – | Filters, as {"<field>": value} or {"<field>_<operator>": value}. Operators: eq (default), eqi (case-insensitive), ne, gt, gte, lt, lte, range ("5-10"), match (regex), in (comma-separated). Example: {… |
| limit | integer | – | Results per page, 1-1000 (default 25). |
| page | integer | – | Page number, counting from 0 (default 0). Pass the previous reply's next_page. |
| sort | object | – | Sort by one field, e.g. {"field": "under_value", "direction": "desc"}. |
No output schema declared.
No examples provided.
inventoryplanner_list_variant_vendors List a variant's vendors ~73
The vendors a variant can be ordered from, with cost_price, landing_cost_price, vendor_reference (vendor SKU), vendor_name, vendor_packaging (MOQ) and uom_ordering. GET /api/v1/variants/{id}/vendors.
| Name | Type | Req | Description |
|---|---|---|---|
| variant_id | string | yes | Inventory Planner id. |
No output schema declared.
No examples provided.
inventoryplanner_list_variants List variants (forecast and replenishment) ~313
List product variants with Inventory Planner's computed metrics (forecast, replenishment, days to sell out, lost revenue, lead time, review period and ~200 more). Always pass `fields` to pick the metrics you need (default: id,sku,lead_time,review_period,replenishment,oos,under_value; oos = forecasted days to sell out, under_value = forecasted lost revenue, replenishment = recommended order quantity). Use `filters` and `sort` for questions like "which SKUs need reordering". Removed variants are excluded unless include_removed. GET /api/v1/variants.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | – |
| filters | object | – | Filters, as {"<field>": value} or {"<field>_<operator>": value}. Operators: eq (default), eqi (case-insensitive), ne, gt, gte, lt, lte, range ("5-10"), match (regex), in (comma-separated). Example: {… |
| include_removed | boolean | – | – |
| limit | integer | – | Results per page, 1-1000 (default 25). |
| page | integer | – | Page number, counting from 0 (default 0). Pass the previous reply's next_page. |
| sort | object | – | Sort by one field, e.g. {"field": "under_value", "direction": "desc"}. |
No output schema declared.
No examples provided.
inventoryplanner_update_draft_purchase_order Edit a draft purchase order ~142
WRITE: change the reference, expected date or notes of a purchase order that is still a draft (PATCH /api/v1/purchase-orders/{id}). The order is read first and refused unless its status is "draft". It never changes the status, sends the order, or touches line items or received quantities.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_date | string | – | Expected delivery date, e.g. 2026-11-15 or 2026-11-15T10:00:00+01:00. |
| notes | string | – | – |
| purchase_order_id | string | yes | Inventory Planner id. |
| reference | string | – | – |
No output schema declared.
No examples provided.
How do I install the Inventory Planner MCP by usefulapi server?
Inventory Planner MCP by usefulapi is a hosted endpoint at https://inventory-planner.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 · inventory-planner.usefulapi.io
claude mcp add --transport http io-usefulapi-inventory-planner 'https://inventory-planner.usefulapi.io/mcp'
What is the Inventory Planner MCP by usefulapi server?
Inventory Planner MCP by usefulapi is listed in the public MCP registry as io.usefulapi/inventory-planner. Read Inventory Planner forecasts, replenishment and purchase orders; create draft purchase orders. This page covers its hosted endpoint (https://inventory-planner.usefulapi.io/mcp).
Is the Inventory Planner MCP by usefulapi server safe to use?
Inventory Planner MCP by usefulapi scores 63 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 Inventory Planner MCP by usefulapi server expose?
Inventory Planner MCP by usefulapi exposes 11 tools: inventoryplanner_list_variants, inventoryplanner_get_variant, inventoryplanner_list_variant_vendors, inventoryplanner_get_variant_vendor, inventoryplanner_list_purchase_orders, and 6 more. Their descriptions and schemas cost roughly 1,583 tokens of context every time the server is loaded.
Does the Inventory Planner MCP by usefulapi server require authentication?
Yes. Inventory Planner MCP by usefulapi 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 Inventory Planner MCP by usefulapi server still maintained?
Inventory Planner MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.