Qut Pay (Kaspi QR payments)
REMOTE · API.QUT.KZ · 2 COMPONENTS
Kaspi QR payments (Kazakhstan) via Qut Pay: create invoices, check status, refund, sandbox tests.
Available components
Last scanned (19 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (qutpay_refund_invoice). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1010 tokens (~72/item across 14 items; 9 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 41% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 66
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 4 Nov 2026 · Probed https://api.qut.kz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qut.kz | CN=YE1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 585427645f27c47280d47be5f994d8cd8fa |
| SANs: api.qut.kz, qut.kz, www.qut.kz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.qut.kz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| kz. | present | 10656 | 13 | Verified |
| qut.kz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.qut.kz/mcp | Verified | 200 | |
| http (plaintext) | http://api.qut.kz/mcp | HTTPS enforced | 301 | https://api.qut.kz/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 →
qutpay_account Qut Pay account and mode ~41
Returns the organization behind the API key: mode (sandbox or live), tariff and limits, connected Kaspi cashiers, provider status. Call this first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qutpay_cancel_invoice Cancel an open invoice ~44
Closes a pending invoice. A QR may still be paid until expiresAt — then invoice.paid arrives anyway; handle it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
qutpay_create_invoice Create a Kaspi invoice ~252
Creates an invoice (QR by default, or pushed to the customer's Kaspi.kz app with kind="phone"). Returns payUrl (hosted pay page), qrImageUrl, deepLink, expiresAt (~3 min). Always pass idempotencyKey (e.g. "order-1001") so a retry never creates a second invoice. Amount in KZT, ≤ 2 decimals; whole tenge for kind="phone".
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount in KZT, e.g. 2500 or 1500.5 |
| customer | object | – | – |
| description | string | – | Shown to the customer, e.g. "Order #1001" |
| externalOrderId | string | – | Your order id; later GET /invoices?externalOrderId finds it |
| failUrl | string | – | – |
| idempotencyKey | string | – | Unique per order; same key → same invoice |
| kind | string | – | "qr" (default) or "phone" (invoice pushed into the customer's Kaspi.kz app; needs customer.phone) |
| metadata | object | – | Returned unchanged in webhooks |
| successUrl | string | – | – |
No output schema declared.
No examples provided.
qutpay_get_invoice Get invoice status ~70
Reads one invoice by id (inv_…). live=true asks Kaspi right now instead of the cached status. Status flow: new → pending → paid | failed | expired | cancelled; paid → partially_refunded → refunded.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| live | boolean | – | – |
No output schema declared.
No examples provided.
qutpay_get_subscription Get one subscription ~36
Reads a recurring invoice schedule by id (sub_…). Needs the subscriptions:manage scope.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
qutpay_list_invoices List invoices ~97
Lists invoices of the organization, newest first. Filter by status, externalOrderId, date range (ISO), limit ≤ 50, offset for paging.
| Name | Type | Req | Description |
|---|---|---|---|
| externalOrderId | string | – | – |
| from | string | – | ISO date/time, inclusive |
| limit | integer | – | – |
| offset | integer | – | – |
| status | string | – | – |
| to | string | – | ISO date/time, exclusive |
No output schema declared.
No examples provided.
qutpay_list_subscriptions List scheduled invoices (subscriptions) ~44
Read-only list of recurring invoice schedules. Needs the subscriptions:manage scope on the key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
qutpay_refund_invoice Refund a paid invoice ~103
Full refund (omit amount) or partial refund of a paid invoice. Needs the refunds:write scope. With a LIVE key real money is returned to the customer, so confirm=true is required and the merchant must have asked for this refund explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Omit for a full refund |
| confirm | boolean | – | Required (true) with a live key |
| id | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
qutpay_simulate_payment Simulate a payment (sandbox only) ~66
Completes a sandbox invoice as paid / failed / expired without Kaspi, so the whole flow including the merchant's webhook can be tested. Refuses to run with a live key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| status | string | – | Default "paid" |
No output schema declared.
No examples provided.
How do I install the Qut Pay (Kaspi QR payments) MCP server?
Qut Pay (Kaspi QR payments) is a hosted endpoint at https://api.qut.kz/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 · api.qut.kz
claude mcp add --transport http kz-qut-mcp 'https://api.qut.kz/mcp'
What is the Qut Pay (Kaspi QR payments) MCP server?
Qut Pay (Kaspi QR payments) is an MCP server listed in the public MCP registry as kz.qut/mcp. Kaspi QR payments (Kazakhstan) via Qut Pay: create invoices, check status, refund, sandbox tests. This page covers its hosted endpoint (https://api.qut.kz/mcp).
Is the Qut Pay (Kaspi QR payments) MCP server safe to use?
Qut Pay (Kaspi QR payments) scores 70 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 Qut Pay (Kaspi QR payments) MCP server expose?
Qut Pay (Kaspi QR payments) exposes 9 tools: qutpay_account, qutpay_create_invoice, qutpay_get_invoice, qutpay_list_invoices, qutpay_cancel_invoice, and 4 more. Their descriptions and schemas cost roughly 753 tokens of context every time the server is loaded.
Does the Qut Pay (Kaspi QR payments) MCP server require authentication?
No. We connected to Qut Pay (Kaspi QR payments) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Qut Pay (Kaspi QR payments) MCP server still maintained?
Qut Pay (Kaspi QR payments) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.