Next free-source huntWe check for new free data every weekday.
FinancialMCP serverFirst audited Nov 13, 2026

Loyverse MCP by usefulapi

Query Loyverse POS receipts, shifts, items, inventory and customers, and update stock and customers.The vendor's description, from its MCP Registry listing.

Passed public checksAudited Nov 13, 2026

Every public check ran and passed. Public audit: we connect as an AI client would, list the tools and check what they say. We do not run them. How we audit

Does it work?
YesConnected in 184 ms.
Sign-up?
None neededIt answered without any account or key.
Can it change things?
YesSome tools say they can change things. Your AI client should ask you first.
Endpointhttps://loyverse.usefulapi.io/mcp

Source code Website Streamable HTTP · protocol 2025-11-25 · server version 1.39.1

What we checked, the evidence, and the tools it offers.

What we checked

Security

  • Passed: Connections are encrypted (HTTPS).

  • Passed: No hidden instructions found in tool text.

Safety labels

  • Note: 4 tools are labelled as able to change things.

    Expected for tools that send, write or buy. Your AI client should ask before calling them.

    • loyverse_upsert_customer
    • loyverse_upsert_category
    • loyverse_upsert_supplier
    • loyverse_set_inventory_levels
  • Passed: Every tool says whether it only reads or can change things.

Tools

  • Passed: 21 tools listed.

  • Passed: Every tool describes its inputs with a valid schema.

Protocol

  • Passed: The MCP handshake works (Streamable HTTP).

  • Passed: Protocol version 2025-11-25 (latest).

  • Passed: Unknown requests are refused.

Connection

  • Passed: The server responds.

Tools (21)

As the server describes them. The labels are the server's own: it says whether each tool only reads or can change things.

  • loyverse_get_merchantFetch the merchant account this token belongs to — business name, email, country and currency. A cheap way to confirm the token works. Loyverse: GET /merchant/.Read-only
  • loyverse_list_storesList the merchant's stores (locations) with their addresses. Store ids are what the receipt, shift and inventory filters take. Loyverse: GET /stores.Read-only
  • loyverse_list_employeesList employees, with the stores each can access and whether they are the owner. Loyverse: GET /employees.Read-only
  • loyverse_list_receiptsList sales and refund receipts, newest first, with line items, payments, discounts and taxes. Filter by store, time range or receipt numbers — the core of any sales question. Loyverse: GET /receipts.Read-only
  • loyverse_get_receiptFetch a single receipt by its receipt number (e.g. 2-1008), with line items, modifiers, discounts, taxes and payments. Loyverse: GET /receipts/{receipt_number}.Read-only
  • loyverse_list_shiftsList cash-register shifts with their cash, gross/net sales, refunds, discounts, taxes, per-payment-type totals and pay-in/pay-out movements — the end-of-day view. Loyverse: GET /shifts.Read-only
  • loyverse_list_itemsList catalog items with their variants (SKU, barcode, price, cost, per-store pricing), category, taxes and modifiers. Loyverse: GET /items.Read-only
  • loyverse_get_itemFetch a single catalog item by id, with its variants. Loyverse: GET /items/{item_id}.Read-only
  • loyverse_list_variantsList item variants — the sellable SKUs — optionally for given items or one SKU. Variant ids are what inventory levels are keyed on. Loyverse: GET /variants.Read-only
  • loyverse_list_categoriesList item categories. Loyverse: GET /categories.Read-only
  • loyverse_list_inventoryList current stock (`in_stock`) per variant per store. Filter by stores and/or variants — the answer to 'what is running low?'. Loyverse: GET /inventory.Read-only
  • loyverse_list_customersList loyalty customers, newest first, with visits, total spent and points balance. Filter by email or ids. Loyverse: GET /customers.Read-only
  • loyverse_get_customerFetch a single customer by id, with visits, total spent and points balance. Loyverse: GET /customers/{customer_id}.Read-only
  • loyverse_list_payment_typesList the payment types (cash, card, integrated terminals…) and the stores where each is available. Receipt payments reference these ids. Loyverse: GET /payment_types.Read-only
  • loyverse_list_discountsList configured discounts (fixed/variable percent or amount, discount-by-points) and where they apply. Loyverse: GET /discounts.Read-only
  • loyverse_list_taxesList taxes with their rate, whether they are INCLUDED in or ADDED to the price, and the stores they apply in. Loyverse: GET /taxes.Read-only
  • loyverse_list_suppliersList suppliers with their contact details. Loyverse: GET /suppliers/.Read-only
  • loyverse_upsert_customerCreate a loyalty customer, or update one by passing its `id`. Loyverse does not document whether omitted fields survive an update, so on update fetch the customer first and send the full record. Loyv…Can change things
  • loyverse_upsert_categoryCreate an item category, or rename/recolor one by passing its `id`. Loyverse: POST /categories.Can change things
  • loyverse_upsert_supplierCreate a supplier, or update one by passing its `id`. Loyverse does not document whether omitted fields survive an update, so on update send the full record. Loyverse: POST /suppliers/.Can change things
  • loyverse_set_inventory_levelsSet the ABSOLUTE stock (`stock_after`) of one or more variants at given stores — e.g. after a stock count. This overwrites the current level rather than adding to it; read the current levels with loy…Can change things

Audit history

  1. Nov 13Passed

What we sent

Every request in this audit, with the answer and how long it took. We never send credentials and never call a tool.

RequestAnswerTime
initializeHTTP 200184 ms
initializedHTTP 20240 ms
tools/listHTTP 200176 ms
prompts/listHTTP 200148 ms
unknown-methodHTTP 40194 ms

Run this server, or disagree with the result?

Fix the issue and it shows in the next weekly audit, or email us to ask for a re-audit or to dispute a finding. Read how we audit for what each check means.