Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KHQRPAY_API_BASENoAnother KHQRPay address, for testing. Must be https, or http on localhost.
KHQRPAY_SECRET_KEYYesYour KHQRPay key. Use a `kp_test_` key for every tool, or a `kp_live_` key for the read tools only when `KHQRPAY_MCP_LIVE_READS` is also set.
KHQRPAY_MCP_LIVE_READSNoSet to `1` to let a live key read payments and usage. Nothing ever creates or changes live payments.
KHQRPAY_WEBHOOK_SECRETNoA webhook endpoint's signing secret, for `check_webhook_signature`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_test_paymentA

Creates a KHQRPay test payment: a KHQR that no bank will pay, with a hosted checkout page. Only with a kp_test_ key: this server never creates live payments. Returns the payment, including checkout_url and expires_at. Move it with simulate_test_payment; the store's test webhook endpoints get the events.

simulate_test_paymentA

Moves a test payment to scanned, paid, expired or failed, as if the customer and the bank had acted, and the store's test webhook endpoints get the matching event. Test payments only. To try a late payment, simulate expired and then paid. A status the payment can't move to changes nothing.

get_paymentA

Reads one payment by its id: status (pending, scanned, paid, expired or failed), amounts, expiry, and whether it was paid late. Each call counts toward the account's daily read allowance, so read when you need the answer and never poll in a loop; application code should follow payments with webhooks.

list_paymentsA

Lists the store's payments in the key's mode, newest first, one page at a time; each leaves out metadata, which get_payment returns. Each call counts toward the account's daily read allowance, so read when you need the answer and never poll in a loop; application code should follow payments with webhooks.

get_usageA

Shows the account's plan, its paid transactions used and left this period, and when the period ends. Only paid live payments count; test payments never do.

check_webhook_signatureA

Checks an X-KHQRPay-Signature header against a webhook's raw body, with the signing secret from this server's KHQRPAY_WEBHOOK_SECRET (the secret is never an argument and never shown). Says why a check fails: a malformed header, a timestamp more than 5 minutes off, or a mismatch. Runs on this machine; nothing is sent anywhere.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: usage/limits (get_usage), creation (create_test_payment), state transition (simulate_test_payment), single read (get_payment), bulk read (list_payments), and webhook verification (check_webhook_signature). The only near-neighbors, get_payment vs list_payments and create_test_payment vs simulate_test_payment, are explicitly differentiated by 'one payment' vs 'one page' and 'create' vs 'move' language.

Naming Consistency5/5

All six tools follow a uniform snake_case verb_noun pattern (get_, create_, simulate_, list_, check_). The shared test_payment suffix groups related tools rather than creating inconsistency.

Tool Count5/5

Six tools is well-scoped for a test-only payment API: usage, create, simulate, get, list, and signature check each cover a distinct step with no filler. Nothing feels padded or missing at the count level.

Completeness4/5

The test-payment lifecycle is closed: create -> simulate (including expired-then-paid for late payments) -> get/list -> verify webhook signature, plus account usage. Minor gaps remain: no refund/cancel operation, no webhook endpoint registration or event listing, and live payments are excluded by design.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues