What can you do with this server?

The xendit-mcp server integrates with the Xendit payment API to manage invoices, balances, transactions, and disbursements across Southeast Asian markets. * Invoice Management: Create invoices with payment links (IDR, PHP, THB, VND, MYR, USD), list with filters (status, date, currency), retrieve by ID, or expire active invoices. * Balance Inquiry: Check account balance by type (CASH, HOLDING, TAX), optionally filtered by currency. * Transaction History: List payments, disbursements, refunds, fees, and adjustments with filters for type, status, currency, and date range. * Disbursements (requires XENDIT_ENABLE_DISBURSEMENTS=true): Send funds to bank accounts or e-wallets (Indonesia/Philippines); check disbursement status by ID; list supported banks and e-wallets filtered by country/currency and channel type (BANK or EWALLET). * Prompts & Resources: Quick actions for balance checks, recent payments, unpaid invoices, and daily summaries; static access to supported bank codes and API info. * Safety: Disbursement tools are disabled by default; live API keys are refused unless explicitly allowed.

Which integrations are available for this server?

Provides tools for managing Xendit payment APIs, including creating invoices, sending disbursements, checking balances, and tracking transactions across Southeast Asian countries (Indonesia, Philippines, Thailand, Vietnam, Malaysia).

de en es ja ko ru zh

xendit-mcp

by mrslbt

Overview Schema Source Related Servers Score Discussions Admin

JavaScript

Remote

xendit-mcp

npm version npm downloads MCP Badge xendit-mcp MCP server License: MIT

Model Context Protocol server for the Xendit payment API. Supports payment links via invoices, payouts/disbursements, balances, and transactions across Indonesia, the Philippines, Thailand, Vietnam, and Malaysia.

Install

npm install -g xendit-mcp

Or run on demand with npx xendit-mcp.

Related MCP server: rippr

Upgrading from 0.1.x

0.2.0 introduces breaking defaults. If you were on 0.1.x and relied on invoice creation or one-shot payouts working out of the box, those tools are now disabled by default.

To restore the old behavior, set these in your MCP config env:

XENDIT_ENABLE_INVOICE_MUTATIONS=true
XENDIT_ENABLE_DISBURSEMENTS=true
XENDIT_ENABLE_LEGACY_ONE_SHOT_DISBURSEMENT=true

If you enable disbursements, you must also set the four safety gates (XENDIT_MAX_DISBURSEMENT_AMOUNT, XENDIT_MAX_DAILY_AMOUNT, XENDIT_ALLOWED_ACCOUNTS, XENDIT_APPROVAL_CODE) or the server will refuse to start.

The recommended migration is to adopt the new two-step payout flow (prepare_disbursement → confirm_disbursement with an approval code) instead of re-enabling the legacy one-shot. See Safety for details.

User-facing modes

Think about the product in 3 modes:

read-only: balances, invoices read, transactions read
invoices: read-only plus create_invoice and expire_invoice
guarded-payouts: invoices mode plus prepare_disbursement and confirm_disbursement

For non-technical users, the easiest helpers are:

npx xendit-mcp doctor
npx xendit-mcp setup

doctor prints the current mode, enabled capabilities, and what is still blocked.
setup generates a Claude Code or Claude Desktop snippet for the mode you want.

Configuration

Sign up at the Xendit Dashboard.
Go to Settings → API Keys and generate a key.
Use a test key (xnd_development_...) for development or a live key for production.

Variable	Required	Description
`XENDIT_API_KEY`	yes	Test or live API key
`XENDIT_ENABLE_INVOICE_MUTATIONS`	no	Set to `true` to enable `create_invoice`, `expire_invoice`, and the `create_payment_link` prompt. Disabled by default for safer read-only behavior.
`XENDIT_ENABLE_DISBURSEMENTS`	no	Set to `true` to enable disbursement tools (money-movement). Disabled by default.
`XENDIT_ALLOW_LIVE`	no	Set to `true` to allow live/production keys (prefixes `xnd_production_`, `iluma_production_`, `sk_live_`). Refused by default.
`XENDIT_MAX_DISBURSEMENT_AMOUNT`	no	Hard cap for one money-out call. Set to `0` or omit to disable.
`XENDIT_MAX_DAILY_AMOUNT`	no	Rolling 24-hour cap across money-out calls. Set to `0` or omit to disable.
`XENDIT_ALLOWED_ACCOUNTS`	no	Comma-separated allowlist in `CHANNEL_CODE:ACCOUNT_NUMBER` format, e.g. `ID_BCA:1234567890`.
`XENDIT_PREPARE_TTL_SECONDS`	no	How long a prepared disbursement token stays valid. Defaults to `300`, max `86400`.
`XENDIT_APPROVAL_CODE`	no	Required when `XENDIT_ENABLE_DISBURSEMENTS=true`. Human approval code required by `confirm_disbursement` and legacy one-shot payouts. Keep it out of untrusted prompt context.
`XENDIT_ENABLE_LEGACY_ONE_SHOT_DISBURSEMENT`	no	Set to `true` only if you intentionally want the old `create_disbursement` one-shot tool. Disabled by default.

Guided setup

If you do not want to hand-edit env vars, run:

npx xendit-mcp setup

It will ask which client you use and which mode you want, then output a ready-to-paste Claude config snippet with placeholders for secrets.

If the MCP is already connected in Claude, you can also ask Claude to use:

get_workspace_mode
guided_setup

guided_setup uses MCP elicitation in Claude Code when available, so the user sees a form instead of raw config details.

Claude Desktop

Edit claude_desktop_config.json:

{
  "mcpServers": {
    "xendit": {
      "command": "npx",
      "args": ["-y", "xendit-mcp"],
      "env": {
        "XENDIT_API_KEY": "your-api-key"
      }
    }
  }
}

Claude Code

claude mcp add xendit --env XENDIT_API_KEY=your-api-key -- npx -y xendit-mcp

Cursor

Add to ~/.cursor/mcp.json with the same shape as Claude Desktop.

Tools

Tool	Description
`get_workspace_mode`	Explain which Xendit mode is active, what is enabled, and the safest next step to unlock more features.
`guided_setup`	Generate a Claude Code or Claude Desktop config snippet for `read-only`, `invoices`, or `guarded-payouts`.
`get_balance`	Account balance by type (CASH, HOLDING, TAX).
`list_invoices`	List invoices filtered by status, date range, or currency.
`get_invoice`	Retrieve a single invoice.
`create_invoice`	Create a payment invoice and return a payment link. Disabled unless `XENDIT_ENABLE_INVOICE_MUTATIONS=true`.
`expire_invoice`	Expire an active invoice. Disabled unless `XENDIT_ENABLE_INVOICE_MUTATIONS=true`.
`list_transactions`	List payments, payouts, refunds, transfers, and balance adjustments.
`prepare_disbursement`	Stage a money-out call and return a short-lived confirmation token. Disabled unless `XENDIT_ENABLE_DISBURSEMENTS=true`.
`confirm_disbursement`	Execute a previously prepared money-out token. Requires `approvalCode`. Disabled unless `XENDIT_ENABLE_DISBURSEMENTS=true`.
`cancel_disbursement`	Cancel a prepared money-out token. Disabled unless `XENDIT_ENABLE_DISBURSEMENTS=true`.
`create_disbursement`	Legacy one-shot payout/disbursement. Requires `approvalCode` and explicit legacy opt-in. Disabled unless both `XENDIT_ENABLE_DISBURSEMENTS=true` and `XENDIT_ENABLE_LEGACY_ONE_SHOT_DISBURSEMENT=true`.
`get_disbursement`	Check payout/disbursement status. Disabled unless `XENDIT_ENABLE_DISBURSEMENTS=true`.
`list_disbursement_banks`	List payout channels such as `ID_BCA` and `PH_BPI`. Disabled unless `XENDIT_ENABLE_DISBURSEMENTS=true`.

Prompts

Prompt	Description
`check_balance`	Report account balance.
`recent_payments`	Payments received in the last N days.
`create_payment_link`	Generate a payment link for a customer. Disabled unless `XENDIT_ENABLE_INVOICE_MUTATIONS=true`.
`unpaid_invoices`	List pending invoices.
`daily_summary`	Today's payment activity.

Resources

Resource	URI	Description
Supported Banks	`xendit://banks`	Common payout channel aliases for Indonesia and the Philippines.
Setup Guide	`xendit://setup`	Current mode, setup commands, and plain-English mode explanations.
API Info	`xendit://info`	Xendit API overview and doc links.

Example queries

What's my current Xendit balance?
Saldo Xendit saya berapa?

With `XENDIT_ENABLE_INVOICE_MUTATIONS=true`:
Create an invoice for Rp 500,000 for "Website design deposit".
Buatkan invoice Rp 500.000 untuk "Deposit desain website".

Show me all unpaid invoices.
Tampilkan semua invoice yang belum dibayar.

With XENDIT_ENABLE_DISBURSEMENTS=true:

Prepare a Rp 1,000,000 payout to Ahmad at BCA, then wait for my confirmation.
Siapkan payout Rp 1.000.000 ke Ahmad di BCA, lalu tunggu konfirmasi saya.

List available payout channels in the Philippines.

Environments

Xendit issues separate test and live API keys. Test keys operate against the Xendit sandbox, so no real funds move. Live keys (xnd_production_..., iluma_production_..., sk_live_...) operate against production.

Safety

This server can move real money through the Xendit API. Key safeguards:

Read-only by default. Invoice write tools are disabled unless XENDIT_ENABLE_INVOICE_MUTATIONS=true. Money-moving tools are disabled unless XENDIT_ENABLE_DISBURSEMENTS=true.
Live keys are refused by default. Keys with the prefixes xnd_production_, iluma_production_, or sk_live_ are rejected at startup unless XENDIT_ALLOW_LIVE=true. Always test with a development key (xnd_development_...) first.
Fail-closed money movement. If you enable disbursements, the server refuses to start unless XENDIT_MAX_DISBURSEMENT_AMOUNT, XENDIT_MAX_DAILY_AMOUNT, XENDIT_ALLOWED_ACCOUNTS, and XENDIT_APPROVAL_CODE are configured.
Human-in-the-loop flow. confirm_disbursement requires both the staged token and a separate approvalCode.
Legacy one-shot payouts stay off by default. create_disbursement is not even registered unless XENDIT_ENABLE_LEGACY_ONE_SHOT_DISBURSEMENT=true.
Hard caps and allowlists. XENDIT_MAX_DISBURSEMENT_AMOUNT, XENDIT_MAX_DAILY_AMOUNT, and XENDIT_ALLOWED_ACCOUNTS let you fail closed before a payout is sent.
Idempotency. Payout calls use your externalId as the Idempotency-Key, so safe retries do not create duplicate transfers.
Setup helpers are always available. get_workspace_mode and guided_setup are exposed even in read-only mode so users can understand what is blocked and how to enable the next mode safely.
Important limitation. No MCP server can be fully immune to prompt injection if you expose sensitive read or write tools to an untrusted model context. These defaults reduce risk, but you should still only connect this server to trusted agent workflows.

Even with these gates on, review any money-moving request before approving the tool call. Treat tool inputs derived from model output as untrusted.

Payout lifecycle

A confirmed payout does not always succeed or fail immediately. Xendit returns one of these statuses, and the terminal state may arrive seconds or minutes later:

ACCEPTED — accepted by Xendit, channel processing in progress
REQUESTED — submitted to the destination channel, waiting for the channel's response
SUCCEEDED — funds delivered
FAILED — final failure (e.g. INVALID_DESTINATION, REJECTED_BY_CHANNEL, INSUFFICIENT_BALANCE)

Some destinations (observed in PHP sandbox testing) sit in REQUESTED for a while before transitioning to FAILED. Always re-fetch with get_disbursement before assuming the final state. Do not treat the initial response from confirm_disbursement as proof of delivery.

Sandbox verification scope

0.2.0 was verified against the Xendit sandbox using IDR and PHP development keys (May 25, 2026). Verified flows:

Invoice create / get / list / expire (IDR + PHP)
Payout channel discovery (PHP)
Guarded payout prepare → confirm → get (IDR + PHP)
Negative payout reasons INVALID_DESTINATION and REJECTED_BY_CHANNEL (PHP only — the IDR sandbox key had balance: 0, so negative IDR cases surfaced as INSUFFICIENT_BALANCE rather than destination-specific failures)

Thailand, Vietnam, and Malaysia behavior is not yet verified against real sandbox keys. Behavior should be similar but cannot be claimed as tested.

Optional Claude Code hardening

Claude Code supports PreToolUse hooks that can force an extra approval dialog for sensitive tools such as confirm_disbursement. That gives you a second control outside the model context.

Example .claude/settings.json snippet:

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "mcp__xendit__confirm_disbursement",
        "hooks": [
          {
            "type": "command",
            "command": "printf '%s' '{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"permissionDecision\":\"ask\",\"permissionDecisionReason\":\"Human review required before confirm_disbursement.\"}}'"
          }
        ]
      }
    ]
  }
}

Disclaimer

This is an unofficial, community-built MCP server. Not affiliated with, endorsed by, or sponsored by Xendit. Xendit is a trademark of its respective owners. Use at your own risk. The author accepts no liability for funds lost through misuse, prompt injection, or bugs.

License

MIT

Available Tools

6 tools

get_balanceA

Read-only

Get your Xendit account balance. Returns available balance by account type (CASH, HOLDING, TAX).

ParametersJSON Schema

Name	Required	Description	Default
`currency`	No	Currency code (e.g., IDR, PHP). Defaults to your account's primary currency.
`accountType`	No	Account type to check	CASH

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true, and the description adds that the tool returns available balance by account type, which is consistent and adds value beyond annotations. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences, front-loaded with the purpose, with no extraneous information. Every word is justified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple read tool with full schema and annotations. However, the lack of output schema means the description could add return format details, but it is sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description does not add new parameter-level details beyond what the schema already provides (e.g., default currency, account type enum).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states verb 'Get' and resource 'Xendit account balance', and specifies return by account types (CASH, HOLDING, TAX). This distinguishes it from sibling tools like get_invoice or list_transactions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use versus alternatives or when not to use. The purpose is clear, but the description lacks explicit context for selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_invoiceA

Read-only

Get details of a specific Xendit invoice by ID.

ParametersJSON Schema

Name	Required	Description	Default
`invoiceId`	Yes	Xendit invoice ID

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true. Description adds minimal behavioral context beyond stating it returns 'details'. No mention of error behavior or what details include.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with key information, no redundant words. Efficient and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple get-by-id operation with one required parameter and readOnlyHint, the description is complete. No output schema is expected, and sibling tools don't require additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description for invoiceId is clear ('Xendit invoice ID'). Description does not add further semantics beyond the schema. With 100% schema coverage, baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Get details of a specific Xendit invoice by ID' with a specific verb and resource. It distinguishes from siblings like list_invoices which lists multiple invoices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternatives are mentioned. Usage is implied for retrieving a single invoice by ID, but no guidance is given for scenarios like missing invoice or comparison with list_invoices.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_workspace_modeWorkspace ModeA

Read-only

Explain the current Xendit MCP mode, what actions are enabled, and the safest next step to enable more access.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds significant behavioral context beyond the readOnlyHint annotation: it discloses that the tool explains the mode, actions enabled, and a recommended next step. This aligns with the annotation and provides useful transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that clearly states the tool's purpose and outputs. Every part is necessary and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters, is read-only, and no output schema, the description sufficiently covers what the tool does and what it returns. No additional context is needed for correct usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the description does not need to add parameter details. The baseline for 0 params is 4, and the description fulfills it by explaining what the tool does without needing parameter input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool explains the current Xendit MCP mode, actions enabled, and next step for more access. This is a specific verb+resource that distinguishes it from sibling tools like get_balance or get_invoice which deal with different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies the usage context: when you need to understand the current mode and possible next steps. However, it does not explicitly state when not to use or mention alternatives, though given the unique purpose, this is a minor gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

guided_setupGuided SetupA

Read-only

Generate a safe Claude Code or Claude Desktop setup snippet for read-only, invoices, or guarded payouts mode. Uses a form when the client supports MCP elicitation.

ParametersJSON Schema

Name	Required	Description
`mode`	No	Desired user-facing mode
`client`	No	Target client
`allowLive`	No	Set true only if you intend to use a live Xendit key
`serverName`	No	Claude MCP server name, defaults to xendit
`maxDailyAmount`	No	Only used for guarded-payouts mode
`allowedAccounts`	No	Comma-separated CHANNEL_CODE:ACCOUNT_NUMBER entries for guarded-payouts mode
`maxDisbursementAmount`	No	Only used for guarded-payouts mode

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=true, so the agent knows this is a safe read operation. Description adds that the snippet is 'safe' and mentions form elicitation, but doesn't add substantive behavioral traits beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences that front-load the purpose. No redundant information; every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters (0 required), two enums, and no output schema, the description covers the core functionality. Could mention output format or more about allowLive context, but siblings are all queries so the role is clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (all parameters documented in schema). Description does not add additional meaning beyond schema, so baseline is 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it generates a safe setup snippet for three specific modes (read-only, invoices, guarded-payouts). Distinct from sibling tools which are all retrieval/query tools, so no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context about generating snippets and using forms when client supports MCP elicitation, but does not explicitly state when to use this tool versus alternatives or mention when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_invoicesA

Read-only

List invoices from your Xendit account with optional filters for status, date range, and pagination.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Number of invoices to return (1-100)
`status`	No	Filter by invoice status
`currency`	No	Filter by currency (IDR, PHP, etc.)
`createdAfter`	No	Return invoices created after this ISO 8601 timestamp. Must be used with createdBefore.
`createdBefore`	No	Return invoices created before this ISO 8601 timestamp. Must be used with createdAfter.

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, and description confirms read-only listing. Adds filter context but does not explain pagination mechanics or result set behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, 16 words, no redundant information. Front-loaded with verb and resource.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers basic listing and filters. Missing details on pagination and return format, but for a simple tool with no output schema, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 5 parameters. Description groups filters but adds no extra meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it lists invoices from Xendit account with optional filters, distinguishing it from sibling get_invoice (single invoice) and list_transactions (different resource).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Lacks explicit guidance on when to use this tool versus alternatives like get_invoice or list_transactions. No exclusions or when-not-to-use context provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_transactionsA

Read-only

List transactions from your Xendit account. Includes payments received, payouts, refunds, transfers, and balance adjustments.

ParametersJSON Schema

Name	Required	Description
`limit`	No	Number of transactions (1-50)
`types`	No	Filter by transaction type
`status`	No	Filter by transaction status
`currency`	No	Filter by currency
`createdGte`	No	Created on or after (ISO 8601)
`createdLte`	No	Created on or before (ISO 8601)

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate read-only, which aligns with the description. However, the description adds no further behavioral details such as pagination, rate limits, or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that is front-loaded with the main action and includes essential details without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the purpose but does not describe the return format or any output schema, leaving the agent uncertain about the response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds no additional meaning beyond the schema. The description lists transaction types, but they are already in the enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List transactions' with the resource and includes a comprehensive list of transaction types, distinguishing it from siblings like get_balance and get_invoice.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While the description implies usage for listing multiple transactions, it lacks explicit guidance on when to use this tool versus alternatives like get_invoice for specific transactions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

9 tool updatesv0.2.0May 25, 2026

Removedcreate_disbursement
Removedcreate_invoice
Removedexpire_invoice
Removedget_disbursement
Addedget_workspace_mode
Addedguided_setup
Removedlist_disbursement_banks

Changedlist_invoices2 fields changed

changedInput schema / properties / createdAfter / description

Previous value: -"Return invoices created after this date (ISO 8601, e.g., 2025-01-01T00:00:00Z)"New value: +"Return invoices created after this ISO 8601 timestamp. Must be used with createdBefore."

changedInput schema / properties / createdBefore / description

Previous value: -"Return invoices created before this date (ISO 8601)"New value: +"Return invoices created before this ISO 8601 timestamp. Must be used with createdAfter."

Changedlist_transactions3 fields changed

changedInput schema / properties / status / description

Previous value: -"Filter by status"New value: +"Filter by transaction status"

changedInput schema / properties / status / enum

Previous value: -[
-  "SUCCESS",
-  "PENDING",
-  "FAILED",
-  "VOIDED"
-]New value: +[
+  "PENDING",
+  "SUCCESS",
+  "FAILED",
+  "VOIDED",
+  "REVERSED"
+]

changedInput schema / properties / types / enum

Previous value: -[
-  "PAYMENT",
-  "DISBURSEMENT",
-  "REFUND",
-  "FEE",
-  "ADJUSTMENT"
-]New value: +[
+  "ADJUSTMENT_ADD",
+  "ADJUSTMENT_DEDUCT",
+  "BNPL_PARTNER_SETTLEMENT_CREDIT",
+  "BNPL_PARTNER_SETTLEMENT_DEBIT",
+  "CASHBACK_FEE",
+  "CASHBACK_VAT",
+  "CHARGEBACK",
+  "CONVERSION",
+  "DISBURSEMENT",
+  "FOREX_DEDUCTION",
+  "FOREX_DEPOSIT",
+  "IN_PERSON_PAYMENT",
+  "LOAN_REPAYMENT",
+  "OTHER",
+  "PAYMENT",
+  "REFUND",
+  "REMITTANCE",
+  "REMITTANCE_COLLECTION_PAYMENT",
+  "REMITTANCE_PAYOUT",
+  "RESERVES_HOLD",
+  "RESERVES_RELEASE",
+  "TOPUP",
+  "TRANSFER_IN",
+  "TRANSFER_OUT",
+  "WITHDRAWAL"
+]

9 tool updatesv1.0.0Apr 14, 2026
- First observedcreate_disbursement
- First observedcreate_invoice
- First observedexpire_invoice
- First observedget_balance
- First observedget_disbursement
- First observedget_invoice
- First observedlist_disbursement_banks
- First observedlist_invoices
- First observedlist_transactions

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored 2026-06-04 04:10 across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: balance retrieval, invoice details, workspace mode explanation, setup snippet generation, and listing of invoices and transactions. No overlap between tools.

Naming Consistency4/5

Most tools follow a verb_noun pattern using snake_case (e.g., get_balance, list_invoices). The only minor deviation is 'guided_setup' which is adjective_noun, but it remains clear and consistent with the overall style.

Tool Count5/5

Six tools is well-scoped for a payment service MCP server covering essential read operations, account balance, and setup guidance. It's neither too few nor too many.

Completeness2/5

The tool surface is limited to read and setup operations, missing write capabilities like create/update/delete invoices or payouts. This creates notable gaps for a payment API, restricting agents to passive data retrieval.

Maintenance

ActivityStale

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

modern-treasury A
io.usefulapi
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Finance Payments & Billing
172
codat A
io.usefulapi
MCP server for Codat — companies, connections, invoices, bills and financial statements.
Finance ERP Systems Data Platforms
282
quaderno A
io.usefulapi
MCP server for Quaderno — tax-rate calculation, invoices, contacts, products, receipts & expenses.
Finance Payments & Billing
232
inflowOAuth
ai.inflowpay.app
MCP Server for agents to onboard, pay, and provision services autonomously with InFlow
Agent Orchestration Autonomous Agents Payments & Billing
26

Related MCP Servers

Velo Payments API MCP Server
Finance Developer Tools
ag2-mcp-servers
F
license
Not graded
quality
D
maintenance
An MCP server that enables interaction with Velo Payments APIs for global payment operations, automatically generated using AG2's MCP builder from the Velo Payments OpenAPI specification.
Updated a year ago (2025-07-16 14:36 UTC)
-
rippr
RAG Systems Web Scraping
mrslbt
A
license
A
quality
B
maintenance
Extract YouTube transcripts for AI agents, RAG pipelines, and LLM workflows. Supports any YouTube URL. Returns clean text or timestamped segments. No API keys required.
Updated a month ago (2026-07-31 02:31 UTC)
1
4
MIT
rakuten-mcp
E-commerce & Retail Travel & Transportation Search
mrslbt
A
license
A
quality
A
maintenance
MCP server for Rakuten APIs. Search products, books, hotels, and rankings across Japan's largest e-commerce platform.
Updated 2 months ago (2026-07-16 04:29 UTC)
28
90
5
MIT
paper-invoice-mcp
Finance Payments & Billing
igun997
F
license
Not graded
quality
D
maintenance
MCP server for Paper.id Indonesian invoicing and accounting platform, providing 31 tools for partner and invoice management, QRIS payments, and reporting with automatic token refresh.
Updated 4 months ago (2026-05-14 17:57 UTC)
-