SOS Inventory MCP by usefulapi
REMOTE · SOS-INVENTORY.USEFULAPI.IO
Read SOS Inventory stock and orders; create customers, items and purchase or sales orders.
Available components
Last scanned (52 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
- 2 Nov 26 −47
- 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_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 functional
- 30 Oct 26 61
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 5 Nov 2026 · Probed https://sos-inventory.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 sos-inventory.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://sos-inventory.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/sos-inventory/ |
| http (plaintext) | http://sos-inventory.usefulapi.io/mcp | Inconclusive | 302 | http://sos-inventory.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 →
sosinventory_create_customer Create customer ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | – | Billing address. |
| company_name | string | – | – |
| string | – | – | |
| name | string | yes | 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). |
No output schema declared.
No examples provided.
sosinventory_create_item Create item ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
sosinventory_create_purchase_order Create purchase order ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Existing vendor (sosinventory_list_vendors). |
| vendor_message | string | – | Message to the vendor. |
No output schema declared.
No examples provided.
sosinventory_create_sales_order Create sales order ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Internal comment (not shown to the customer). |
| customer | object | yes | 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 | yes | Order lines. |
| location | object | – | Location (type=location). |
| number | string | – | Order number; leave out for SOS's automatic numbering. |
No output schema declared.
No examples provided.
sosinventory_create_vendor Create vendor ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_number | string | – | Your account number with this vendor. |
| address | object | – | Vendor address. |
| company_name | string | – | – |
| string | – | – | |
| name | string | yes | Vendor name (how it is looked up in SOS). |
| notes | string | – | Internal notes. |
| phone | string | – | – |
| terms | object | – | Payment terms (type=terms). |
No output schema declared.
No examples provided.
sosinventory_get_customer Get customer ~56
One customer by id with all fields (addresses, contact, terms, price tier, custom fields). GET /api/v2/customer/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | SOS customer id (from sosinventory_list_customers). |
No output schema declared.
No examples provided.
sosinventory_get_item Get item ~78
One item by id with all fields: quantities, prices, accounts, vendor, category, units of measure, price tiers, custom fields. GET /api/v2/item/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | SOS item id (from sosinventory_list_items). |
| location | string | – | Location name: quantities then reflect that location. |
No output schema declared.
No examples provided.
sosinventory_get_item_bom Get item bill of materials ~52
The bill of materials of an assembly item: component items, quantities and costs. GET /api/v2/item/{id}/bom.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | SOS item id of the assembly. |
No output schema declared.
No examples provided.
sosinventory_get_purchase_order Get purchase order ~57
One purchase order by id with all fields and line items. GET /api/v2/purchaseorder/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | SOS purchase order id (from sosinventory_list_purchase_orders; not the PO number). |
No output schema declared.
No examples provided.
sosinventory_get_sales_order Get sales order ~57
One sales order by id with all fields and line items. GET /api/v2/salesorder/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | SOS sales order id (from sosinventory_list_sales_orders; not the order number). |
No output schema declared.
No examples provided.
sosinventory_get_transaction Get transaction ~65
One transaction of any type by id, with all fields and line items. GET /api/v2/{type}/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | SOS record id (from sosinventory_list_transactions). |
| type | string | yes | Transaction type (the API endpoint name). |
No output schema declared.
No examples provided.
sosinventory_get_vendor Get vendor ~44
One vendor by id with all fields. GET /api/v2/vendor/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | SOS vendor id (from sosinventory_list_vendors). |
No output schema declared.
No examples provided.
sosinventory_list_customers List customers ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
sosinventory_list_items List items ~309
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
sosinventory_list_purchase_orders List purchase orders ~244
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
sosinventory_list_reference_data List reference data ~196
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Which table to list (the API endpoint name). |
No output schema declared.
No examples provided.
sosinventory_list_sales_orders List sales orders ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
sosinventory_list_transactions List other transactions ~397
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Transaction type (the API endpoint name). |
| updated_since | string | – | Only transactions created or updated since this local date-time (YYYY-MM-DDTHH:MM:SS). |
No output schema declared.
No examples provided.
sosinventory_list_vendors List vendors ~175
List or search vendors (suppliers) by name or notes, with contact details, address, terms and account number. GET /api/v2/vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
remote · sos-inventory.usefulapi.io
claude mcp add --transport http io-usefulapi-sos-inventory 'https://sos-inventory.usefulapi.io/mcp'
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.