is-bankasi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ISBANK_CLIENT_ID | Yes | OAuth client ID from Isbank developer portal | |
| ISBANK_CLIENT_SECRET | Yes | OAuth client secret from Isbank developer portal |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountsC | List bank accounts |
| get_account_balanceA | Get account balance by account ID |
| get_transactionsC | Get account transactions |
| get_exchange_ratesC | Get current exchange rates |
| initiate_transferA | Initiate a money transfer (EFT/FAST/havale) |
| get_transfer_statusA | Get transfer status by ID |
| get_credit_cardsB | List credit cards |
| get_card_transactionsC | Get credit card transactions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource and action: accounts, balances, transactions, exchange rates, transfers, and cards are clearly separated. There is no overlap between getting account transactions versus card transactions, and transfer initiation/status checking are unambiguous.
Seven of eight tools follow the 'get_' verb-noun pattern, making the set highly predictable. 'initiate_transfer' deviates by using an action verb rather than 'get_', which is a minor inconsistency but does not cause confusion.
With 8 tools, the server is well-scoped for a banking API covering accounts, transactions, cards, exchange rates, and transfers. Each tool serves a distinct purpose, and the number feels appropriate without being overwhelming or sparse.
The toolset covers core banking workflows: listing accounts, checking balances, viewing transactions, managing transfers, and accessing card data. Minor gaps exist, such as lacking a dedicated transfer history or card details endpoint, but agents can work around these using existing tools.