ToolsMCP
mcp-kushki
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- codespar (GitHub)
- Prerequisites
- Install @codespar/mcp-kushki from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.0 · updated
- Official links
Publisher’s description
MCP server for Kushki — LATAM PSP: card charges, preauth, PSE/SPEI transfer, cash, subscriptions
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- codespar (GitHub)
- Version observed
- 0.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.codespar%2Fmcp-kushki/versions/0.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Create invoices and handle payments | Publisher description mentions “subscriptions”, “charges”. | No connection check or task run. Capability is as described by the publisher. | Rule payments-invoices matched: “subscriptions”, “charges”. Rule payments-invoices. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@codespar/mcp-kushki(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.codespar/mcp-kushki
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.