Skip to content

Qut Pay (Kaspi QR payments) MCP server

kz.qut/mcpqut.kzstreamable-httpv0.1.5Scanned

Kaspi QR payments (Kazakhstan) via Qut Pay: invoices, refunds, subscriptions, payment links.

23 tools: 4 can delete or cancel things, 2 do something that can't be undone, 10 change things and 7 only read.

Tools: 4 delete, 2 irreversible, 10 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 23
  • Can send data out · 5
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

4 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Qut Pay (Kaspi QR payments) MCP server can do

The Qut Pay (Kaspi QR payments) MCP server is published by qut.kz, a domain the MCP Registry verified. It has 23 tools. It can delete or cancel things (4 tools: qutpay_cancel_invoice, qutpay_refund_invoice, qutpay_cancel_subscription and qutpay_delete_payment_link), do things that cannot be undone, such as sending, paying or publishing (qutpay_create_topup and qutpay_simulate_payment) and create or change data (10 tools: qutpay_create_invoice, qutpay_create_subscription, qutpay_update_subscription, qutpay_pause_subscription and 6 more). 7 tools only read.

23 tools bring in text other people can write (qutpay_account, qutpay_create_invoice, qutpay_create_topup and 20 more); 5 tools can send data out of your system (qutpay_create_invoice, qutpay_create_subscription, qutpay_update_subscription and 2 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.1.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

23 tools

Deletes or cancels 4Claude Code: deny
  • qutpay_cancel_invoiceCloses a pending invoice.Reads text others write1 finding

    Why it is in this group

    • The name "qutpay_cancel_invoice" says "cancel": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "qutpay_cancel_invoice" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "qutpay_cancel_invoice" says "cancel": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Closes a pending invoice. A QR may still be paid until expiresAt — then invoice.paid arrives anyway; handle it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • qutpay_cancel_subscriptionDESTRUCTIVE: ends the subscription for good — it cannot be resumed or edited afterwards (create a new one instead).Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_cancel_subscription" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    DESTRUCTIVE: ends the subscription for good — it cannot be resumed or edited afterwards (create a new one instead). Invoices already issued are not affected. To stop it for a while use qutpay_pause_subscription. With a LIVE key confirm=true is required, only after the merchant explicitly asked to cancel.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • qutpay_refund_invoiceFull refund (omit amount) or partial refund of a paid invoice.Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_refund_invoice" says "refund": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Can't be undone 2Claude Code: ask
  • qutpay_create_topupBalance top-up for a user of the merchant's own service (AI service, SaaS, website): a QR invoice whose metadata is { ref: userRef, pack, qutpay_kind: "topup" }.Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_create_topup" says "create": a word for a change.
    • The name "qutpay_create_topup" also says "topup": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Balance top-up for a user of the merchant's own service (AI service, SaaS, website): a QR invoice whose metadata is { ref: userRef, pack, qutpay_kind: "topup" }. The merchant keeps the balance in their own system and credits it on the invoice.paid webhook (idempotent by invoice id; subtract on invoice.refunded). Qut Pay holds no balance. Not for digital goods inside Telegram bots (Telegram requires Stars there). Returns payUrl like qutpay_create_invoice.

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
  • qutpay_simulate_paymentCompletes a sandbox invoice as paid / failed / expired without Kaspi, so the whole flow including the merchant's webhook can be tested.Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_simulate_payment" says "payment": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 10Claude Code: ask
  • qutpay_create_invoiceCreates an invoice (QR by default, or pushed to the customer's Kaspi.kz app with kind="phone").Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "qutpay_create_invoice" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.customer.phone): what the tool writes goes there.
    Description, as the server wrote it
    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".

    Annotations the server declares

    • readOnlyHint: false
    • idempotentHint: true
    • openWorldHint: true
  • qutpay_create_subscriptionCreates a schedule that issues an invoice every N days/weeks/months (gym pass, tutoring, rent, SaaS plan).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "qutpay_create_subscription" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.customer.phone): what the tool writes goes there.
    Description, as the server wrote it
    Creates a schedule that issues an invoice every N days/weeks/months (gym pass, tutoring, rent, SaaS plan). Each run is an invoice the customer confirms — in the Kaspi.kz app (kind="phone") or through a pay link; Kaspi has no card-on-file auto-debit. The customer's own page (customerUrl) shows the schedule. startAt sets the first run (default now). Needs subscriptions:manage or invoices:write.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • qutpay_pause_subscriptionStops issuing invoices until resumed.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "stop": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Stops issuing invoices until resumed. Reversible with qutpay_resume_subscription.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • qutpay_resume_subscriptionRe-activates a paused subscription in the organization's current mode.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Re-activates a paused subscription in the organization's current mode. If the next run time has already passed it is rescheduled from now; catchUp=true issues the missed invoice right away instead.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • qutpay_run_subscription_nowIssues the next invoice of a subscription immediately instead of waiting for nextRunAt and moves the schedule on, so the same period is never billed twice.Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_run_subscription_now" says "run": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Issues the next invoice of a subscription immediately instead of waiting for nextRunAt and moves the schedule on, so the same period is never billed twice. Returns { invoice (with payUrl), run, subscription }.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • qutpay_update_subscriptionChanges an active or paused subscription: amount, description, schedule (interval, every, dayOfMonth, nextRunAt), customer, maxRuns, reminders, metadata.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "qutpay_update_subscription" says "update": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.customer.phone): what the tool writes goes there.
    Description, as the server wrote it
    Changes an active or paused subscription: amount, description, schedule (interval, every, dayOfMonth, nextRunAt), customer, maxRuns, reminders, metadata. Only the fields passed change. Cancelled or finished subscriptions cannot be changed.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 7Show 7 read-only tools
  • qutpay_accountReturns the organization behind the API key: mode (sandbox or live), tariff and limits, connected Kaspi cashiers, provider status.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Returns the organization behind the API key: mode (sandbox or live), tariff and limits, connected Kaspi cashiers, provider status. Call this first.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • qutpay_get_invoiceReads one invoice by id (inv_…).Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_get_invoice" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • qutpay_get_subscriptionReads a recurring invoice schedule by id (sub_…): status, amount, interval, nextRunAt, last run and its error, customerUrl.Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_get_subscription" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Reads a recurring invoice schedule by id (sub_…): status, amount, interval, nextRunAt, last run and its error, customerUrl. Needs the invoices:read scope.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • qutpay_list_invoicesLists invoices of the organization, newest first.Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_list_invoices" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Lists invoices of the organization, newest first. Filter by status, externalOrderId, date range (ISO), limit ≤ 50, offset for paging.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • qutpay_list_subscriptionsLists recurring invoice schedules (subscriptions), newest first.Reads text others writeNo findings

    Why it is in this group

    • The name "qutpay_list_subscriptions" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Lists recurring invoice schedules (subscriptions), newest first. Needs the invoices:read scope.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out5
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:24 UTC, unchanged since Oct 26, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (2 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.qut.kz/mcp: tools/list returned 9 tools to an anonymous client, including qutpay_cancel_invoice (destructive), qutpay_refund_invoice (destructive), qutpay_simulate_payment (irreversible), qutpay_create_invoice (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "qutpay_cancel_invoice" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "qutpay_cancel_invoice" says "cancel": a word for removing or ending something.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools14 added, 2 changed.+14 added~2 changedView diff

Install

Pinned to version 0.1.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http qut https://api.qut.kz/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http qut https://api.qut.kz/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__qut__qutpay_account",
      "mcp__qut__qutpay_get_invoice",
      "mcp__qut__qutpay_list_invoices",
      "mcp__qut__qutpay_list_subscriptions",
      "mcp__qut__qutpay_get_subscription",
      "mcp__qut__qutpay_list_payment_links",
      "mcp__qut__qutpay_get_payment_link"
    ],
    "ask": [
      "mcp__qut__qutpay_create_invoice",
      "mcp__qut__qutpay_create_topup",
      "mcp__qut__qutpay_simulate_payment",
      "mcp__qut__qutpay_create_subscription",
      "mcp__qut__qutpay_update_subscription",
      "mcp__qut__qutpay_pause_subscription",
      "mcp__qut__qutpay_resume_subscription",
      "mcp__qut__qutpay_run_subscription_now",
      "mcp__qut__qutpay_create_payment_link",
      "mcp__qut__qutpay_update_payment_link",
      "mcp__qut__qutpay_pause_payment_link",
      "mcp__qut__qutpay_resume_payment_link"
    ],
    "deny": [
      "mcp__qut__qutpay_cancel_invoice",
      "mcp__qut__qutpay_refund_invoice",
      "mcp__qut__qutpay_cancel_subscription",
      "mcp__qut__qutpay_delete_payment_link"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as qut. Review it before you use it.

Capability tags behind 23 rules
  • mcp__qut__qutpay_account untrusted-input
  • mcp__qut__qutpay_create_invoice untrusted-input, outbound
  • mcp__qut__qutpay_create_topup untrusted-input
  • mcp__qut__qutpay_get_invoice untrusted-input
  • mcp__qut__qutpay_list_invoices untrusted-input
  • mcp__qut__qutpay_cancel_invoice untrusted-input
  • mcp__qut__qutpay_refund_invoice untrusted-input
  • mcp__qut__qutpay_simulate_payment untrusted-input
  • mcp__qut__qutpay_list_subscriptions untrusted-input
  • mcp__qut__qutpay_get_subscription untrusted-input
  • mcp__qut__qutpay_create_subscription untrusted-input, outbound
  • mcp__qut__qutpay_update_subscription untrusted-input, outbound
  • mcp__qut__qutpay_pause_subscription untrusted-input
  • mcp__qut__qutpay_resume_subscription untrusted-input
  • mcp__qut__qutpay_cancel_subscription untrusted-input
  • mcp__qut__qutpay_run_subscription_now untrusted-input
  • mcp__qut__qutpay_create_payment_link untrusted-input, outbound
  • mcp__qut__qutpay_list_payment_links untrusted-input
  • mcp__qut__qutpay_get_payment_link untrusted-input
  • mcp__qut__qutpay_update_payment_link untrusted-input, outbound
  • mcp__qut__qutpay_pause_payment_link untrusted-input
  • mcp__qut__qutpay_resume_payment_link untrusted-input
  • mcp__qut__qutpay_delete_payment_link untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/kz.qut/mcp/verify?hash=c1f77997d086982ddec0a8adccc57a49e21be1fea4c07593a1793ecc27ee3838" | jq -e '.changed == false'

Pinned hash c1f77997d086, from Nov 18, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/kz.qut/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for kz.qut/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/kz.qut/mcp.svg)](https://radar.anlyon.com/servers/kz.qut/mcp)

Source: MCP Registry · repository. Synced Nov 18, 2026, 06:17 UTC.

Qut Pay (Kaspi QR payments) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Qut Pay (Kaspi QR payments) MCP server safe?

No scan can promise that. What its definitions show: 23 tools, 16 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Qut Pay (Kaspi QR payments) MCP server delete data?

Yes. 4 tools can delete, cancel or revoke something: qutpay_cancel_invoice, qutpay_refund_invoice, qutpay_cancel_subscription and qutpay_delete_payment_link.

Can the Qut Pay (Kaspi QR payments) MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: qutpay_create_topup and qutpay_simulate_payment.

What tools does the Qut Pay (Kaspi QR payments) MCP server have?

23 tools: 4 destructive, 2 irreversible, 10 write, 7 read. qutpay_cancel_invoice, qutpay_refund_invoice, qutpay_cancel_subscription, qutpay_delete_payment_link, qutpay_create_topup, qutpay_simulate_payment, qutpay_create_invoice, qutpay_create_subscription and 15 more.

Does the Qut Pay (Kaspi QR payments) MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Qut Pay (Kaspi QR payments) MCP server send data to outside services?

5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): qutpay_create_invoice, qutpay_create_subscription, qutpay_update_subscription, qutpay_create_payment_link and qutpay_update_payment_link.

Has the Qut Pay (Kaspi QR payments) MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.