@klappay/mcp
OfficialRelated Servers
Alternatives to @klappay/mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to read and modify an Acumulus administration through natural language over the official API, including invoices, picklists, and direct endpoint calls. Runs locally over stdio and supports test mode to validate writes without persisting them.427 PyPIAGPL 3.0
- AlicenseNot gradedqualityBmaintenanceLets AI clients work with one or more Stax Payments merchant accounts over stdio, discovering and switching between accounts, finding customers, listing saved payment methods, and reading transactions. Read-only by default, with opt-in write tools for creating customers, charging saved payment methods, capturing, refunding, and voiding transactions.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to integrate stablecoin crypto checkout into applications by registering workspaces, configuring settlement wallets and webhooks, creating payment links and invoices, and verifying payment status and webhook signatures. It exposes these payment operations as tools over stdio so agents can complete end-to-end payment setup without manual dashboard work.-

cryptbrew-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to answer Cryptbrew product questions and check live API health without merchant authentication. Exposes tools for pricing, FAQs, invoice flow, and health probes over stdio or streamable HTTP.8MIT- AlicenseNot gradedqualityCmaintenanceEnables local AI clients such as Claude Code and Cursor to search, analyze, and monitor prediction-market data, and, once live mode is explicitly switched on, sign and submit CLOB orders from the operator's own wallet. It runs in a safe preview mode by default, writing simulated trades to local SQLite instead of sending orders.115 npm3MIT
- AlicenseAqualityAmaintenanceAPI client for coding agents. Sends saved HTTP, GraphQL and gRPC requests, runs collections with their checks, and creates or edits requests over stdio or loopback HTTP, with secret values redacted and calls limited to an allowlist of hosts.1792MIT
TDQS
Scored across 14 tools
Each tool maps to a distinct resource and action: charges get/list/timeline/check/create, webhook list/deliveries/retry, escrow prepare release vs refund, plus networks, metrics, sandbox, and environment status. The read-only prepare tools are clearly separated from execution and from charge inspection, so an agent can select reliably.
Most tool names follow a predictable resource_action snake_case pattern (charges_get, webhooks_list_deliveries, networks_get, metrics_query). The main deviation is klap_status, which breaks the resource-prefix convention but remains readable and clearly scoped.
Fourteen tools is well within the appropriate range for a payment operations server. Each tool covers a meaningful operation across charges, webhooks, networks, metrics, sandbox testing, and environment status, with little apparent redundancy.
The surface covers charge inspection, test charge creation, webhook delivery inspection/retry, network discovery, metrics, and sandbox simulation. However, notable lifecycle gaps remain: webhook endpoints cannot be created/updated/deleted, and escrow release/refund can only be prepared, not executed, creating dead ends for those workflows.