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.
Available components
Last scanned (10 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 18 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 −14
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.07 ▲ functional
- Server version: 1.2.0 → 1.8.0 functional
- 8 Oct 26 74
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 18 Oct 2026 · Probed https://lightspeed-r-series.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 lightspeed-r-series.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://lightspeed-r-series.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://lightspeed-r-series.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://lightspeed-r-series.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://lightspeed-r-series.usefulapi.io/mcp |
| Authorisation server | https://lightspeed-r-series.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lightspeed-r-series.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/lightspeed-r-series/ |
| http (plaintext) | http://lightspeed-r-series.usefulapi.io/mcp | Inconclusive | 302 | http://lightspeed-r-series.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 →
create_customer Create a customer ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name. |
| customer_type_id | string | – | customerTypeID to assign. |
| 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. |
No output schema declared.
No examples provided.
get_account Get account ~48
The connected Lightspeed Retail (R-Series) account: id, name, status, employee count/limit, default and purchasing currencies. Good first call. GET /Account/{accountID}.json.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_customer Get a customer ~117
One customer by customerID with Contact (emails, phones, addresses), customer type and notes. GET /Account/{accountID}/Customer/{customerID}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_id | string | yes | 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… |
No output schema declared.
No examples provided.
get_item Get an item ~155
One item by itemID with its prices, per-shop stock (ItemShops), category and other related records. GET /Account/{accountID}/Item/{itemID}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | 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… |
No output schema declared.
No examples provided.
get_purchase_order Get a purchase order ~120
One purchase order by orderID with its lines (OrderLines: itemID, quantity, numReceived, price), vendor and shop. GET /Account/{accountID}/Order/{orderID}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | 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… |
No output schema declared.
No examples provided.
get_sale Get a sale ~188
One sale by saleID with its line items (SaleLines with Item), payments (SalePayments with PaymentType) and customer. GET /Account/{accountID}/Sale/{saleID}.json.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The saleID (from list_sales). |
No output schema declared.
No examples provided.
list_categories List categories ~153
Item categories (hierarchical): categoryID, name, fullPathName, parentID, nodeDepth. GET /Account/{accountID}/Category.json.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_customers List customers ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | string | – | false (default) = active records only, true = active and archived, only = archived only. |
| company | string | – | Company contains this text. |
| 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. |
No output schema declared.
No examples provided.
list_employees List employees ~166
Employees: employeeID, firstName, lastName, lockOut, archived, employeeRoleID, limitToShopID. Use employeeID to filter sales. GET /Account/{accountID}/Employee.json.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_inventory List inventory levels ~243
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_items List items ~407
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_purchase_orders List purchase orders ~216
Purchase orders to vendors: orderID, vendorID, shopID, orderedDate, arrivalDate, receivedDate, complete, totalQuantity, shipCost. GET /Account/{accountID}/Order.json.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
list_sales List sales ~376
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_shops List shops ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
list_vendors List vendors ~159
Suppliers: vendorID, name, accountNumber, archived. GET /Account/{accountID}/Vendor.json.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
update_item Update an item ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The itemID to update. |
| manufacturer_sku | string | – | New manufacturer SKU. |
| upc | string | – | New UPC (11-14 digits). |
No output schema declared.
No examples provided.
update_stock Set stock level ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | The itemID. |
| item_shop_id | string | – | Or the itemShopID of that item/shop record (from get_item ItemShops). |
| qoh | integer | yes | The new quantity on hand. |
| shop_id | string | – | The shopID whose stock to set (from list_shops). |
No output schema declared.
No examples provided.
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.
remote · lightspeed-r-series.usefulapi.io
claude mcp add --transport http io-usefulapi-lightspeed-r-series 'https://lightspeed-r-series.usefulapi.io/mcp'
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.