_ registry / mcp streamable-http · checked 1h ago

qutpay

https://api.qut.kz

Registry code: 0bc5ffe416eabd07

api record

Qut Pay — Kaspi QR payments for Kazakhstan. Mode of this key: anonymous. Start with qutpay_account. Create invoices with an idempotencyKey per order; the customer pays at payUrl; the merchant's webhook (registered in the cabinet) marks the order paid. In sandbox use qutpay_simulate_payment to complete a test payment. Read resource qutpay://skill for the integration procedure. Never ask the merchant to paste the API key into chat.

endpoint
https://api.qut.kz/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is qutpay live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is qutpay free to use?
Not measured yet.
What tools does qutpay have?
9 tools: qutpay_account, qutpay_list_invoices, qutpay_refund_invoice, qutpay_create_invoice, qutpay_get_invoice, qutpay_cancel_invoice, qutpay_simulate_payment, qutpay_list_subscriptions, ….
Is qutpay safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
308ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
9 never probed 0 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • qutpay_account unknown never probed

    Returns the organization behind the API key: mode (sandbox or live), tariff and limits, connected Kaspi cashiers, provider status. Call this first.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • qutpay_list_invoices unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "to": {
      "type": "string",
      "description": "ISO date/time, exclusive"
    },
    "from": {
      "type": "string",
      "description": "ISO date/time, inclusive"
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    },
    "status": {
      "enum": [
        "new",
        "pending",
        "paid",
        "failed",
        "expired",
        "cancelled",
        "partially_refunded",
        "refunded"
      ],
      "type": "string"
    },
    "externalOrderId": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • qutpay_refund_invoice unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    },
    "amount": {
      "type": "number",
      "description": "Omit for a full refund",
      "exclusiveMinimum": 0
    },
    "reason": {
      "type": "string",
      "maxLength": 255
    },
    "confirm": {
      "type": "boolean",
      "description": "Required (true) with a live key"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • qutpay_create_invoice unknown never probed

    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".

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "amount"
  ],
  "properties": {
    "kind": {
      "enum": [
        "qr",
        "phone"
      ],
      "type": "string",
      "description": "\"qr\" (default) or \"phone\" (invoice pushed into the customer's Kaspi.kz app; needs customer.phone)"
    },
    "amount": {
      "type": "number",
      "description": "Amount in KZT, e.g. 2500 or 1500.5",
      "exclusiveMinimum": 0
    },
    "failUrl": {
      "type": "string",
      "format": "uri"
    },
    "customer": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string"
        },
        "email": {
          "type": "string",
          "format": "email"
        },
        "phone": {
          "type": "string",
          "pattern": "^7\\d{10}$",
          "description": "7XXXXXXXXXX"
        }
      },
      "additionalProperties": false
    },
    "metadata": {
      "type": "object",
      "description": "Returned unchanged in webhooks",
      "additionalProperties": {}
    },
    "successUrl": {
      "type": "string",
      "format": "uri"
    },
    "description": {
      "type": "string",
      "maxLength": 255,
      "description": "Shown to the customer, e.g. \"Order #1001\""
    },
    "idempotencyKey": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "Unique per order; same key → same invoice"
    },
    "externalOrderId": {
      "type": "string",
      "maxLength": 120,
      "description": "Your order id; later GET /invoices?externalOrderId finds it"
    }
  },
  "additionalProperties": false
}
    arguments 70 lines
  • qutpay_get_invoice unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    },
    "live": {
      "type": "boolean"
    }
  },
  "additionalProperties": false
}
    arguments 17 lines
  • qutpay_cancel_invoice unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • qutpay_simulate_payment unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    },
    "status": {
      "enum": [
        "paid",
        "failed",
        "expired"
      ],
      "type": "string",
      "description": "Default \"paid\""
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • qutpay_list_subscriptions unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "status": {
      "enum": [
        "active",
        "paused",
        "cancelled"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • qutpay_get_subscription unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0bc5ffe416eabd07.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0bc5ffe416eabd07/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0bc5ffe416eabd07/badge.svg)](https://brick.blue/agent/0bc5ffe416eabd07?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.