# Zettle MCP by usefulapi (remote · zettle.usefulapi.io)

Read sales, products, stock, balance and payouts; create products in Zettle.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `zettle.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-zettle/zettle.md), [page](https://verifymcp.io/servers/io-usefulapi-zettle/zettle)

## Channel facts

- Endpoint: `https://zettle.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.4`

## 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-11-06.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - 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.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Zettle MCP by usefulapi server?

Zettle MCP by usefulapi is a hosted endpoint at https://zettle.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-zettle 'https://zettle.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-zettle": {
      "url": "https://zettle.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  io-usefulapi-zettle:
    url: "https://zettle.usefulapi.io/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-zettle": {
      "type": "http",
      "url": "https://zettle.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-11-06 (score 18, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-02 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 65)

First indexed and scored.

## MCP tools (14)

### `zettle_get_account` (~35 tokens)

Get account

The Zettle user and organization this API key belongs to (uuid, organizationUuid). GET oauth.zettle.com/users/self.

### `zettle_list_purchases` (~209 tokens)

List purchases

List POS purchases (sales and refunds) with amount, currency, timestamp, products, discounts, payments, refund info and the cashier. Needs READ:PURCHASE. Amounts are in the smallest currency unit. Default window is the last 3 years. Page with next_page_hash (pass it back as last_purchase_hash with the same other arguments). GET /purchases/v2.

Input parameters:

- `descending` (boolean): true = most recent first (default false: oldest first).
- `end_date` (string): Only purchases before this UTC date or date-time (exclusive), e.g. 2026-10-08.
- `last_purchase_hash` (string): next_page_hash of the previous reply, for the next page.
- `limit` (integer): Purchases per page, 1-1000 (default 25).
- `start_date` (string): Only purchases from this UTC date or date-time on (inclusive), e.g. 2026-10-01.

### `zettle_get_purchase` (~117 tokens)

Get purchase

One purchase (sale or refund) in full by its purchase UUID (the purchaseUUID1 field of zettle_list_purchases; the older short purchaseUUID is deprecated and not accepted): line items, VAT, payments, refund links. Needs READ:PURCHASE. GET /purchase/v2/{purchaseUuid}.

Input parameters:

- `purchase_uuid` (string, required): Purchase UUID: the purchaseUUID1 field (a UUID such as 589c2de6-3ee4-11eb-9e70-a2ac075b17fd).

### `zettle_list_products` (~143 tokens)

List products

List the products in the POS product library with variants (SKU, barcode, price, cost price, VAT), category, online status and ETag. Zettle returns the whole library at once; this tool slices it with limit/offset and filters by name. Needs READ:PRODUCT. Prices are in the smallest currency unit. GET /organizations/self/products/v2.

Input parameters:

- `limit` (integer): Products to return, 1-200 (default 50).
- `name_contains` (string): Only products whose name contains this text (case-insensitive).
- `offset` (integer): Products to skip (default 0). Use next_offset of the previous reply.

### `zettle_get_product` (~54 tokens)

Get product

One product by UUID with all variants, prices, VAT, category, images and online-store data. Needs READ:PRODUCT. GET /organizations/self/products/{productUuid}.

Input parameters:

- `product_uuid` (string, required): Product UUID.

### `zettle_list_categories` (~32 tokens)

List categories

List the product categories (uuid, name). Needs READ:PRODUCT. GET /organizations/self/categories/v2.

### `zettle_get_library` (~94 tokens)

Get product library with discounts

The product library together with its discounts (name, amount or percentage), paginated. Returns products, discounts and next_offset (pass it back as offset). Needs READ:PRODUCT. GET /organizations/self/library.

Input parameters:

- `limit` (integer): Items per page, 1-500 (default 100).
- `offset` (integer): Position to start from (default 0); use next_offset of the previous reply.

### `zettle_create_product` (~155 tokens)

Create product

WRITE: add a new product to the Zettle product library (it appears in the POS and, if enabled, the online store). Not idempotent: calling twice creates two products. Needs READ:PRODUCT and WRITE:PRODUCT. vat_percentage must be one of the VAT rates enabled in the merchant's Zettle settings. Prices are in the smallest currency unit. POST /organizations/self/products.

Input parameters:

- `description` (string): Product description.
- `name` (string, required): Product name.
- `variants` (array, required): 1-99 variants (a product without options has one).
- `vat_percentage` (number, required): VAT percent, e.g. 25. Must match a rate set in the merchant's Zettle account.

### `zettle_list_inventories` (~67 tokens)

List inventories (stock locations)

List the stock locations (inventories): inventoryUuid, name, type (STORE, SOLD, SUPPLIER, BIN) and which is the default. Use the STORE inventoryUuid with zettle_get_stock. Needs READ:PRODUCT. GET /v3/inventories.

### `zettle_get_stock` (~134 tokens)

Get stock balances

Stock balances per product variant (balance, low-stock level and alert, last update). With inventory_uuid: that STORE inventory only; without: all stores. Only products with inventory tracking enabled appear. Needs READ:PRODUCT. Page with next_cursor. GET /v3/stock or /v3/stock/{inventoryUuid}.

Input parameters:

- `cursor` (string): next_cursor of the previous reply, for the next page.
- `inventory_uuid` (string): Limit to this inventory (see zettle_list_inventories).
- `limit` (integer): Balances per page, 1-1000 (default 100).

### `zettle_get_stock_for_products` (~141 tokens)

Get stock for products

Stock balances of a few specific products in one inventory (read-only lookup, nothing is changed). Needs READ:PRODUCT. Page with next_cursor (send the same product_uuids again). POST /v3/stock/{inventoryUuid}/products with the product UUIDs.

Input parameters:

- `cursor` (string): next_cursor of the previous reply, for the next page.
- `inventory_uuid` (string, required): The inventory (see zettle_list_inventories).
- `limit` (integer): Balances per page, 1-1000 (default 100).
- `product_uuids` (array, required): 1-100 product UUIDs.

### `zettle_get_account_balance` (~118 tokens)

Get account balance

The merchant's Zettle account balance (totalBalance in the smallest currency unit, currencyId). LIQUID = money available for payout; PRELIMINARY = payments not yet settled. Optional point in time. Needs READ:FINANCE. GET /v2/accounts/{LIQUID|PRELIMINARY}/balance.

Input parameters:

- `account` (string, required): LIQUID (available for payout) or PRELIMINARY (not yet settled).
- `at` (string): Balance as of this UTC date-time (default now).

### `zettle_list_account_transactions` (~202 tokens)

List account transactions

Transactions (payments, fees, payouts, adjustments) in the LIQUID or PRELIMINARY account between start and end (end exclusive), with timestamp, amount (smallest currency unit, can be negative), type and originating transaction UUID. Needs READ:FINANCE. Page with next_offset. GET /v2/accounts/{account}/transactions.

Input parameters:

- `account` (string, required): LIQUID or PRELIMINARY.
- `end` (string, required): End, UTC date or date-time (exclusive), e.g. 2026-11-01.
- `limit` (integer): Transactions per page, 1-1000 (default 100).
- `offset` (integer): Transactions to skip (default 0); use next_offset.
- `start` (string, required): Start, UTC date or date-time (inclusive), e.g. 2026-10-01.
- `types` (array): Only these transaction types (default all).

### `zettle_get_payout_info` (~70 tokens)

Get payout info

Payout information of the LIQUID account: totalBalance, currencyId, nextPayoutAmount, discountRemaining and payout periodicity. Needs READ:FINANCE. GET /v2/payout-info.

Input parameters:

- `at` (string): As of this UTC date-time (default now).

## Diagnostics

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

## Score history

- 2026-11-06: 18
- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 66
- 2026-10-31: 65

## Common questions

### What is the Zettle MCP by usefulapi server?

Zettle MCP by usefulapi is listed in the public MCP registry as io.usefulapi/zettle. Read sales, products, stock, balance and payouts; create products in Zettle. This page covers its hosted endpoint (https://zettle.usefulapi.io/mcp).

### Is the Zettle MCP by usefulapi server safe to use?

Zettle MCP by usefulapi scores 18 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 Zettle MCP by usefulapi server expose?

Zettle MCP by usefulapi exposes 14 tools: zettle_get_account, zettle_list_purchases, zettle_get_purchase, zettle_list_products, zettle_get_product, and 9 more. Their descriptions and schemas cost roughly 1,571 tokens of context every time the server is loaded.

### Does the Zettle MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Zettle MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Zettle MCP by usefulapi server still maintained?

Zettle MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Zettle MCP by usefulapi server?

VerifyMCP ran 4 checks on Zettle MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Zettle MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://zettle.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/zettle/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-zettle/zettle.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-zettle/zettle/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-zettle/zettle.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-zettle/zettle