Rinne MCP server

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

• activate_user

  JWT required (org users only). Reactivate a suspended user.

• authenticate_transaction

  Complete 3DS authentication for a transaction that came back AWAITING_3DS (transaction-first flow).

• cancel_refundwrite action

  Cancel a refund that hasn't settled yet.

• cancel_transactionwrite action

  Cancel a pending transaction (e.g. an unpaid BOLEPIX charge before its due date).

• create_3ds_sessionwrite action

  Create a 3D Secure authentication session for a card, ahead of (or alongside) creating a transaction. Returns an id to pass as `three_d_secure_session_id` to create_transaction / authenticate_transaction.

• create_affiliationwrite action

  Create a merchant account with a payment provider (e.g. RINNE, CAPPTA, CELCOIN), enabling transaction processing for the given payment methods and capture channels. Starts in PENDING_APPROVAL.

• create_api_keywrite action

  JWT required (RINNE_EMAIL/RINNE_PASSWORD) — API keys can't create other API keys. The full key is returned once only; store it immediately.

• create_bank_accountwrite action

  Register an external bank account (payout destination).

• create_cashoutwrite action

  Create a cashout (payout) to a bank account or PIX key. Provide exactly one of destination_bank_account_id or destination_pix_key_id.

• create_fee_policywrite action

  Create a fee policy — pricing rules applied to merchants.

• create_internal_transferwrite action

  Transfer funds between two of your organization's own bank accounts.

• create_merchantwrite action

  Create a new merchant under your organization. Requires KYC data. Financial fields may be required by specific affiliation providers later.

• create_pix_collection_keywrite action

  Create a PIX key the merchant uses to RECEIVE payments, tied to a provider affiliation. Different resource from register_cashout_pix_key (which registers a key as a payout destination).

• create_rolewrite action

  JWT required. Create a custom role.

• create_transactionwrite action

  Create a transaction — card (raw, stored, or Apple Pay/Google Pay) or PIX. For card, either: (1) "session-first" — call create_3ds_session first and pass its id as three_d_secure_session_id; or (2) "transaction-first" — pass require_3ds: true and the transaction comes back AWAITING_3DS, then call authenticate_transaction. For PIX, set payment_method: "PIX" and fill pix_data + consumer; the transac

• create_userwrite action

  Create a user. With merchant_id, uses the merchant's x-api-key scope; without it, creates an org user and requires JWT (RINNE_EMAIL/RINNE_PASSWORD).

• delete_cardwrite action

  Delete a stored card.

• get_affiliation

  Get a specific affiliation for a merchant.

• get_balance

  Get the current balance.

• get_card

  Get a stored card by ID.

• get_cashout

  Get a single cashout by ID.

• get_cashout_receipt

  Get a cashout's receipt.

• get_company

  Get the authenticated company (organization or merchant, depending on the API key's scope).

• get_current_session

  JWT required. Get the current JWT session's identity/company context — a whoami for the JWT scope, distinct from get_company (x-api-key scope).

• get_health

  Check Rinne API health status.

• get_ledger_entry

  Get a single ledger entry by ID.

• get_merchant

  Get merchant details by ID.

• get_sandbox_guide

  Return Rinne sandbox rules: the card-encryption requirement, test card numbers, the amount-based approve/decline rule, and which tools need a JWT session.

• get_statement

  Get a merchant's balance statement (movements) for a date range.

• get_transaction

  Get transaction details and current status by ID, including any refunds.

• get_transaction_receipt

  Get a transaction's receipt(s) (returns base64 PDF).

• get_webhook_dashboard_url

  Get the URL of the webhook management dashboard, to configure endpoints and subscribed events (webhooks themselves are configured there, not via this API). Requires the webhook.list permission. Events are Svix-signed; verify with the Svix SDK and your webhook secret.

• list_affiliations

  List affiliations. With merchant_id, scoped to that merchant; without it, lists across all merchants in the organization.

• list_api_keys

  JWT required. List API keys (shows prefix + last 4 only, not the full key).

• list_cards

  List cards on file.

• list_cashouts

  List cashouts.

• list_cost_policies

  List cost policies (what providers charge you).

• list_fee_policies

  List fee policies (what you charge merchants).

• list_judicial_blockages

  List judicial blockages (court-ordered account freezes) affecting balances.

• list_ledger_entries

  List ledger entries for the authenticated company.

• list_mccs

  List Merchant Category Codes (MCCs), for use in create_merchant.

• list_merchants

  List merchants under your organization.

• list_permissions

  JWT required. List all available permissions (read-only, system-defined), optionally filtered by resource.

• list_pix_collection_keys

  List the merchant's PIX collection keys.

• list_roles

  JWT required. List roles.

• list_transactions

  List transactions. With merchant_id, scoped to that merchant; without it, lists across all merchants in the organization.

• list_users

  List users. With merchant_id, uses the merchant's x-api-key scope; without it, lists org users and requires JWT.

• lookup_zipcode

  JWT required — unlike almost every other endpoint in this API, zipcode lookup rejects x-api-key. Look up a Brazilian address by CEP.

• refund_transactionwrite action

  Refund a transaction, fully or partially.

• register_affiliation

  Register a gateway-mode affiliation — bring an existing account/credentials with the provider instead of having Rinne provision a new one.

• register_cashout_pix_key

  Register an external PIX key as a payout (cashout) destination. Different resource from create_pix_collection_key (which registers a key to receive payments).

• replace_fee_policy

  Replace a fee policy in full (PUT).

• revoke_api_key

  JWT required. Revoke an API key.

• simulate_pay_transactionwrite action

  SANDBOX ONLY. Mark a WAITING_PAYMENT transaction (typically PIX) as paid, simulating the payer completing payment.

• store_card

  Save a card on file for reuse in future transactions (via card_id).

• suspend_user

  JWT required (org users only). Suspend a user's access.

• topup_balance

  SANDBOX ONLY. Simulate funding the balance — not a real deposit call.

• update_bank_accountwrite action

  Set a bank account as primary.

• update_companywrite action

  Update the authenticated company. All fields optional.

• update_fee_policywrite action

  Partially update a fee policy (PATCH) — any subset of fields.

• update_merchantwrite action

  Update a merchant. All fields optional besides merchant_id.

• update_userwrite action

  JWT required (org users only). Update a user's name/roles.

• 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 26 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 63% of 48,255 servers

Tools

62

the typical server has 7

Tools that change things

35%

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

GitHub stars

271

more than 95% of 28,688 servers

Downloads a week

11

more than 3% of 12,191 servers with a package

Rinne: common questions

Is Rinne MCP server safe?

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

How do I install Rinne?

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

Does Rinne need an API key?

Yes. The registry entry asks for RINNE_API_KEY, RINNE_PASSWORD.

Is Rinne maintained?

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

How does Rinne compare with other MCP servers?

safety score 82/100 (higher than 63% of 48,255 servers); tools 62 (the typical server has 7); tools that change things 35% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.