In-depth architectural comparison of the Xendit MCP and Ozon Seller MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Xendit MCP
Finance & Fintech · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Ozon Seller MCP Server
Finance & Fintech · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Xendit MCP if you need specialized Finance & Fintech tools running via a local process. Choose Ozon Seller MCP Server if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Xendit MCP when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
Xendit payment gateway for Southeast Asia. Invoices, disbursements, balance checks, and bank transfers across Indonesia, Philippines, Thailand, Vietnam, and Malaysia. Install via npx xendit-mcp.
MCP server for Ozon Seller API. 26 tools: products, prices, orders, analytics, finance, rating.
Xendit MCP is categorized under Finance & Fintech and uses a local stdio subprocess. In contrast, Ozon Seller MCP Server belongs to Finance & Fintech using local stdio subprocess. Select Xendit MCP when you need capabilities focused on finance & fintech and Ozon Seller MCP Server when you require tools for finance & fintech.
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`.