# Qut MCP server

Source: https://glimind.com/server/mcp-registry%2Fkz.qut%2Fmcp
Registry id: `mcp-registry/kz.qut/mcp`
Status: live (checked 2026-11-22T17:14:41.949Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 705
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "qut-mcp-server": {
      "type": "http",
      "url": "https://api.qut.kz/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http qut-mcp-server https://api.qut.kz/mcp
```

## Tools (25)

- `qutpay_account`: Returns the organization behind the API key: mode (sandbox or live), tariff and limits, connected Kaspi cashiers, provider status. Call this first.
- `qutpay_cancel_invoice`: Closes a pending invoice. A QR may still be paid until expiresAt — then invoice.paid arrives anyway; handle it.
- `qutpay_cancel_subscription`: 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
- `qutpay_create_invoice`: Creates an invoice (QR by default, or pushed to the customer's Kaspi.kz app with kind="phone"). Returns payUrl (hosted pay page), qrImageUrl (SVG), qrPngUrl (PN
- `qutpay_create_payment_link`: Creates a permanent page /p/<slug> with a printable QR: a fixed price, a customer-entered amount (optionally with min/max), or 2–6 top-up packs shown as buttons
- `qutpay_create_subscription`: 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
- `qutpay_create_topup`: 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" }
- `qutpay_delete_payment_link`: DESTRUCTIVE: removes the link for good — its page and every printed QR stop working and the slug is freed. Invoices already paid through it are kept. To stop it
- `qutpay_get_invoice`: 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; 
- `qutpay_get_payment_link`: Reads a payment link by id (pl_…): settings, packs, url, qrImageUrl, status, hits (page views) and invoicesCount (live invoices created from it).
- `qutpay_get_subscription`: Reads a recurring invoice schedule by id (sub_…): status, amount, interval, nextRunAt, last run and its error, customerUrl. Needs the invoices:read scope.
- `qutpay_get_subscription_customer`: The customer side of a subscription: customerUrl (their page: schedule, last invoice, «Pay»), telegramUrl (one tap turns on Telegram reminders), whether Telegra
- `qutpay_list_invoices`: Lists invoices of the organization, newest first. Filter by status, externalOrderId, date range (ISO), limit ≤ 50, offset for paging.
- `qutpay_list_payment_links`: Lists the organization's payment links, newest first, with url, qrImageUrl, status, hits (page views) and invoicesCount. Filter by status; limit ≤ 100, offset f
- `qutpay_list_subscriptions`: Lists recurring invoice schedules (subscriptions), newest first. Needs the invoices:read scope.
- `qutpay_pause_payment_link`: The page stays reachable but takes no payments until resumed (customers see that it is paused). Reversible with qutpay_resume_payment_link.
- `qutpay_pause_subscription`: Stops issuing invoices until resumed. Reversible with qutpay_resume_subscription.
- `qutpay_refund_invoice`: 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
- `qutpay_remind_subscription_customer`: Sends the customer a reminder right away through every channel that reaches them (Telegram, e-mail, WhatsApp within the monthly quota; never to a number that an
- `qutpay_resume_payment_link`: Lets a paused payment link take payments again.
- `qutpay_resume_subscription`: 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 t
- `qutpay_run_subscription_now`: 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. Retu
- `qutpay_simulate_payment`: 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 li
- `qutpay_update_payment_link`: Changes title, description, price or limits, packs (null removes them), required fields or successUrl. Only the fields passed change; the slug — and so the prin
- `qutpay_update_subscription`: Changes an active or paused subscription: amount, description, schedule (interval, every, dayOfMonth, nextRunAt), customer, maxRuns, reminders, metadata. Only t

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
