# SOS Inventory MCP by usefulapi (remote · sos-inventory.usefulapi.io)

Read SOS Inventory stock and orders; create customers, items and purchase or sales orders.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://sos-inventory.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.3`

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

- **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 SOS Inventory MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-sos-inventory": {
      "type": "http",
      "url": "https://sos-inventory.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-02 (score 18, −47)

- [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 65, +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 64, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “check_stock_availability”
- [functional] New prompt “prepare_a_purchase_order”
- [functional] New prompt “review_outstanding_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

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

First indexed and scored.

## MCP tools (19)

### `sosinventory_list_items` (~309 tokens)

List items

List or search inventory items (products, assemblies, services...) with SKU, type, quantities (onhand, available, on sales/purchase orders) and prices. Filter by free text, SKU, category, type, tags, ids or update time; pass location to see quantities at one location. GET /api/v2/item.

Input parameters:

- `category` (string): Category name.
- `ids` (array): Only these item ids.
- `location` (string): Location name: quantities then reflect that location.
- `max_results` (integer): Rows per call, 1-200 (default 50).
- `query` (string): Free-text search over item name, SKU, description and similar fields.
- `sku` (string): Exact SKU.
- `start` (integer): 1-based row number to start at (default 1). Pass next_start from the previous reply to read the next page.
- `summary` (boolean): true (default) = summary records without line items and long sub-lists; false = full records.
- `tags` (string): Comma-separated tags; records matching them are returned.
- `type` (string): Item type: "Inventory Item", "Non-inventory", "Category", "Expense", "Assembly", "Kit", "Service", "Labor", "Overhead" or "Other".
- `updated_since` (string): Only items created or updated since this local date-time (YYYY-MM-DDTHH:MM:SS).

### `sosinventory_get_item` (~78 tokens)

Get item

One item by id with all fields: quantities, prices, accounts, vendor, category, units of measure, price tiers, custom fields. GET /api/v2/item/{id}.

Input parameters:

- `id` (integer, required): SOS item id (from sosinventory_list_items).
- `location` (string): Location name: quantities then reflect that location.

### `sosinventory_get_item_bom` (~52 tokens)

Get item bill of materials

The bill of materials of an assembly item: component items, quantities and costs. GET /api/v2/item/{id}/bom.

Input parameters:

- `id` (integer, required): SOS item id of the assembly.

### `sosinventory_list_customers` (~217 tokens)

List customers

List or search customers with contact details, billing/shipping addresses, terms, sales rep and credit-hold flag. Filter by name/notes text, name, email or update time. GET /api/v2/customer.

Input parameters:

- `email` (string): Match on the customer email.
- `max_results` (integer): Rows per call, 1-200 (default 50).
- `name` (string): Match on the customer name or full name.
- `query` (string): Free-text search over the customer name, full name and notes (use `email` for an email lookup).
- `start` (integer): 1-based row number to start at (default 1). Pass next_start from the previous reply to read the next page.
- `summary` (boolean): true (default) = summary records without line items and long sub-lists; false = full records.
- `updated_since` (string): Only customers created or updated since this local date-time (YYYY-MM-DDTHH:MM:SS).

### `sosinventory_get_customer` (~56 tokens)

Get customer

One customer by id with all fields (addresses, contact, terms, price tier, custom fields). GET /api/v2/customer/{id}.

Input parameters:

- `id` (integer, required): SOS customer id (from sosinventory_list_customers).

### `sosinventory_list_vendors` (~175 tokens)

List vendors

List or search vendors (suppliers) by name or notes, with contact details, address, terms and account number. GET /api/v2/vendor.

Input parameters:

- `max_results` (integer): Rows per call, 1-200 (default 50).
- `query` (string): Free-text search over the vendor name and notes (SOS has no email or phone filter for vendors).
- `start` (integer): 1-based row number to start at (default 1). Pass next_start from the previous reply to read the next page.
- `summary` (boolean): true (default) = summary records without line items and long sub-lists; false = full records.
- `updated_since` (string): Only vendors created or updated since this local date-time (YYYY-MM-DDTHH:MM:SS).

### `sosinventory_get_vendor` (~44 tokens)

Get vendor

One vendor by id with all fields. GET /api/v2/vendor/{id}.

Input parameters:

- `id` (integer, required): SOS vendor id (from sosinventory_list_vendors).

### `sosinventory_list_sales_orders` (~277 tokens)

List sales orders

List or search sales orders with customer, dates, totals, order stage, channel and (with summary=false) line items with shipped/invoiced quantities. GET /api/v2/salesorder.

Input parameters:

- `channel` (string): Channel name.
- `from` (string): Transaction date on or after this (YYYY-MM-DDTHH:MM:SS). `to` is optional.
- `location` (string): Location name.
- `max_results` (integer): Rows per call, 1-200 (default 50).
- `order_stage` (string): Order stage name.
- `query` (string): Free-text search over number, customer/vendor name, reference fields and similar.
- `start` (integer): 1-based row number to start at (default 1). Pass next_start from the previous reply to read the next page.
- `status` (string): Open or closed transactions.
- `summary` (boolean): true (default) = summary records without line items and long sub-lists; false = full records.
- `to` (string): Transaction date on or before this (YYYY-MM-DDTHH:MM:SS). `from` is optional.
- `updated_since` (string): Only transactions created or updated since this local date-time (YYYY-MM-DDTHH:MM:SS).

### `sosinventory_get_sales_order` (~57 tokens)

Get sales order

One sales order by id with all fields and line items. GET /api/v2/salesorder/{id}.

Input parameters:

- `id` (integer, required): SOS sales order id (from sosinventory_list_sales_orders; not the order number).

### `sosinventory_list_purchase_orders` (~244 tokens)

List purchase orders

List or search purchase orders with vendor, dates, expected receipt date, totals and (with summary=false) line items with received quantities. GET /api/v2/purchaseorder.

Input parameters:

- `from` (string): Transaction date on or after this (YYYY-MM-DDTHH:MM:SS). `to` is optional.
- `max_results` (integer): Rows per call, 1-200 (default 50).
- `query` (string): Free-text search over number, customer/vendor name, reference fields and similar.
- `start` (integer): 1-based row number to start at (default 1). Pass next_start from the previous reply to read the next page.
- `status` (string): Open or closed transactions.
- `summary` (boolean): true (default) = summary records without line items and long sub-lists; false = full records.
- `to` (string): Transaction date on or before this (YYYY-MM-DDTHH:MM:SS). `from` is optional.
- `updated_since` (string): Only transactions created or updated since this local date-time (YYYY-MM-DDTHH:MM:SS).

### `sosinventory_get_purchase_order` (~57 tokens)

Get purchase order

One purchase order by id with all fields and line items. GET /api/v2/purchaseorder/{id}.

Input parameters:

- `id` (integer, required): SOS purchase order id (from sosinventory_list_purchase_orders; not the PO number).

### `sosinventory_list_transactions` (~397 tokens)

List other transactions

List any SOS transaction type: invoices, estimates, sales receipts, item receipts, shipments, pick tickets, work orders, builds, adjustments, transfers, RMAs, returns, returns to vendor, rentals, rental returns and processes. Filters: query, date range, updated_since; status (open/closed; invoices voided/notvoided; estimates accepted/pending/closed/rejected; not available for transfers, shipments, builds, returns, item receipts, processes); location (transfers, rentals and rental returns take from_location/to_location instead). GET /api/v2/{type}.

Input parameters:

- `from` (string): Transaction date on or after this (YYYY-MM-DDTHH:MM:SS). `to` is optional.
- `from_location` (string): Transfers, rentals, rental returns: the source location name.
- `location` (string): Location name.
- `max_results` (integer): Rows per call, 1-200 (default 50).
- `query` (string): Free-text search over number, customer/vendor name, reference fields and similar.
- `start` (integer): 1-based row number to start at (default 1). Pass next_start from the previous reply to read the next page.
- `status` (string): Status filter; the allowed values depend on the type (see the tool description).
- `summary` (boolean): true (default) = summary records without line items and long sub-lists; false = full records.
- `to` (string): Transaction date on or before this (YYYY-MM-DDTHH:MM:SS). `from` is optional.
- `to_location` (string): Transfers, rentals, rental returns: the destination location name.
- `type` (string, required): Transaction type (the API endpoint name).
- `updated_since` (string): Only transactions created or updated since this local date-time (YYYY-MM-DDTHH:MM:SS).

### `sosinventory_get_transaction` (~65 tokens)

Get transaction

One transaction of any type by id, with all fields and line items. GET /api/v2/{type}/{id}.

Input parameters:

- `id` (integer, required): SOS record id (from sosinventory_list_transactions).
- `type` (string, required): Transaction type (the API endpoint name).

### `sosinventory_list_reference_data` (~196 tokens)

List reference data

List a configuration or reference table: locations, channels, classes, departments, payment terms, tax codes, sales reps, ship methods, payment methods, priorities, order stages, price tiers, units of measure, users (id, name, email), accounts, custom fields, warranties, bins, workers, work centers, jobs, lots or serial numbers. Use it to find the ids and names that the create tools reference. GET /api/v2/{type}.

Input parameters:

- `max_results` (integer): Rows per call, 1-200 (default 50).
- `query` (string): Free-text filter (supported by some tables, e.g. job, lot, serial).
- `start` (integer): 1-based row number to start at (default 1). Pass next_start from the previous reply to read the next page.
- `type` (string, required): Which table to list (the API endpoint name).

### `sosinventory_create_customer` (~157 tokens)

Create customer

WRITE: creates a new customer record in SOS Inventory. Only name is required. Check sosinventory_list_customers first so you do not create a duplicate. POST /api/v2/customer.

Input parameters:

- `billing` (object): Billing address.
- `company_name` (string)
- `email` (string)
- `name` (string, required): Customer name (how it is looked up in SOS).
- `notes` (string): Internal notes (not shown to the customer).
- `phone` (string)
- `sales_rep` (object): Sales rep (type=salesrep).
- `terms` (object): Payment terms, e.g. {name: 'Net 30'} (see sosinventory_list_reference_data type=terms).

### `sosinventory_create_vendor` (~132 tokens)

Create vendor

WRITE: creates a new vendor (supplier) record in SOS Inventory. Only name is required. Check sosinventory_list_vendors first to avoid a duplicate. POST /api/v2/vendor.

Input parameters:

- `account_number` (string): Your account number with this vendor.
- `address` (object): Vendor address.
- `company_name` (string)
- `email` (string)
- `name` (string, required): Vendor name (how it is looked up in SOS).
- `notes` (string): Internal notes.
- `phone` (string)
- `terms` (object): Payment terms (type=terms).

### `sosinventory_create_item` (~250 tokens)

Create item

WRITE: creates a new inventory item. Optionally books initial stock: SOS then creates an inventory adjustment for the quantity at the given location. Item names must be unique within their category: check sosinventory_list_items first. POST /api/v2/item.

Input parameters:

- `barcode` (string)
- `base_sales_price` (number): Sales price per unit.
- `category` (object): Existing category (a category cannot be created here).
- `description` (string)
- `initial_location` (string): Location name that receives the opening stock (type=location).
- `initial_quantity` (number): Opening stock. Needs initial_location; SOS books an adjustment for it.
- `initial_quantity_date` (string): Date of the opening stock (YYYY-MM-DDTHH:MM:SS).
- `initial_value` (number): Total value of the opening stock.
- `name` (string, required): Item name.
- `purchase_cost` (number): Purchase cost per unit.
- `reorder_point` (number)
- `sku` (string)
- `taxable` (boolean)
- `type` (string): Item type (SOS's default applies when omitted).
- `vendor` (object): Default vendor.

### `sosinventory_create_sales_order` (~207 tokens)

Create sales order

WRITE: creates a new sales order for an EXISTING customer with line items for existing items (a customer or item cannot be created inside an order: use the create tools first). The order number is assigned automatically (SOS auto-numbering) unless you pass one. Confirm the customer, items, quantities and prices with the user before calling. POST /api/v2/salesorder.

Input parameters:

- `comment` (string): Internal comment (not shown to the customer).
- `customer` (object, required): Existing customer (sosinventory_list_customers).
- `customer_message` (string): Message shown to the customer.
- `customer_po` (string): Customer purchase order reference.
- `date` (string): Order date (YYYY-MM-DDTHH:MM:SS); defaults to now in SOS.
- `lines` (array, required): Order lines.
- `location` (object): Location (type=location).
- `number` (string): Order number; leave out for SOS's automatic numbering.

### `sosinventory_create_purchase_order` (~196 tokens)

Create purchase order

WRITE: creates a new purchase order to an EXISTING vendor with line items for existing items. The PO number is assigned automatically unless you pass one. Confirm the vendor, items, quantities and costs with the user before calling. POST /api/v2/purchaseorder.

Input parameters:

- `comment` (string): Internal comment.
- `date` (string): Order date (YYYY-MM-DDTHH:MM:SS); defaults to now in SOS.
- `expected_date` (string): Expected receipt date (YYYY-MM-DDTHH:MM:SS).
- `lines` (array, required): PO lines (unit_price = purchase cost per unit).
- `location` (object): Location that receives the goods (type=location).
- `number` (string): PO number; leave out for automatic numbering.
- `vendor` (object, required): Existing vendor (sosinventory_list_vendors).
- `vendor_message` (string): Message to the vendor.

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 65
- 2026-10-31: 64
- 2026-10-30: 61

## Common questions

### What is the SOS Inventory MCP by usefulapi server?

SOS Inventory MCP by usefulapi is listed in the public MCP registry as io.usefulapi/sos-inventory. Read SOS Inventory stock and orders; create customers, items and purchase or sales orders. This page covers its hosted endpoint (https://sos-inventory.usefulapi.io/mcp).

### Is the SOS Inventory MCP by usefulapi server safe to use?

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

SOS Inventory MCP by usefulapi exposes 19 tools: sosinventory_list_items, sosinventory_get_item, sosinventory_get_item_bom, sosinventory_list_customers, sosinventory_get_customer, and 14 more. Their descriptions and schemas cost roughly 3,166 tokens of context every time the server is loaded.

### Does the SOS Inventory MCP by usefulapi server require authentication?

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

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

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