Investec OpenAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INVESTEC_API_KEY | No | Your Investec API key. | |
| INVESTEC_CLIENT_ID | No | Your Investec Developer client ID. | |
| INVESTEC_ENVIRONMENT | No | Environment: 'production' for live data, 'sandbox' for mock accounts. | sandbox |
| INVESTEC_CLIENT_SECRET | No | Your Investec Developer client secret. | |
| INVESTEC_INTERMEDIARY_ID | No | Optional: Required for Advisor or Intermediary API scopes. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| investec_pb_list_accountsA | List all Private Banking (PB) accounts linked to the user profile, including account balances and details. |
| investec_pb_get_account_balanceC | Retrieve detailed balance information for a specific Private Banking account. |
| investec_pb_get_account_transactionsB | Retrieve transaction history for a specific Private Banking account. Supports date filtering and including pending transactions. |
| investec_pb_get_pending_transactionsB | Retrieve pending/unposted transactions for a specific Private Banking account. |
| investec_pb_list_profilesA | List all Investec Online Banking profiles linked to the user. |
| investec_pb_list_profile_accountsA | List all bank accounts associated with a specific Online Banking profile. |
| investec_pb_get_authorisation_setup_detailsA | Get authorization setup details for a profile and account (critical for understanding who needs to approve a batch payment). |
| investec_pb_list_beneficiariesA | List all global beneficiaries defined on the user's online banking profile. |
| investec_pb_list_beneficiary_categoriesB | List categories used to organize beneficiaries. |
| investec_pb_list_profile_account_beneficiariesB | List beneficiaries linked to a specific account under a profile. |
| investec_pb_pay_multipleA | Initiate batch payments to one or more beneficiaries. Note: Beneficiaries must be pre-registered and paid at least once via online banking. |
| investec_pb_transfer_multipleA | Initiate transfers between own accounts (inter-account transfers). |
| investec_pb_get_documentsA | List available PDF documents (such as statements and tax certificates) for an account. Supports optional fromDate and toDate filters. |
| investec_pb_get_documentB | Retrieve a specific document or statement file (returns metadata and document link). |
| investec_card_list_cardsA | List all debit and credit cards on the account, including card status, programmable features, and details. |
| investec_card_create_virtual_cardB | Create a virtual card for a specific account number. |
| investec_card_get_cardB | Retrieve details of a specific card by its card key. |
| investec_card_get_codeB | Retrieve the draft/working JavaScript code uploaded to a programmable card. |
| investec_card_update_codeB | Upload a draft JavaScript code block for a programmable card. |
| investec_card_publish_codeA | Publish the draft code block for a card to make it active for transactions. |
| investec_card_get_published_codeB | Retrieve the currently active/published JavaScript code running on the programmable card. |
| investec_card_execute_codeA | Simulate a transaction authorization request against a card's code to test the code logic. |
| investec_card_get_execution_historyB | Retrieve the logs and execution history of transaction approvals running on the card's programmable code. |
| investec_card_get_env_varsB | Retrieve environment variables (secrets/constants) configured for a card's code. |
| investec_card_update_env_varsB | Save environment variables (key-value strings) for a card's programmable code. |
| investec_card_toggle_programmableB | Toggle the programmable banking feature on/off for a specific card. |
| investec_card_countriesB | Get reference list of supported countries for card transactions. |
| investec_card_currenciesB | Get reference list of supported currencies for card transactions. |
| investec_card_merchantsA | Get reference list of merchant categories (MCCs). |
| investec_cib_list_accountsA | List all Corporate Banking (CIB) accounts and balances. |
| investec_cib_get_account_transactionsC | Retrieve corporate transaction history for a CIB account. |
| investec_cib_list_companiesA | List all companies associated with the CIB corporate profile. |
| investec_cib_get_orders_shipments_reportB | Get current orders and shipment status report for a corporate company. |
| investec_ifi_list_accountsA | List accounts linked to the active Intermediary profile. |
| investec_ifi_get_client_dashboardB | Query and view the client dashboard summary by keyword (client details, holdings). |
| investec_ifi_forex_list_bop_reportsA | List Balance of Payments (BOP) reports for foreign exchange reporting. |
| investec_ifi_forex_get_allowances_balanceB | Get foreign exchange allowances balance for a specific account. |
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 37 tools
Tools are organized by clear domain prefixes (card, cib, ifi, pb) and each tool targets a specific action on a specific entity. No two tools have overlapping purposes; even similar actions (e.g., list_accounts) are for different domains or contexts.
All tool names follow a strict pattern: 'investec_{domain}_{action}_{detail}' using snake_case. The consistent prefix and verb_noun structure makes the surface predictable and easy to navigate.
37 tools is on the higher side, but the server covers multiple distinct banking domains (cards, corporate, intermediary, private banking), each with a reasonable set of operations. The count is justified given the breadth of functionality.
Each domain includes essential CRUD-like operations, queries, and management actions (e.g., card lifecycle, account details, transactions, beneficiaries). Minor gaps exist (e.g., updating beneficiaries, creating accounts) but these are common omissions in banking APIs.