# Lightspeed Retail (R-Series) MCP by usefulapi (remote · lightspeed-r-series.usefulapi.io)

Read Lightspeed R-Series items, stock, sales, customers and POs; create customers and set stock.

- Trust score: 66/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `lightspeed-r-series.usefulapi.io`: 66/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-lightspeed-r-series/lightspeed-r-series.md), [page](https://verifymcp.io/servers/io-usefulapi-lightspeed-r-series/lightspeed-r-series)

## Channel facts

- Endpoint: `https://lightspeed-r-series.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.6.1`

## 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-10-18.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3455 tokens (~203/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Lightspeed Retail (R-Series) MCP by usefulapi server?

Lightspeed Retail (R-Series) MCP by usefulapi is a hosted endpoint at https://lightspeed-r-series.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-lightspeed-r-series 'https://lightspeed-r-series.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-lightspeed-r-series": {
      "url": "https://lightspeed-r-series.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  io-usefulapi-lightspeed-r-series:
    url: "https://lightspeed-r-series.usefulapi.io/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-lightspeed-r-series": {
      "type": "http",
      "url": "https://lightspeed-r-series.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-10-17 (score 66, +1)

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

### 2026-10-15 (score 65, +1)

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

### 2026-10-14 (score 64, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.8.0 → 1.9.0

### 2026-10-13 (score 62, +1)

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

### 2026-10-12 (score 61, +1)

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

### 2026-10-10 (score 60, −14)

- [security regression] HTTPS: pass → unverified
- [security regression] Transport: pass → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Stability: unverified → 0.07
- [functional] Server version: 1.2.0 → 1.8.0

### 2026-10-08 (score 74)

First indexed and scored.

## MCP tools (17)

### `get_account` (~48 tokens)

Get account

The connected Lightspeed Retail (R-Series) account: id, name, status, employee count/limit, default and purchasing currencies. Good first call. GET /Account/{accountID}.json.

### `list_shops` (~143 tokens)

List shops

List the account's shops (store locations): shopID, name, time zone, archived flag. Use shopID to filter sales, inventory and purchase orders. GET /Account/{accountID}/Shop.json.

Input parameters:

- `include_contact` (boolean): Also load each shop's Contact (address, phone).
- `limit` (integer): Records per page (1-100, default 100).
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `sort` (string): Sort field; prefix "-" for descending. Allowed: shopID.

### `list_items` (~407 tokens)

List items

Search the product catalog. Each item has itemID, description, SKUs (systemSku, customSku, upc, ean, manufacturerSku), defaultCost, categoryID and its Prices (price levels). Set include_stock to add per-shop quantities (ItemShops; shopID 0 = all shops). Paginate with next_url. GET /Account/{accountID}/Item.json.

Input parameters:

- `archived` (string): false (default) = active records only, true = active and archived, only = archived only.
- `category_id` (string): Only items in this category (categoryID).
- `custom_sku` (string): Exact custom SKU.
- `description` (string): Description contains this text (like search).
- `ean` (string): Exact EAN.
- `include_category` (boolean): Include the Category record.
- `include_stock` (boolean): Include per-shop stock (ItemShops relation).
- `item_code` (string): Exact match on itemID, UPC or EAN.
- `limit` (integer): Records per page (1-100, default 100).
- `manufacturer_sku` (string): Exact manufacturer SKU.
- `min_qoh` (integer): Only items with at least one shop record whose quantity on hand is >= this (loads ItemShops).
- `modified_since` (string): Only items modified at or after this time (item timeStamp, UTC unless an offset is given).
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `sort` (string): Sort field; prefix "-" for descending. Allowed: itemID, timeStamp, description.
- `system_sku` (string): Exact Lightspeed system SKU (the barcode on labels).
- `upc` (string): Exact UPC.
- `vendor_id` (string): Only items whose default vendor is this vendorID.

### `get_item` (~155 tokens)

Get an item

One item by itemID with its prices, per-shop stock (ItemShops), category and other related records. GET /Account/{accountID}/Item/{itemID}.json.

Input parameters:

- `item_id` (string, required): The itemID (from list_items).
- `relations` (array): Related records to include (each adds a little to the request's rate-limit cost). Default: ItemShops, Category, Manufacturer, ItemVendorNums, Note. Allowed: Category, TaxClass, ItemAttributes, ItemAt…

### `list_inventory` (~243 tokens)

List inventory levels

Stock levels per item per shop (ItemShop records): qoh (quantity on hand), sellable, backorder, reorderPoint, reorderLevel, costs and values. shopID 0 is the all-shops summary. Paginate with next_url. GET /Account/{accountID}/ItemShop.json.

Input parameters:

- `item_id` (string): Only this item (itemID).
- `limit` (integer): Records per page (1-100, default 100).
- `max_qoh` (integer): Quantity on hand <= this (e.g. 0 for out of stock).
- `min_qoh` (integer): Quantity on hand >= this.
- `modified_since` (string): Only records changed at or after this time (timeStamp).
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `shop_id` (string): Only this shop (shopID; 0 = the all-shops summary records).
- `sort` (string): Sort field; prefix "-" for descending. Allowed: itemShopID, timeStamp.

### `list_categories` (~153 tokens)

List categories

Item categories (hierarchical): categoryID, name, fullPathName, parentID, nodeDepth. GET /Account/{accountID}/Category.json.

Input parameters:

- `limit` (integer): Records per page (1-100, default 100).
- `name` (string): Name contains this text.
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `parent_id` (string): Only direct children of this categoryID (0 = top level).
- `sort` (string): Sort field; prefix "-" for descending. Allowed: categoryID, timeStamp, leftNode, rightNode.

### `list_sales` (~376 tokens)

List sales

Sales history: saleID, completed/voided flags, completeTime, totals (calcSubtotal, calcTax1/2, total, balance), customerID, employeeID, shopID, registerID. Filter by a date range on completeTime (default) or timeStamp, shop, customer, employee. Set include_lines for SaleLines (items sold). Paginate with next_url. GET /Account/{accountID}/Sale.json.

Input parameters:

- `completed` (boolean): true = completed sales only, false = open/unfinished only.
- `customer_id` (string): Only sales for this customer (customerID).
- `date_field` (string): Which date from/to apply to (default completeTime).
- `employee_id` (string): Only sales processed by this employee (employeeID).
- `from` (string): Start (inclusive), e.g. 2026-10-01 or 2026-10-01T00:00:00-04:00. Times are UTC unless an offset is given.
- `include_lines` (boolean): Include the SaleLines relation (line items).
- `include_payments` (boolean): Include the SalePayments relation.
- `limit` (integer): Records per page (1-100, default 100).
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `shop_id` (string): Only sales in this shop (shopID).
- `sort` (string): Sort field; prefix "-" for descending. Allowed: saleID, timeStamp, completeTime, updatetime.
- `to` (string): End (inclusive), same format.
- `voided` (boolean): true = voided only, false = exclude voided.

### `get_sale` (~188 tokens)

Get a sale

One sale by saleID with its line items (SaleLines with Item), payments (SalePayments with PaymentType) and customer. GET /Account/{accountID}/Sale/{saleID}.json.

Input parameters:

- `relations` (array): Related records to include (each adds a little to the request's rate-limit cost). Default: SaleLines, SaleLines.Item, SalePayments, SalePayments.PaymentType, Customer. Allowed: SaleLines, SaleLines.D…
- `sale_id` (string, required): The saleID (from list_sales).

### `list_customers` (~245 tokens)

List customers

Search customers by name, company or email: customerID, firstName, lastName, company, customerTypeID, createTime. Email search loads the Contact relation (emails, phones, addresses). Paginate with next_url. GET /Account/{accountID}/Customer.json.

Input parameters:

- `archived` (string): false (default) = active records only, true = active and archived, only = archived only.
- `company` (string): Company contains this text.
- `email` (string): Email contains this text (searches Contact.email).
- `first_name` (string): First name contains this text.
- `include_contact` (boolean): Include the Contact relation (emails, phones, addresses).
- `last_name` (string): Last name contains this text.
- `limit` (integer): Records per page (1-100, default 100).
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `sort` (string): Sort field; prefix "-" for descending. Allowed: customerID, timeStamp, firstName, lastName.

### `get_customer` (~117 tokens)

Get a customer

One customer by customerID with Contact (emails, phones, addresses), customer type and notes. GET /Account/{accountID}/Customer/{customerID}.json.

Input parameters:

- `customer_id` (string, required): The customerID (from list_customers).
- `relations` (array): Related records to include (each adds a little to the request's rate-limit cost). Default: Contact, CustomerType, Note. Allowed: Contact, CustomerType, Discount, Note, TaxCategory, CreditAccount, Tag…

### `list_vendors` (~159 tokens)

List vendors

Suppliers: vendorID, name, accountNumber, archived. GET /Account/{accountID}/Vendor.json.

Input parameters:

- `archived` (string): false (default) = active records only, true = active and archived, only = archived only.
- `include_contact` (boolean): Include the Contact relation.
- `limit` (integer): Records per page (1-100, default 100).
- `name` (string): Name contains this text.
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `sort` (string): Sort field; prefix "-" for descending. Allowed: vendorID, timeStamp, name.

### `list_purchase_orders` (~216 tokens)

List purchase orders

Purchase orders to vendors: orderID, vendorID, shopID, orderedDate, arrivalDate, receivedDate, complete, totalQuantity, shipCost. GET /Account/{accountID}/Order.json.

Input parameters:

- `archived` (string): false (default) = active records only, true = active and archived, only = archived only.
- `complete` (boolean): true = completed orders only, false = open orders only.
- `include_lines` (boolean): Include the OrderLines relation.
- `limit` (integer): Records per page (1-100, default 100).
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `shop_id` (string): Only orders for this shop (shopID).
- `sort` (string): Sort field; prefix "-" for descending. Allowed: orderID, timeStamp.
- `vendor_id` (string): Only orders to this vendor (vendorID).

### `get_purchase_order` (~120 tokens)

Get a purchase order

One purchase order by orderID with its lines (OrderLines: itemID, quantity, numReceived, price), vendor and shop. GET /Account/{accountID}/Order/{orderID}.json.

Input parameters:

- `order_id` (string, required): The orderID (from list_purchase_orders).
- `relations` (array): Related records to include (each adds a little to the request's rate-limit cost). Default: OrderLines, Vendor, Shop, Note. Allowed: OrderLines, Note, Vendor, Shop, CustomFieldValues, CustomFieldValue…

### `list_employees` (~166 tokens)

List employees

Employees: employeeID, firstName, lastName, lockOut, archived, employeeRoleID, limitToShopID. Use employeeID to filter sales. GET /Account/{accountID}/Employee.json.

Input parameters:

- `archived` (string): false (default) = active records only, true = active and archived, only = archived only.
- `include_contact` (boolean): Include the Contact relation.
- `limit` (integer): Records per page (1-100, default 100).
- `next_url` (string): To get the next page: the next_url value from a previous call of this same tool, unchanged. Other filters are ignored when it is set.
- `sort` (string): Sort field; prefix "-" for descending. Allowed: employeeID, timeStamp.

### `create_customer` (~144 tokens)

Create a customer

Create a new customer, optionally with a primary email and one phone number (stored in the customer's Contact). Give at least a first name, last name or company. Returns the new customer with its customerID. POST /Account/{accountID}/Customer.json.

Input parameters:

- `company` (string): Company name.
- `customer_type_id` (string): customerTypeID to assign.
- `email` (string): Primary email address.
- `first_name` (string): First name.
- `last_name` (string): Last name.
- `phone` (string): Phone number.
- `phone_type` (string): Phone type (default Mobile).
- `title` (string): Job title.

### `update_item` (~175 tokens)

Update an item

Change fields of an existing item: description, default cost, SKUs, category. Only the fields you pass are changed. Prices and stock are not changed here (use update_stock for quantities). PUT /Account/{accountID}/Item/{itemID}.json.

Input parameters:

- `category_id` (string): New categoryID (0 = no category).
- `custom_sku` (string): New custom SKU.
- `default_cost` (number): New default (reorder) cost.
- `description` (string): New description (shown on receipts and labels).
- `ean` (string): New EAN (11-14 digits).
- `item_id` (string, required): The itemID to update.
- `manufacturer_sku` (string): New manufacturer SKU.
- `upc` (string): New UPC (11-14 digits).

### `update_stock` (~183 tokens)

Set stock level

CHANGES STOCK COUNTS: sets (does not add to) the quantity on hand of one item in one shop to `qoh`, by updating the item's ItemShop record. Use for correcting a few items; for many items use an inventory count in Lightspeed. Identify the shop by shop_id, or by item_shop_id from get_item's ItemShops. Not for shopID 0 (the all-shops summary). PUT /Account/{accountID}/Item/{itemID}.json with ItemShops.

Input parameters:

- `item_id` (string, required): The itemID.
- `item_shop_id` (string): Or the itemShopID of that item/shop record (from get_item ItemShops).
- `qoh` (integer, required): The new quantity on hand.
- `shop_id` (string): The shopID whose stock to set (from list_shops).

## Diagnostics

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

## Score history

- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 62
- 2026-10-12: 61
- 2026-10-10: 60
- 2026-10-08: 74

## Common questions

### What is the Lightspeed Retail (R-Series) MCP by usefulapi server?

Lightspeed Retail (R-Series) MCP by usefulapi is listed in the public MCP registry as io.usefulapi/lightspeed-r-series. Read Lightspeed R-Series items, stock, sales, customers and POs; create customers and set stock. This page covers its hosted endpoint (https://lightspeed-r-series.usefulapi.io/mcp).

### Is the Lightspeed Retail (R-Series) MCP by usefulapi server safe to use?

Lightspeed Retail (R-Series) MCP by usefulapi scores 66 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 Lightspeed Retail (R-Series) MCP by usefulapi server expose?

Lightspeed Retail (R-Series) MCP by usefulapi exposes 17 tools: get_account, list_shops, list_items, get_item, list_inventory, and 12 more. Their descriptions and schemas cost roughly 3,238 tokens of context every time the server is loaded.

### Does the Lightspeed Retail (R-Series) MCP by usefulapi server require authentication?

Yes. Lightspeed Retail (R-Series) MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Lightspeed Retail (R-Series) MCP by usefulapi server still maintained?

Lightspeed Retail (R-Series) MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://lightspeed-r-series.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/lightspeed-r-series/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-lightspeed-r-series/lightspeed-r-series.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-lightspeed-r-series/lightspeed-r-series.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-lightspeed-r-series/lightspeed-r-series