TurkishBankMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_FILE | No | Path to the cache file. Use 'off' to disable disk cache. Defaults to '.data/cache.json'. | .data/cache.json |
| BANK_PROVIDER | No | The bank provider. Defaults to 'mock' for local testing. Set to 'ohvps' for production access. | mock |
| OHVPS_BASE_URL | No | The base URL of the ÖHVPS provider endpoint. Required when BANK_PROVIDER=ohvps. | |
| OHVPS_GROUP_ID | No | Optional group ID for ÖHVPS requests. | |
| OHVPS_TPP_CODE | No | The TPP (third-party provider) code. Required when BANK_PROVIDER=ohvps. | |
| HTTP_TIMEOUT_MS | No | HTTP timeout in milliseconds. Defaults to 12000. | 12000 |
| HTTP_MAX_RETRIES | No | Maximum number of HTTP retries. Defaults to 2. | 2 |
| OHVPS_ASPSP_CODE | No | The ASPSP (account servicing payment service provider) code. Required when BANK_PROVIDER=ohvps. | |
| HTTP_RETRY_BASE_MS | No | Base retry delay in milliseconds. Defaults to 500. | 500 |
| OHVPS_ACCESS_TOKEN | No | The access token for authentication. Alternative to OHVPS_ACCESS_TOKEN_FILE. | |
| OHVPS_SPEC_VERSION | No | The ÖHVPS specification version. Defaults to '2.0.0'. | 2.0.0 |
| OHVPS_GATEWAY_TOKEN | No | The gateway token for authentication. Alternative to OHVPS_GATEWAY_TOKEN_FILE. | |
| OHVPS_PSU_FRAUD_CHECK | No | Optional PSU fraud check value. | |
| HTTP_MAX_RETRY_WAIT_MS | No | Maximum retry wait time in milliseconds. Defaults to 5000. | 5000 |
| OHVPS_ACCESS_TOKEN_FILE | No | Path to a file containing the access token. Alternative to OHVPS_ACCESS_TOKEN. | |
| OHVPS_GATEWAY_TOKEN_FILE | No | Path to a file containing the gateway token. Alternative to OHVPS_GATEWAY_TOKEN. | |
| OHVPS_PSU_FRAUD_CHECK_FILE | No | Path to a file containing the PSU fraud check data. |
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 |
|---|---|
| bank_provider_statusA | Show Garanti API Store configuration status without exposing credentials. |
| bank_test_connectionA | Test Garanti OAuth client_credentials authentication. The access token is never returned. |
| bank_list_accountsD | Call Garanti Account Information and return its read-only response. |
| bank_get_balancesC | Read account information from Garanti. This uses the same Account Information product because the public portal does not document a separate balance API. |
| bank_list_transactionsB | Call Garanti Account Transactions for an account and date range. No payment or transfer endpoint is available to this MCP. |
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 5 tools
bank_list_accounts and bank_get_balances overlap significantly since both read account information, with bank_get_balances explicitly noting it uses the same Account Information product. bank_provider_status and bank_test_connection are both connectivity-related but distinguishable as status vs. authentication test. Other tools are distinct.
All tools share the bank_ prefix and most follow a verb_noun pattern (test_connection, list_accounts, get_balances, list_transactions). However, bank_provider_status uses a noun_noun construction, which is a minor deviation from the otherwise consistent pattern.
Five tools is well-scoped for a read-only banking data server. Each tool serves a clear functional area (status, auth test, accounts, balances, transactions), and no tool feels superfluous.
The server covers the core read-only operations for banking data: accounts, balances, and transactions, plus connection testing. It lacks payment/transfer functionality, but the description explicitly states these are unavailable in the underlying API, so the surface is appropriate for the stated purpose with minor gaps.