Qut Pay (Kaspi QR payments)

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Computer or cloud
• Transport: stdio, Streamable HTTP
• Category: Accounting, finance & tax
• You need to fill in: QUTPAY_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet
• npmNode.js installed (for the npx command)

Which app do you use?

{
  "mcpServers": {
    "qut": {
      "command": "npx",
      "args": [
        "-y",
        "@qutpay/mcp"
      ],
      "env": {
        "QUTPAY_API_KEY": "your-value",
        "QUTPAY_BASE_URL": "your-value"
      }
    }
  }
}

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

claude mcp add qut --env QUTPAY_API_KEY=your-value --env QUTPAY_BASE_URL=your-value -- npx -y @qutpay/mcp

{
  "mcpServers": {
    "qut": {
      "url": "https://api.qut.kz/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "mcpServers": {
    "qut": {
      "command": "npx",
      "args": [
        "-y",
        "@qutpay/mcp"
      ],
      "env": {
        "QUTPAY_API_KEY": "your-value",
        "QUTPAY_BASE_URL": "your-value"
      }
    }
  }
}

{
  "servers": {
    "qut": {
      "type": "http",
      "url": "https://api.qut.kz/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "qut": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@qutpay/mcp"
      ],
      "env": {
        "QUTPAY_API_KEY": "your-value",
        "QUTPAY_BASE_URL": "your-value"
      }
    }
  }
}

Your choice stays on this device in a cookie; no account needed.

Values you fill in

• QUTPAY_API_KEY secret required env
  Qut Pay API key (qp_test_… sandbox or qp_live_…), from the cabinet → Integrations → API keys
• QUTPAY_BASE_URL env
  API base URL, default https://api.qut.kz
• Authorization secret required HTTP header
  Bearer

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

• 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_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, deepLink, expiresAt (~3 min). Always pass idempotencyKey (e.g. "order-1001") so a retry never creates a second invoice. Amount in KZT, ≤ 2

• 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; paid → partially_refunded → refunded.

• qutpay_list_invoices

  Lists invoices of the organization, newest first. Filter by status, externalOrderId, date range (ISO), limit ≤ 50, offset for paging.

• qutpay_cancel_invoice

  Closes a pending invoice. A QR may still be paid until expiresAt — then invoice.paid arrives anyway; handle it.

• 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=true is required and the merchant must have asked for this refund explicitly.

• 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 live key.

• qutpay_list_subscriptions

  Read-only list of recurring invoice schedules. Needs the subscriptions:manage scope on the key.

• qutpay_get_subscription

  Reads a recurring invoice schedule by id (sub_…). Needs the subscriptions:manage scope.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain qut.kz (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 1398 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 9 tool descriptions and found no hidden instructions to the AI

Compared with others in Accounting, finance & taxi

• More stars than 0% of the other 2915 servers in this category
• Published to the registry more recently than 70% of the other 2915 servers in this category
• Basic checks equal to or better than 100% of the other 2915 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

claude mcp add qutpay -e QUTPAY_API_KEY=qp_test_… -- npx -y @qutpay/mcp

{