Extensiv MCP by usefulapi
REMOTE · EXTENSIV.USEFULAPI.IO
Read Extensiv warehouse records, create outbound orders and cancel eligible orders.
Available components
Last scanned (4 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +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.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- 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 functional
- 30 Oct 26 62
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 6 Nov 2026 · Probed https://extensiv.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 extensiv.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://extensiv.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/extensiv/ |
| http (plaintext) | http://extensiv.usefulapi.io/mcp | Inconclusive | 302 | http://extensiv.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 →
extensiv_cancel_order Cancel an order ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| charge | number | – | Cancellation fee to bill, 0 (default) if none. |
| order_id | string | yes | The order's transaction id (from extensiv_list_orders). |
| reason | string | yes | Why the order is cancelled. |
No output schema declared.
No examples provided.
extensiv_create_order Create an order ~292
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | The shipper account number for third-party or collect billing. |
| billing_code | string | yes | Freight billing code as listed for the carrier by extensiv_list_carriers (billingCodes), for example Prepaid or BillThirdParty. |
| carrier | string | yes | Carrier name, for example UPS (from extensiv_list_carriers). |
| customer_id | string | yes | The customer id the order is for. |
| facility_id | string | yes | The facility id that fulfils it. |
| items | array | yes | The order lines. |
| mode | string | yes | The carrier's service mode code (from extensiv_list_carriers). |
| notes | string | – | Warehouse instructions. |
| reference_num | string | yes | Your reference number for the order (for example a PO or web-shop order number). |
| ship_to | object | yes | The ship-to address. |
| shipping_notes | string | – | Carrier-specific shipping instructions. |
No output schema declared.
No examples provided.
extensiv_get_customer Get a customer ~48
One customer by customer id: company info, contacts and settings. GET /customers/{customer_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id (from extensiv_list_customers). |
No output schema declared.
No examples provided.
extensiv_get_order Get an order ~138
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The order's transaction id. |
No output schema declared.
No examples provided.
extensiv_get_receiver Get a receiver ~47
One receiver by its transaction id. GET /inventory/receivers/{transaction_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| receiver_id | string | yes | The receiver's transaction id (from extensiv_list_receivers). |
No output schema declared.
No examples provided.
extensiv_list_carriers List carriers and services ~45
List the carriers with their shipment services (modes) and billing codes, the values an order's routingInfo and billingCode must use. GET /properties/carriers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
extensiv_list_customers List customers ~170
List the warehouse's customers (the companies whose goods it stores), with their customer ids. GET /customers.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
extensiv_list_facilities List facilities ~41
List the warehouse's facilities with their ids and properties (facility ids are needed for orders, stock details and receivers). GET /properties/facilities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
extensiv_list_inventory List inventory details ~160
Inventory detail lines (location, lot, quantities). Filter with rql, for example `itemIdentifier.sku==SF-Box-DG`. GET /inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
extensiv_list_items List a customer's items ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | 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`. |
No output schema declared.
No examples provided.
extensiv_list_orders List orders ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
extensiv_list_purchase_orders List purchase orders ~170
List inbound purchase orders per customer. Filter with rql, sort with sort. GET /inventory/pos.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
extensiv_list_receiver_items List a receiver's items ~76
The line items of one receiver, with item details. GET /inventory/receivers/{transaction_id}/items.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Detail level, comma-delimited: None (default), SavedElements, All. |
| receiver_id | string | yes | The receiver's transaction id (from extensiv_list_receivers). |
No output schema declared.
No examples provided.
extensiv_list_receivers List receivers ~220
List inbound receivers (receipts of goods), for example `ReadOnly.CustomerIdentifier.id==1`. Use detail=ReceiveItems for the lines. GET /inventory/receivers.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
extensiv_list_stock_details List stock details ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | The customer id. |
| facility_id | string | yes | 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). |
No output schema declared.
No examples provided.
extensiv_list_stock_summaries List stock summaries ~170
Inventory totals per item and facility (on hand, allocated, available). Filter with rql, for example `ItemId==123` or a customer filter. GET /inventory/stocksummaries.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
remote · extensiv.usefulapi.io
claude mcp add --transport http io-usefulapi-extensiv 'https://extensiv.usefulapi.io/mcp'
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.