# Inventory Planner MCP by usefulapi (remote · inventory-planner.usefulapi.io)

Read Inventory Planner forecasts, replenishment and purchase orders; create draft purchase orders.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://inventory-planner.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

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

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-inventory-planner": {
      "type": "http",
      "url": "https://inventory-planner.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-10-17 (score 63, +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.

### 2026-10-14 (score 62, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] 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

### 2026-10-13 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 59)

First indexed and scored.

## MCP tools (11)

### `inventoryplanner_list_variants` (~313 tokens)

List variants (forecast and replenishment)

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.

Input parameters:

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

### `inventoryplanner_get_variant` (~75 tokens)

Get variant

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

Input parameters:

- `fields` (string)
- `variant_id` (string, required): Inventory Planner id.

### `inventoryplanner_list_variant_vendors` (~73 tokens)

List a variant's vendors

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.

Input parameters:

- `variant_id` (string, required): Inventory Planner id.

### `inventoryplanner_get_variant_vendor` (~101 tokens)

Get a variant's vendor terms

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

Input parameters:

- `variant_id` (string, required): Inventory Planner id.
- `vendor_id` (string, required): The vendor name in lowercase, as listed by inventoryplanner_list_variant_vendors.

### `inventoryplanner_list_purchase_orders` (~286 tokens)

List purchase orders (and transfers, assembly orders)

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.

Input parameters:

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

### `inventoryplanner_get_purchase_order` (~77 tokens)

Get purchase order

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

Input parameters:

- `fields` (string)
- `purchase_order_id` (string, required): Inventory Planner id.

### `inventoryplanner_list_purchase_order_items` (~128 tokens)

List purchase order line items

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.

Input parameters:

- `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, required): Inventory Planner id.

### `inventoryplanner_get_purchase_order_connections` (~81 tokens)

Get purchase order connection status

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.

Input parameters:

- `purchase_order_id` (string, required): Inventory Planner id.

### `inventoryplanner_get_purchase_order_stock_update` (~107 tokens)

Get purchase order stock update (preview)

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.

Input parameters:

- `for_destination` (boolean): true (default) = the destination warehouse; false = the source warehouse (transfers only).
- `purchase_order_id` (string, required): Inventory Planner id.

### `inventoryplanner_create_draft_purchase_order` (~200 tokens)

Create a draft purchase order

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

Input parameters:

- `currency` (string)
- `expected_date` (string): Expected delivery date, e.g. 2026-11-15 or 2026-11-15T10:00:00+01:00.
- `items` (array, required)
- `notes` (string)
- `reference` (string): Your PO reference.
- `vendor` (string, required): The vendor name, as it appears in Inventory Planner.
- `warehouse` (string, required): The destination warehouse, as it appears in Inventory Planner.

### `inventoryplanner_update_draft_purchase_order` (~142 tokens)

Edit a draft purchase order

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.

Input parameters:

- `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, required): Inventory Planner id.
- `reference` (string)

## Diagnostics

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

## Score history

- 2026-10-17: 63
- 2026-10-16: 62
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 59
- 2026-10-12: 59

## Common questions

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

## Links

- Remote endpoint: https://inventory-planner.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/inventory-planner/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-inventory-planner/inventory-planner.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-inventory-planner/inventory-planner.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-inventory-planner/inventory-planner