Brankas MCP. Manage payouts and financial records automatically.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Brankas handles open finance operations, letting your AI agent manage payments, payouts, and financial data across Southeast Asia. Use this MCP to initiate direct account-to-account checkouts, send inter- or intra-bank disbursements, and pull real-time bank statements and identity records.
What your AI agents can do
Create checkout
Starts a new session to accept immediate payments directly into your account.
Get balance
Retrieves the current linked balance for an account.
Get identities
Pulls verified identity information from connected users.
You trigger checkout sessions that allow you to accept instant account-to-account payments and track the money flow.
The agent initiates transfers, sending funds out through either an inter-bank or intra-bank network while monitoring the transfer status.
You ask for and receive the real-time balance linked to a specific bank account.
The MCP provides status updates on completed payments or ongoing transactions.
You pull comprehensive transaction history and balance data from the connected bank account statements.
The agent retrieves linked identity data, ensuring compliance and verification before any funds move.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Brankas: 8 Payment & Finance Tools
Use these eight specialized tools to manage every aspect of payments, from initiating checkouts to retrieving detailed account statements.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Brankas on Vinkius019d7562create checkout
Starts a new session to accept immediate payments directly into your account.
019d7562get balance
Retrieves the current linked balance for an account.
019d7562get identities
Pulls verified identity information from connected users.
019d7562get statement
Fetches detailed, real-time transaction history and statement data.
019d7562get transaction
Checks the status of a payment that was recently initiated.
019d7562get transfer status
Provides current status details for an ongoing disbursement transfer.
019d7562inter bank transfer
Initiates a payout through the broader inter-bank payment network.
019d7562intra bank transfer
Sends funds directly between accounts within the same bank or system.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Brankas, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Brankas. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Tracking payments feels like managing dozens of dashboards.
Right now, if a client asks you about a payment, your workflow means checking the internal ledger, then logging into the bank's website to see the transfer status, and finally pulling up the statement PDF just to confirm it hit the right account. It’s a process of copy-pasting data across three or four different tabs.
With this MCP, you ask your agent about the payment once. Your client handles the sequence: calling `get_transaction` for status, and if needed, using `inter_bank_transfer` to initiate the fix. You get a single, clean, real-time answer without ever leaving your chat window.
The Brankas MCP gives you full control over money movement.
You eliminate manual reconciliation steps. Instead of waiting for end-of-day reports, the agent pulls raw transaction data using `get_statement` instantly. You can also verify who you're paying with a call to `get_identities`, making compliance checks immediate.
What changes now is that money movement isn't a series of manual forms and logins; it’s an executable, conversational command.
What you can do with this MCP connector
Connect Brankas's Open Finance capabilities to your AI agent to manage every step of your money workflow in Southeast Asia. You can accept instant payments by creating checkout sessions that track transaction status immediately. Need to pay out a client? The MCP handles sending disbursements, whether it's through an inter-bank or intra-bank transfer, and you get real-time tracking on their progress.
Beyond transactions, you pull the data needed for compliance and operations; your agent can grab current bank account balances, retrieve full transaction histories from linked statements, and access identity data from consented users. This makes handling complex financial processes feel like a natural conversation. Once connected via Vinkius, your AI client manages everything from payment initiation to final reconciliation.
019d7562-a02f-737e-b831-d288ee122d3c 
How Brankas MCP Works
- 1 First, subscribe to the MCP and enter your Brankas API key, specifying whether you're running in sandbox or production mode.
- 2 Next, instruct your AI agent to perform a specific action, like checking balances or initiating a disbursement. The agent uses the appropriate tool call within the system.
- 3 Finally, the MCP executes the request against Brankas and returns the status, balance data, or confirmation ID back to your agent for follow-up.
The bottom line is you connect your API credentials once, and then your AI client handles all the complex payment logic via natural conversation.
Who Is Brankas MCP For?
Operations managers who spend too much time jumping between banking portals to verify payouts or reconciling accounts. It's for anyone whose job depends on moving money and proving it, without needing to manually click through half a dozen dashboards.
They use this MCP to automate payout runs, ensuring every disbursement has proper status tracking (using inter_bank_transfer or intra_bank_transfer).
They rely on the ability to pull historical data and current balances using get_statement and get_balance for monthly reporting.
They need reliable checks on user identities (get_identities) before any payment, ensuring all transactions meet KYC requirements.
What Changes When You Connect
- Accept payments instantly. Use
create_checkoutto generate a secure session, giving you immediate visibility into incoming funds and transaction status viaget_transaction. - Handle complex disbursements reliably. You can automate money-out processes using either
inter_bank_transferorintra_bank_transfer, then track the progress withget_transfer_status. - Get a complete financial picture. Pull all necessary data points, including balances (
get_balance), transaction statements (get_statement), and identity proofs (get_identities). - Simplify reconciliation. Instead of manually downloading bank statements, your agent uses
get_statementto pull structured history directly into the workflow. - Minimize manual steps. Your AI client combines multiple calls—for example, checking a balance with
get_balance, then initiating a payment usinginter_bank_transfer—in one continuous conversation.
Real-World Use Cases
Processing daily payouts to vendors
A payroll manager needs to pay 50 contractors. Instead of logging into the bank portal five times, they ask their agent to run a batch payout. The agent uses inter_bank_transfer for each payment and then confirms completion using get_transfer_status, providing an instant audit trail.
Onboarding a new merchant
A sales rep needs to verify a client's financial standing. They ask the agent to check two things: first, their linked identity using get_identities, and second, their current available funds using get_balance before signing off on a contract.
Investigating failed payments
A customer reports money was supposed to arrive but didn't. The agent uses the transaction ID in conjunction with get_transaction and get_statement. This allows them to pinpoint exactly where the funds stalled.
Reconciling month-end books
A finance clerk needs a full picture of activity. They instruct their agent to retrieve all transactions for the last 30 days using get_statement, providing raw data perfect for ledger entry.
The Tradeoffs
Treating transfers as simple messages
Asking the AI agent to just 'send $100' without specifying if it needs an inter-bank or intra-bank transfer. The payment fails because the system doesn't know the required rail.
→
Always specify the nature of the payout. Use inter_bank_transfer for payouts outside your immediate bank network, or use intra_bank_transfer when moving money within a known local account group.
Checking balances without history
Only asking to see the current balance using get_balance. This tells you nothing about why the balance is what it is, leaving you blind to recent large transactions.
→
Pair a balance check with data retrieval. After calling get_balance, always follow up by requesting statements via get_statement to see the underlying transaction flow.
Over-relying on one API key
Assuming that just because you can pull balance information, you also have permission to initiate transfers. This is a security mistake and will result in an authorization error.
→
Treat the tools separately. Use get_balance for reading data only. To move funds, you must use dedicated payout tools like inter_bank_transfer, which require different permissions.
When It Fits, When It Doesn't
Use this MCP if your core business process involves moving money or proving the source/destination of funds in Southeast Asia. If you need to know 'how much' and 'where', this is it. You must use get_identities when dealing with any new user onboarding or compliance check, period. Don't use this if you only need simple internal messaging—you'll get a specialized financial payload back. Conversely, don't use this MCP if your goal is just to manage inventory records; those tools are for physical assets, not money movement. This system requires a transaction flow: first, verify data (get_identities), then check status (get_balance, get_statement), and finally act (inter_bank_transfer).
Common Questions About Brankas MCP
How do I check the status of a payment using get_transaction? +
You pass the unique transaction ID to get_transaction. It returns whether the direct payment was successful or if it's currently pending. You can use this information to guide the user through next steps.
Can I only pay within my own bank using intra_bank_transfer? +
Yes, intra_bank_transfer is specifically designed for moving funds between accounts that are linked or contained within the same banking system. Use this when you know the destination account shares a primary network.
What data does get_statement provide? +
get_statement pulls comprehensive, structured transaction history from the connected bank statement. This gives you far more detail than just checking the current balance using get_balance.
If I need to verify a client's identity first, which tool should I use? +
You must run get_identities before proceeding with any payments. This ensures that your agent has access to the necessary verified data points required for compliance.
What is the difference between using `inter_bank_transfer` and `intra_bank_transfer`? +
The core difference is the network they use. Use inter_bank_transfer when paying across different banks, as it handles those wider payouts. Stick to intra_bank_transfer for transfers staying within the same bank or institution.
How do I start an account-to-account payment process with `create_checkout`? +
You first call create_checkout to generate a unique session link and required parameters. This initiates the secure payment flow, allowing you to collect instant funds from the payer.
If a payout fails, how do I diagnose the issue using `get_transfer_status`? +
The get_transfer_status tool provides the current status and often includes an error code or specific failure reason. This lets you know exactly why the disbursement didn't complete.
What steps are needed to retrieve my initial account data using `get_balance`? +
You must ensure your AI client has proper permissions to the linked bank accounts before calling get_balance. This tool reads the current, real-time balance for all connected financial sources.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.