Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/loyverse

REMOTE · LOYVERSE.USEFULAPI.IO · SCANNED OCT 3

Query Loyverse POS receipts, shifts, items, inventory and customers, and update stock and customers.

76 Trust /100
Trust breakdown (7 categories)

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 Security89
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4009 tokens (~190/item across 21 items; 21 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 Management10
  • Stability observed for 3 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 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 21 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
Install

How do I install the io.usefulapi/loyverse MCP server?

io.usefulapi/loyverse is a hosted endpoint at https://loyverse.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 · loyverse.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-loyverse 'https://loyverse.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-loyverse": {
      "url": "https://loyverse.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-loyverse": {
      "type": "http",
      "url": "https://loyverse.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-loyverse]
url = "https://loyverse.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-loyverse": {
      "type": "remote",
      "url": "https://loyverse.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-loyverse --url 'https://loyverse.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-loyverse:
    url: "https://loyverse.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-loyverse": {
      "Transport": "http",
      "Url": "https://loyverse.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-loyverse -t streamable-http -u 'https://loyverse.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-loyverse": {
      "type": "http",
      "url": "https://loyverse.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Oct 26 +1

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

  • 2 Oct 26 0
    • Server version: 1.3.0 → 1.5.1 functional
  • 1 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.3.0 functional
  • 30 Sept 26 +42
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • First check of Authorization: partial security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 29 Sept 26 28

    First indexed and scored.

Diagnostics

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 3 Oct 2026 · Probed https://loyverse.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 loyverse.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 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://loyverse.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://loyverse.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://loyverse.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://loyverse.usefulapi.io/mcp
Authorisation server https://loyverse.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://loyverse.usefulapi.io/mcp Verified 200
http (plaintext) http://loyverse.usefulapi.io/mcp HTTPS enforced 301 https://loyverse.usefulapi.io/mcp
MCP tools · 21 exposed · ~4,009 tokens

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 →

Tool Tokens
loyverse_get_customer ~49

Fetch a single customer by id, with visits, total spent and points balance. Loyverse: GET /customers/{customer_id}.

NameTypeReqDescription
customer_idstringyesThe customer id (UUID).

No output schema declared.

No examples provided.

loyverse_get_item ~45

Fetch a single catalog item by id, with its variants. Loyverse: GET /items/{item_id}.

NameTypeReqDescription
item_idstringyesThe item id (UUID).

No output schema declared.

No examples provided.

loyverse_get_merchant ~45

Fetch the merchant account this token belongs to — business name, email, country and currency. A cheap way to confirm the token works. Loyverse: GET /merchant/.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

loyverse_get_receipt ~72

Fetch a single receipt by its receipt number (e.g. 2-1008), with line items, modifiers, discounts, taxes and payments. Loyverse: GET /receipts/{receipt_number}.

NameTypeReqDescription
receipt_numberstringyesThe receipt number, e.g. 2-1008.

No output schema declared.

No examples provided.

loyverse_list_categories ~102

List item categories. Loyverse: GET /categories.

NameTypeReqDescription
categories_idsstring–Comma-separated list of category ids to return.
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
limitinteger–Page size, 1-250 (Loyverse default 50).
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).

No output schema declared.

No examples provided.

loyverse_list_customers ~287

List loyalty customers, newest first, with visits, total spent and points balance. Filter by email or ids. Loyverse: GET /customers.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
customer_idsstring–Comma-separated list of customer ids to return.
emailstring–Only the customer with this email.
limitinteger–Page size, 1-250 (Loyverse default 50).
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_discounts ~248

List configured discounts (fixed/variable percent or amount, discount-by-points) and where they apply. Loyverse: GET /discounts.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
discount_idsstring–Comma-separated list of discount ids to return.
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_employees ~287

List employees, with the stores each can access and whether they are the owner. Loyverse: GET /employees.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
employee_idsstring–Comma-separated list of employee ids to return.
limitinteger–Page size, 1-250 (Loyverse default 50).
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_inventory ~203

List current stock (`in_stock`) per variant per store. Filter by stores and/or variants — the answer to 'what is running low?'. Loyverse: GET /inventory.

NameTypeReqDescription
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
limitinteger–Page size, 1-250 (Loyverse default 50).
store_idsstring–Comma-separated store ids.
updated_at_maxstring–Only levels updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only levels updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
variant_idsstring–Comma-separated variant ids.

No output schema declared.

No examples provided.

loyverse_list_items ~295

List catalog items with their variants (SKU, barcode, price, cost, per-store pricing), category, taxes and modifiers. Loyverse: GET /items.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
items_idsstring–Comma-separated list of item ids to return.
limitinteger–Page size, 1-250 (Loyverse default 50).
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_payment_types ~255

List the payment types (cash, card, integrated terminals…) and the stores where each is available. Receipt payments reference these ids. Loyverse: GET /payment_types.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
payment_type_idsstring–Comma-separated list of payment type ids to return.
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_receipts ~389

List 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.

NameTypeReqDescription
before_receipt_numberstring–Only receipts created up to the receipt with this number.
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
limitinteger–Page size, 1-250 (Loyverse default 50).
orderstring–Only receipts with this order name/number.
receipt_numbersstring–Comma-separated receipt numbers to return, e.g. 2-1008,2-1009.
since_receipt_numberstring–Only receipts created at or after the receipt with this number.
sourcestring–Only receipts from this source (e.g. an app name).
store_idstring–Only receipts from this store.
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_shifts ~202

List 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.

NameTypeReqDescription
created_at_maxstring–Only shifts opened at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only shifts opened at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
limitinteger–Page size, 1-250 (Loyverse default 50).
store_idsstring–Comma-separated list of store ids to return.

No output schema declared.

No examples provided.

loyverse_list_stores ~251

List the merchant's stores (locations) with their addresses. Store ids are what the receipt, shift and inventory filters take. Loyverse: GET /stores.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
store_idsstring–Comma-separated list of store ids to return.
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_suppliers ~107

List suppliers with their contact details. Loyverse: GET /suppliers/.

NameTypeReqDescription
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
limitinteger–Page size, 1-250 (Loyverse default 50).
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
suppliers_idsstring–Comma-separated list of supplier ids to return.

No output schema declared.

No examples provided.

loyverse_list_taxes ~252

List taxes with their rate, whether they are INCLUDED in or ADDED to the price, and the stores they apply in. Loyverse: GET /taxes.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
tax_idsstring–Comma-separated list of tax ids to return.
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).

No output schema declared.

No examples provided.

loyverse_list_variants ~329

List item variants — the sellable SKUs — optionally for given items or one SKU. Variant ids are what inventory levels are keyed on. Loyverse: GET /variants.

NameTypeReqDescription
created_at_maxstring–Only records created at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
created_at_minstring–Only records created at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
cursorstring–The `cursor` from the previous page's response. Omit for the first page.
items_idsstring–Comma-separated item ids whose variants to return.
limitinteger–Page size, 1-250 (Loyverse default 50).
show_deletedboolean–Also return soft-deleted records (they carry deleted_at).
skustring–Only the variant with this SKU.
updated_at_maxstring–Only records updated at or before this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
updated_at_minstring–Only records updated at or after this time (ISO 8601 UTC, e.g. 2026-03-30T18:30:00.000Z).
variants_idsstring–Comma-separated list of variant ids to return.

No output schema declared.

No examples provided.

loyverse_set_inventory_levels ~86

Set 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.

NameTypeReqDescription
inventory_levelsarrayyesThe stock levels to set.

No output schema declared.

No examples provided.

loyverse_upsert_category ~75

Create an item category, or rename/recolor one by passing its `id`. Loyverse: POST /categories.

NameTypeReqDescription
colorstring–Display color on the POS.
idstring–Existing category id to update. Omit to create.
namestringyesThe category name (required).

No output schema declared.

No examples provided.

loyverse_upsert_customer ~209

Create 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.

NameTypeReqDescription
addressstring–Street address.
citystring–City, town or village.
country_codestring–Two-letter ISO 3166-1 alpha-2 country code, e.g. US.
customer_codestring–Your own customer code (e.g. a loyalty card number).
emailstring–Email address.
idstring–Existing customer id to update. Omit to create.
namestringyesThe customer's name (required).
notestring–A note about the customer.
phone_numberstring–Phone number.
postal_codestring–Postal / ZIP code.
regionstring–Province, state or prefecture.

No output schema declared.

No examples provided.

loyverse_upsert_supplier ~221

Create 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/.

NameTypeReqDescription
address_1string–Address line 1.
address_2string–Address line 2.
citystring–City, town or village.
contactstring–Contact person's name.
country_codestring–Two-letter ISO 3166-1 alpha-2 country code, e.g. US.
emailstring–Email address.
idstring–Existing supplier id to update. Omit to create.
namestringyesThe supplier company name (required).
notestring–A note about the supplier.
phone_numberstring–Phone number.
postal_codestring–Postal / ZIP code.
regionstring–Province, state or prefecture.
websitestring–Website URL.

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/loyverse MCP server?

io.usefulapi/loyverse is an MCP server listed in the public MCP registry as io.usefulapi/loyverse. Query Loyverse POS receipts, shifts, items, inventory and customers, and update stock and customers. This page covers its hosted endpoint (https://loyverse.usefulapi.io/mcp).

Is the io.usefulapi/loyverse MCP server safe to use?

io.usefulapi/loyverse scores 76 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 io.usefulapi/loyverse MCP server expose?

io.usefulapi/loyverse exposes 21 tools: loyverse_get_merchant, loyverse_list_stores, loyverse_list_employees, loyverse_list_receipts, loyverse_get_receipt, and 16 more. Their descriptions and schemas cost roughly 4,009 tokens of context every time the server is loaded.

Does the io.usefulapi/loyverse MCP server require authentication?

Yes. io.usefulapi/loyverse 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 io.usefulapi/loyverse MCP server still maintained?

io.usefulapi/loyverse is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.