SkuVault MCP by usefulapi
REMOTE · SKUVAULT.USEFULAPI.IO
MCP server for SkuVault — products, inventory, sales, purchase orders and stock adjustments.
Available components
Last scanned (47 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.
- 1 Nov 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 64
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://skuvault.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 skuvault.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://skuvault.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/skuvault/ |
| http (plaintext) | http://skuvault.usefulapi.io/mcp | Inconclusive | 302 | http://skuvault.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 →
skuvault_add_stock Add stock ~233
WRITE: add quantity of a product to a warehouse location (a transaction in SkuVault's history; every call adds again, so do not retry blindly). The transaction reason must already exist in SkuVault. Serialized or lotted products need serial numbers / a scanned lot code. Moderate throttling (10/min). POST /inventory/addItem.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Product code (give sku or code). |
| location_code | string | yes | Location the quantity is added to. |
| lot_code | string | – | Lot number (ScannedCode); required when adding to a lotted product. |
| note | string | – | Transaction note. |
| quantity | integer | yes | Quantity to add (a positive whole number). |
| reason | string | yes | Transaction reason; must already exist in SkuVault. |
| serial_numbers | array | – | Serial numbers, as many as the quantity; only for serialized products. |
| sku | string | – | Product SKU (give sku or code). |
| warehouse_id | integer | yes | SkuVault warehouse id (an integer; see skuvault_list_warehouses). |
No output schema declared.
No examples provided.
skuvault_get_available_quantities Get available quantities ~235
Sellable (available) quantity per SKU across all warehouses, with last-modified time. Use modified_after to see only what changed. Heavy throttling (5/min). POST /inventory/getAvailableQuantities.
| Name | Type | Req | Description |
|---|---|---|---|
| expand_alternate_skus | boolean | – | List alternate SKUs inside their primary row instead of as separate rows. |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| modified_after | string | – | Only quantities modified at or after this time. |
| modified_before | string | – | Only quantities modified before this time. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-5000 (default 1000). |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
No output schema declared.
No examples provided.
skuvault_get_inventory_by_location Get inventory by location ~224
Where each product is stored: per SKU (or code) the locations with warehouse code, quantity and whether the location is a reserve location. Filter by SKUs or by codes (not both). Heavy throttling (5/min). POST /inventory/getInventoryByLocation.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | – | Only these product codes (the reply is then keyed by code). |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-10000 (default 1000). |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| skus | array | – | Only these SKUs. |
No output schema declared.
No examples provided.
skuvault_get_item_quantities Get item quantities ~220
Product quantities per SKU: total on hand, available, held, pending and picked. Filter by product codes or modification time. Heavy throttling (5/min). POST /inventory/getItemQuantities.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | – | Only these product codes. |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| modified_after | string | – | Only inventory modified at or after this time. |
| modified_before | string | – | Only inventory modified before this time. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-10000 (default 1000). |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
No output schema declared.
No examples provided.
skuvault_get_product Get product ~82
One product (not a kit) by SKU or by code: details plus all quantities (on hand, available, pending, picked, incoming, in stock). Give exactly one of sku or code. Light throttling (20/min). POST /products/getProduct.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Product code. |
| sku | string | – | Product SKU. |
No output schema declared.
No examples provided.
skuvault_get_warehouse_quantities Get warehouse quantities ~233
SKUs and quantities held in one warehouse. Get the warehouse id from skuvault_list_warehouses. Heavy throttling (5/min). POST /inventory/getWarehouseItemQuantities.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| modified_after | string | – | Only quantities modified at or after this time. |
| modified_before | string | – | Only quantities modified before this time. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-10000 (default 1000). |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| warehouse_id | integer | yes | SkuVault warehouse id (an integer; see skuvault_list_warehouses). |
No output schema declared.
No examples provided.
skuvault_list_brands List brands ~149
List the brands created in SkuVault (Name, IsEnabled), 1,000 per page. Heavy throttling (5/min). POST /products/getBrands.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
No output schema declared.
No examples provided.
skuvault_list_classifications List classifications ~144
List product classifications and their named attributes, 1,000 per page. Heavy throttling (5/min). POST /products/getClassifications.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
No output schema declared.
No examples provided.
skuvault_list_integrations List sales channel accounts ~50
List the enabled sales-channel accounts (Amazon, ChannelAdvisor, Shopify...): Id, LongId, Name and Type. Severe throttling (1/min). POST /integration/getIntegrations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
skuvault_list_kits List kits ~265
List kits with their component lines, optional available quantity and cost. Needs a modified-time window (defaults to all time). The page size is not documented: keep following `next` until a page comes back empty. Heavy throttling (5/min). POST /products/getKits.
| Name | Type | Req | Description |
|---|---|---|---|
| include_available_quantity | boolean | – | Also compute the available quantity of each kit (default false: it is 0). |
| include_cost | boolean | – | Also return the kit cost (default false). |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| modified_after | string | – | Only kits modified at or after this time (default: all time). |
| modified_before | string | – | Only kits modified before this time (default: now). |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| skus | array | – | Only these kit SKUs. |
No output schema declared.
No examples provided.
skuvault_list_locations List locations ~117
List the locations in enabled warehouses with warehouse, location code, parent location/container and total quantity. Heavy throttling (5/min). POST /inventory/getLocations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
No output schema declared.
No examples provided.
skuvault_list_po_receives List purchase order receives ~244
Purchase-order receiving history: what was received (SKU, quantity, location, user, dates) followed by quantity corrections. Filter by warehouse codes, PO numbers or received time. Heavy throttling (5/min). POST /purchaseorders/getReceivesHistory.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-10000 (default 1000). |
| po_numbers | array | – | Only receives for these PO numbers. |
| received_after | string | – | Only receives after this time. |
| received_before | string | – | Only receives before this time. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| warehouse_codes | array | – | Only receives into these warehouse codes. |
No output schema declared.
No examples provided.
skuvault_list_products List products ~266
List products (not kits) with description, cost, prices, brand, supplier, classification, reorder point and quantities (on hand, available, pending, picked, incoming...). Filter by SKU or code, or by modification time. Alternate SKUs come back as separate rows (IsAlternateSKU) unless you filter. Heavy throttling (5/min). POST /products/getProducts.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | – | Only these product codes. |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| modified_after | string | – | Only products modified at or after this time. |
| modified_before | string | – | Only products modified before this time. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-10000 (default 1000). |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| skus | array | – | Only these SKUs. |
No output schema declared.
No examples provided.
skuvault_list_purchase_orders List purchase orders ~269
List purchase orders with supplier, dates, status, payment status, costs and line items (SKU, quantity, received quantity). By default completed POs are left out: set status Completed to see them. Specific PO numbers override the date and status filters. 10,000 per page. Heavy throttling (5/min). POST /purchaseorders/getPOs.
| Name | Type | Req | Description |
|---|---|---|---|
| include_products | boolean | – | Also return incoming product details in a separate array. |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| modified_after | string | – | Only POs modified at or after this time. |
| modified_before | string | – | Only POs modified before this time. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| po_numbers | array | – | Only these PO numbers; ignores dates and status. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| status | string | – | PO status (default: everything except Completed). |
No output schema declared.
No examples provided.
skuvault_list_sales List sales by status ~174
List sales (orders) that are ReadyToShip (default) or Pending, or look up specific sales by order id (then status is ignored): items, kits, shipping and contact info, totals. Not paged by the vendor. Heavy throttling (5/min). POST /sales/getSales.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| order_ids | array | – | Specific order ids; overrides status. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| status | string | – | Sale status (default ReadyToShip). |
No output schema declared.
No examples provided.
skuvault_list_sales_by_date List sales by date ~265
Sales within a date range, by sale date or by last-modified date: items, kits, fulfillment/processed quantities, shipping, contact info and totals. The date range may span at most 7 days. The most common way to pull orders. Heavy throttling (5/min). POST /sales/getSalesByDate.
| Name | Type | Req | Description |
|---|---|---|---|
| date_field | string | – | Filter on the sale date (Sale) or on the last-modified date (Modified). |
| from | string | yes | Start of the interval (inclusive). |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-10000 (default 1000). |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| to | string | yes | End of the interval (inclusive); at most 7 days after `from`. |
No output schema declared.
No examples provided.
skuvault_list_sold_items List sold items ~241
Items sold in a date range: date, SKU, quantity and total price per line, optionally breaking kits into components and including transfer sales. The date range may span at most 14 days. Heavy throttling (5/min). POST /sales/getSoldItems.
| Name | Type | Req | Description |
|---|---|---|---|
| break_down_kits | boolean | – | Show kit components instead of the kit (SkuVault default true). |
| from | string | yes | Start date/time (UTC). |
| include_transfer_sales | boolean | – | Include transfer sales (SkuVault default true). |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| to | string | yes | End date/time (UTC); at most 14 days after `from`. |
No output schema declared.
No examples provided.
skuvault_list_suppliers List suppliers ~148
List the suppliers in the account (Name, IsEnabled), 10,000 per page. Heavy throttling (5/min). POST /products/getSuppliers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
No output schema declared.
No examples provided.
skuvault_list_transactions List inventory transactions ~333
Inventory transaction history (adds, removes, picks, creates) with user, SKU, quantity before/after, location, reason, note and the sale it belongs to. The date range may span at most 7 days. Filter by user email, warehouse id, type, reasons or sale id. Heavy throttling (5/min). POST /inventory/getTransactions.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_reasons | array | – | Leave out these transaction reasons. |
| from | string | yes | Start of the range. |
| limit | integer | – | How many items to return from the vendor page, 1-500 (default 50). SkuVault pages hold 1,000-10,000 rows, so a window is shown. |
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
| page_size | integer | – | Vendor page size, 1000-10000 (default 1000). |
| reasons | array | – | Only these transaction reasons. |
| sale_id | string | – | Only transactions against this sale id. |
| skip | integer | – | Items to skip inside the vendor page (default 0). Pass `next.skip` from the previous reply. |
| to | string | – | End of the range (default now). At most 7 days after `from`. |
| type | string | – | Transaction type (default All). |
| user_email | string | – | Only this user's transactions (case-sensitive email). |
| warehouse_id | string | – | Only this warehouse (the Id from skuvault_list_warehouses). |
No output schema declared.
No examples provided.
skuvault_list_warehouses List warehouses ~87
List the regular warehouses (Id and Code). The numeric Id is what the stock tools and skuvault_list_transactions need. SkuVault throttles this call to 1 per minute. POST /inventory/getWarehouses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Vendor page number, starting at 0 (default 0). Pass `next.page` from the previous reply. |
No output schema declared.
No examples provided.
skuvault_remove_stock Remove stock ~193
WRITE: remove quantity of a product from a warehouse location (a transaction in SkuVault's history; every call removes again, so do not retry blindly). The transaction reason must already exist in SkuVault. Serialized products need serial numbers. Moderate throttling (10/min). POST /inventory/removeItem.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Product code (give sku or code). |
| location_code | string | yes | Location the quantity is removed from. |
| quantity | integer | yes | Quantity to remove (a positive whole number). |
| reason | string | yes | Transaction reason; must already exist in SkuVault. |
| serial_numbers | array | – | Serial numbers, as many as the quantity; only for serialized products. |
| sku | string | – | Product SKU (give sku or code). |
| warehouse_id | integer | yes | SkuVault warehouse id (an integer; see skuvault_list_warehouses). |
No output schema declared.
No examples provided.
skuvault_set_stock_quantity Set stock quantity ~155
WRITE: set the exact quantity of a product at one warehouse location, overwriting what is there (running it again with the same values changes nothing more). Use skuvault_get_inventory_by_location first to see the current quantity. Moderate throttling (10/min). POST /inventory/setItemQuantity.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Product code (give sku or code). |
| location_code | string | yes | Location whose quantity is set. |
| quantity | integer | yes | The new quantity at that location (0 or more). |
| sku | string | – | Product SKU (give sku or code). |
| warehouse_id | integer | yes | SkuVault warehouse id (an integer; see skuvault_list_warehouses). |
No output schema declared.
No examples provided.
How do I install the SkuVault MCP by usefulapi server?
SkuVault MCP by usefulapi is a hosted endpoint at https://skuvault.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 · skuvault.usefulapi.io
claude mcp add --transport http io-usefulapi-skuvault 'https://skuvault.usefulapi.io/mcp'
What is the SkuVault MCP by usefulapi server?
SkuVault MCP by usefulapi is listed in the public MCP registry as io.usefulapi/skuvault. MCP server for SkuVault, products, inventory, sales, purchase orders and stock adjustments. This page covers its hosted endpoint (https://skuvault.usefulapi.io/mcp).
Is the SkuVault MCP by usefulapi server safe to use?
SkuVault 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 SkuVault MCP by usefulapi server expose?
SkuVault MCP by usefulapi exposes 22 tools: skuvault_list_warehouses, skuvault_list_locations, skuvault_list_products, skuvault_get_product, skuvault_list_kits, and 17 more. Their descriptions and schemas cost roughly 4,327 tokens of context every time the server is loaded.
Does the SkuVault MCP by usefulapi server require authentication?
Its publisher declares no required credentials for SkuVault 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 SkuVault MCP by usefulapi server still maintained?
SkuVault 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 SkuVault MCP by usefulapi server?
VerifyMCP ran 4 checks on SkuVault 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 SkuVault 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.