Khipu MCP server

Read from the package source without running it. The installed server may list more.

• confirm_payment

  Manually confirm a Khipu payment. Use when the merchant has opted into manual confirmation and the backend has validated the underlying transfer.

• create_automatic_paymentwrite action

  Create a Khipu automatic payment (recurring / subscription charge against a previously enrolled subscription_id). The payer must have completed the subscription enrollment at their bank first.

• create_paymentwrite action

  Create a Khipu payment (bank-transfer charge). Returns a payment_id and URLs the payer visits to authorize the transfer from their Chilean bank account. Use simplified_transfer_url for in-app redirects and transfer_url for desktop bank-login flows.

• create_receiverwrite action

  Create (onboard) a new receiver under an integrator account. The receiver can then collect Khipu payments. Only available to integrator-level API keys.

• create_terminal_sessionwrite action

  Create a Khipu terminal session for in-person / POS bank-transfer checkout. Returns a QR/URL the payer scans at the point of sale to pay from their bank app.

• delete_paymentwrite action

  Delete (cancel) a pending Khipu payment. Only works while the payment has not been paid by the payer.

• delete_webhookwrite action

  Delete (unregister) a webhook endpoint by id. Khipu stops sending notifications immediately.

• get_banks

  List Chilean banks supported by Khipu for bank-transfer payments. Agents can use this to render a bank-selection UI or to validate a bank_id before creating a payment.

• get_merchant

  Fetch a single merchant by id. Returns commercial info, configured collect accounts, and current integration status.

• get_merchants

  List the merchant receiver accounts accessible with the current API key. Useful to confirm auth + discover receiver_id values.

• get_payment

  Retrieve a Khipu payment. Pass either payment_id (lookup by id) or notification_token (lookup from a webhook — preferred, since webhooks only contain the token).

• get_terminal_session

  Retrieve the current status of a terminal (POS) session — whether the payer has scanned, paid, or the session has expired.

• list_conciliations

  List settlement / conciliation records for a date range. Each record groups settled payments into a single bank deposit. Use to match Khipu payouts to your accounting.

• list_merchant_accounts

  List the bank accounts registered for a merchant to collect into. Use with refund_payment / conciliation flows to know which account funds settle to.

• list_payments

  List Khipu payments for the current merchant, optionally filtered by date range and status. Useful for reconciliation jobs and agent-driven reporting.

• list_receivers

  List receivers onboarded under the current integrator account.

• list_reviews

  List payer reviews / opinions left after a Khipu payment. Useful for NPS dashboards and detecting UX problems in the payment flow.

• list_webhooks

  List registered webhook endpoints for the current merchant.

• predict_payment

  Predict whether a payment is likely to succeed for a given payer+amount+bank, and recommend the best bank/rail. Call before create_payment to improve conversion for large or edge-case transfers.

• refund_paymentwrite action

  Refund a paid Khipu payment (full or partial). Refunds are only possible for merchants collecting into a Khipu account and before settlement of the corresponding funds (until 01:00 am the next business day).

• register_webhook

  Register a webhook endpoint to receive Khipu notifications (payment.paid, payment.refunded, etc). Returns a webhook id and the shared secret used to verify incoming signatures.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 29 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 73% of 1,761 Finance servers

Tools

21

the typical Finance server has 8

Tools that change things

33%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

271

more than 95% of 946 Finance servers

Khipu: common questions

Is Khipu MCP server safe?

Mostly: it is graded B (82/100). Read the Khipu safety report

How do I install Khipu?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Khipu need an API key?

Yes. The registry entry asks for KHIPU_API_KEY, KHIPU_SECRET.

Is Khipu maintained?

The last commit was 67 days ago (2026-08-29). The latest release is v0.2.0-alpha.3.

What can I use instead of Khipu?

Servers from other publishers that do the same job: T-Bank MCP server, BankMCP™ MCP server and three.ws Agent Payments MCP server.

How does Khipu compare with other Finance MCP servers?

safety score 82/100 (higher than 73% of 1,761 Finance servers); tools 21 (the typical Finance server has 8); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.