loyverse

Tools

21 tools: 17 read-only, 0 change data, 4 high risk (delete, pay, send or run code).

No tool name points to moving money or changing orders.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 5,560 tokens of tool definitions and a 490 ms handshake.

• high riskloyverse_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. Loyverse: POST /customers.
• high riskloyverse_upsert_categoryCreate an item category, or rename/recolor one by passing its `id`. Loyverse: POST /categories.
• high riskloyverse_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/.
• high riskloyverse_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 loyverse_list_inventory first so they can be restored. Loyverse: POST /inventory.
• read-onlyloyverse_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-onlyloyverse_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-onlyloyverse_list_employeesList employees, with the stores each can access and whether they are the owner. Loyverse: GET /employees.
• read-onlyloyverse_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-onlyloyverse_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-onlyloyverse_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-onlyloyverse_list_itemsList catalog items with their variants (SKU, barcode, price, cost, per-store pricing), category, taxes and modifiers. Loyverse: GET /items.
• read-onlyloyverse_get_itemFetch a single catalog item by id, with its variants. Loyverse: GET /items/{item_id}.
• read-onlyloyverse_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-onlyloyverse_list_categoriesList item categories. Loyverse: GET /categories.
• read-onlyloyverse_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-onlyloyverse_list_customersList loyalty customers, newest first, with visits, total spent and points balance. Filter by email or ids. Loyverse: GET /customers.
• read-onlyloyverse_get_customerFetch a single customer by id, with visits, total spent and points balance. Loyverse: GET /customers/{customer_id}.
• read-onlyloyverse_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-onlyloyverse_list_discountsList configured discounts (fixed/variable percent or amount, discount-by-points) and where they apply. Loyverse: GET /discounts.
• read-onlyloyverse_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-onlyloyverse_list_suppliersList suppliers with their contact details. Loyverse: GET /suppliers/.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 490 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Online store and commerce, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/loyverse.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/loyverse.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=loyverse.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/loyverse.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/loyverse.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=loyverse.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.