Zettle MCP by usefulapi
REMOTE · ZETTLE.USEFULAPI.IO
Read sales, products, stock, balance and payouts; create products in Zettle.
Available components
Last scanned (9 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 6 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 65
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 6 Nov 2026 · Probed https://zettle.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 zettle.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://zettle.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/zettle/ |
| http (plaintext) | http://zettle.usefulapi.io/mcp | Inconclusive | 302 | http://zettle.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 →
zettle_create_product Create product ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Product description. |
| name | string | yes | Product name. |
| variants | array | yes | 1-99 variants (a product without options has one). |
| vat_percentage | number | yes | VAT percent, e.g. 25. Must match a rate set in the merchant's Zettle account. |
No output schema declared.
No examples provided.
zettle_get_account Get account ~35
The Zettle user and organization this API key belongs to (uuid, organizationUuid). GET oauth.zettle.com/users/self.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zettle_get_account_balance Get account balance ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | LIQUID (available for payout) or PRELIMINARY (not yet settled). |
| at | string | – | Balance as of this UTC date-time (default now). |
No output schema declared.
No examples provided.
zettle_get_library Get product library with discounts ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page, 1-500 (default 100). |
| offset | integer | – | Position to start from (default 0); use next_offset of the previous reply. |
No output schema declared.
No examples provided.
zettle_get_payout_info Get payout info ~70
Payout information of the LIQUID account: totalBalance, currencyId, nextPayoutAmount, discountRemaining and payout periodicity. Needs READ:FINANCE. GET /v2/payout-info.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | As of this UTC date-time (default now). |
No output schema declared.
No examples provided.
zettle_get_product Get product ~54
One product by UUID with all variants, prices, VAT, category, images and online-store data. Needs READ:PRODUCT. GET /organizations/self/products/{productUuid}.
| Name | Type | Req | Description |
|---|---|---|---|
| product_uuid | string | yes | Product UUID. |
No output schema declared.
No examples provided.
zettle_get_purchase Get purchase ~117
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| purchase_uuid | string | yes | Purchase UUID: the purchaseUUID1 field (a UUID such as 589c2de6-3ee4-11eb-9e70-a2ac075b17fd). |
No output schema declared.
No examples provided.
zettle_get_stock Get stock balances ~134
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
zettle_get_stock_for_products Get stock for products ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor of the previous reply, for the next page. |
| inventory_uuid | string | yes | The inventory (see zettle_list_inventories). |
| limit | integer | – | Balances per page, 1-1000 (default 100). |
| product_uuids | array | yes | 1-100 product UUIDs. |
No output schema declared.
No examples provided.
zettle_list_account_transactions List account transactions ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | LIQUID or PRELIMINARY. |
| end | string | yes | 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 | yes | Start, UTC date or date-time (inclusive), e.g. 2026-10-01. |
| types | array | – | Only these transaction types (default all). |
No output schema declared.
No examples provided.
zettle_list_categories List categories ~32
List the product categories (uuid, name). Needs READ:PRODUCT. GET /organizations/self/categories/v2.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zettle_list_inventories List inventories (stock locations) ~67
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zettle_list_products List products ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
zettle_list_purchases List purchases ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
remote · zettle.usefulapi.io
claude mcp add --transport http io-usefulapi-zettle 'https://zettle.usefulapi.io/mcp'
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.