# Extensiv MCP by usefulapi (remote · extensiv.usefulapi.io)

Read Extensiv warehouse records, create outbound orders and cancel eligible orders.

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

## Components

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

## Channel facts

- Endpoint: `https://extensiv.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.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 Extensiv MCP by usefulapi server?

Extensiv MCP by usefulapi is a hosted endpoint at https://extensiv.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-extensiv 'https://extensiv.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-extensiv": {
      "type": "http",
      "url": "https://extensiv.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] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

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

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 65, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “check_stock_by_facility”
- [functional] New prompt “inspect_inbound_receipts”
- [functional] New prompt “review_outbound_orders”
- [functional] New prompt “submit_an_outbound_order”
- [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.1 → 1.1.0

### 2026-10-30 (score 62)

First indexed and scored.

## MCP tools (16)

### `extensiv_list_facilities` (~41 tokens)

List facilities

List the warehouse's facilities with their ids and properties (facility ids are needed for orders, stock details and receivers). GET /properties/facilities.

### `extensiv_list_carriers` (~45 tokens)

List carriers and services

List the carriers with their shipment services (modes) and billing codes, the values an order's routingInfo and billingCode must use. GET /properties/carriers.

### `extensiv_list_customers` (~170 tokens)

List customers

List the warehouse's customers (the companies whose goods it stores), with their customer ids. GET /customers.

Input parameters:

- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).
- `rql` (string): Optional RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00;readonly.processDate=lt=2026-10-02T00:00:00` (';' = and).
- `sort` (string): Optional sort expression, for example `ReadOnly.CreationDate`.

### `extensiv_get_customer` (~48 tokens)

Get a customer

One customer by customer id: company info, contacts and settings. GET /customers/{customer_id}.

Input parameters:

- `customer_id` (string, required): The customer id (from extensiv_list_customers).

### `extensiv_list_items` (~207 tokens)

List a customer's items

List the items (SKUs) of one customer, with item ids, descriptions and units. Filter with rql, for example `sku==ABC-1`. GET /customers/{customer_id}/items.

Input parameters:

- `customer_id` (string, required): The customer id (from extensiv_list_customers).
- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).
- `rql` (string): Optional RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00;readonly.processDate=lt=2026-10-02T00:00:00` (';' = and).
- `sort` (string): Optional sort expression, for example `ReadOnly.CreationDate`.

### `extensiv_list_orders` (~301 tokens)

List orders

List outbound orders matching an RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00` (orders closed after that time). Use detail=OrderItems to include the line items. Orders carry the ship-to name, address and contact details (personal data). GET /orders.

Input parameters:

- `detail` (string): Order-level detail, comma-delimited: None (default), OrderItems, BillingDetails, SavedElements, Packages, Contacts, ProposedBilling, OutboundSerialNumbers, SmallParcel, All.
- `itemdetail` (string): Item-level detail, comma-delimited: None (default), SavedElements, Allocations, AllocationsWithDetail, All.
- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).
- `rql` (string): Optional RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00;readonly.processDate=lt=2026-10-02T00:00:00` (';' = and).
- `sort` (string): Optional sort expression, for example `ReadOnly.CreationDate`.

### `extensiv_get_order` (~138 tokens)

Get an order

One order by its transaction id (the order id from extensiv_list_orders): status, ship-to, routing, and with detail=OrderItems the lines. GET /orders/{transaction_id}.

Input parameters:

- `detail` (string): Order-level detail, comma-delimited: None (default), OrderItems, BillingDetails, SavedElements, Packages, Contacts, ProposedBilling, OutboundSerialNumbers, SmallParcel, All.
- `itemdetail` (string): Item-level detail, comma-delimited: None (default), SavedElements, Allocations, AllocationsWithDetail, All.
- `order_id` (string, required): The order's transaction id.

### `extensiv_list_stock_summaries` (~170 tokens)

List stock summaries

Inventory totals per item and facility (on hand, allocated, available). Filter with rql, for example `ItemId==123` or a customer filter. GET /inventory/stocksummaries.

Input parameters:

- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).
- `rql` (string): Optional RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00;readonly.processDate=lt=2026-10-02T00:00:00` (';' = and).

### `extensiv_list_inventory` (~160 tokens)

List inventory details

Inventory detail lines (location, lot, quantities). Filter with rql, for example `itemIdentifier.sku==SF-Box-DG`. GET /inventory.

Input parameters:

- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).
- `rql` (string): Optional RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00;readonly.processDate=lt=2026-10-02T00:00:00` (';' = and).

### `extensiv_list_stock_details` (~127 tokens)

List stock details

All inventory of one customer in one facility, broken out by receive item (lot number, serial number and other track-by values). Both ids are required. GET /inventory/stockdetails.

Input parameters:

- `customer_id` (string, required): The customer id.
- `facility_id` (string, required): The facility id (from extensiv_list_facilities).
- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).

### `extensiv_list_receivers` (~220 tokens)

List receivers

List inbound receivers (receipts of goods), for example `ReadOnly.CustomerIdentifier.id==1`. Use detail=ReceiveItems for the lines. GET /inventory/receivers.

Input parameters:

- `detail` (string): Receiver-level detail, comma-delimited: None (default), ReceiveItems, BillingDetails, SavedElements, ProposedBilling, All.
- `itemdetail` (string): Item-level detail, comma-delimited: None (default), SavedElements, All.
- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).
- `rql` (string): Optional RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00;readonly.processDate=lt=2026-10-02T00:00:00` (';' = and).

### `extensiv_get_receiver` (~47 tokens)

Get a receiver

One receiver by its transaction id. GET /inventory/receivers/{transaction_id}.

Input parameters:

- `receiver_id` (string, required): The receiver's transaction id (from extensiv_list_receivers).

### `extensiv_list_receiver_items` (~76 tokens)

List a receiver's items

The line items of one receiver, with item details. GET /inventory/receivers/{transaction_id}/items.

Input parameters:

- `detail` (string): Detail level, comma-delimited: None (default), SavedElements, All.
- `receiver_id` (string, required): The receiver's transaction id (from extensiv_list_receivers).

### `extensiv_list_purchase_orders` (~170 tokens)

List purchase orders

List inbound purchase orders per customer. Filter with rql, sort with sort. GET /inventory/pos.

Input parameters:

- `pgnum` (integer): Page number, from 1 (default 1). Use totalResults and _links.next of the previous reply.
- `pgsiz` (integer): Page size (default 100, max 500).
- `rql` (string): Optional RQL filter, for example `ReadOnly.CustomerIdentifier.id==1` or `readonly.processDate=gt=2026-10-01T00:00:00;readonly.processDate=lt=2026-10-02T00:00:00` (';' = and).
- `sort` (string): Optional sort expression, for example `ReadOnly.CreationDate`.

### `extensiv_create_order` (~292 tokens)

Create an order

WRITE: submit a new outbound order for a customer and facility (the warehouse will pick and ship it). Not idempotent: calling twice creates two orders, so check extensiv_list_orders for the reference_num first. Needs ids from extensiv_list_customers, extensiv_list_facilities and SKUs from extensiv_list_items; billing_code, carrier and mode are required by Extensiv and must come from extensiv_list_carriers. POST /orders.

Input parameters:

- `account` (string): The shipper account number for third-party or collect billing.
- `billing_code` (string, required): Freight billing code as listed for the carrier by extensiv_list_carriers (billingCodes), for example Prepaid or BillThirdParty.
- `carrier` (string, required): Carrier name, for example UPS (from extensiv_list_carriers).
- `customer_id` (string, required): The customer id the order is for.
- `facility_id` (string, required): The facility id that fulfils it.
- `items` (array, required): The order lines.
- `mode` (string, required): The carrier's service mode code (from extensiv_list_carriers).
- `notes` (string): Warehouse instructions.
- `reference_num` (string, required): Your reference number for the order (for example a PO or web-shop order number).
- `ship_to` (object, required): The ship-to address.
- `shipping_notes` (string): Carrier-specific shipping instructions.

### `extensiv_cancel_order` (~136 tokens)

Cancel an order

WRITE: cancel one order by transaction id, with a reason and an optional cancellation fee. This cannot be undone; the order must be in a state the warehouse can still cancel (otherwise Extensiv answers with an error). The tool first reads the order to get the ETag Extensiv requires (If-Match). POST /orders/{transaction_id}/canceler.

Input parameters:

- `charge` (number): Cancellation fee to bill, 0 (default) if none.
- `order_id` (string, required): The order's transaction id (from extensiv_list_orders).
- `reason` (string, required): Why the order is cancelled.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-extensiv/extensiv#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
- 2026-10-30: 62

## Common questions

### What is the Extensiv MCP by usefulapi server?

Extensiv MCP by usefulapi is listed in the public MCP registry as io.usefulapi/extensiv. Read Extensiv warehouse records, create outbound orders and cancel eligible orders. This page covers its hosted endpoint (https://extensiv.usefulapi.io/mcp).

### Is the Extensiv MCP by usefulapi server safe to use?

Extensiv 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 Extensiv MCP by usefulapi server expose?

Extensiv MCP by usefulapi exposes 16 tools: extensiv_list_facilities, extensiv_list_carriers, extensiv_list_customers, extensiv_get_customer, extensiv_list_items, and 11 more. Their descriptions and schemas cost roughly 2,348 tokens of context every time the server is loaded.

### Does the Extensiv MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Extensiv 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 Extensiv MCP by usefulapi server still maintained?

Extensiv 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 Extensiv MCP by usefulapi server?

VerifyMCP ran 4 checks on Extensiv 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 Extensiv 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://extensiv.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/extensiv/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-extensiv/extensiv.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-extensiv/extensiv/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-extensiv/extensiv.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-extensiv/extensiv