mcp-over-quik
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEBQUIK_CA_BUNDLE | No | Path to the CA chain file for webquik.sberbank.ru. Alternative to placing the CA chain in certs/sberca-chain.pem. | |
| WEBQUIK_SSL_VERIFY | No | Set to false for local debugging to disable SSL certificate verification. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Create a personal webQUIK session for this MCP connection. Required before any trading or market-data tools. Each user connects with their own broker account (login starts with 4). Returns pin_required if SMS confirmation is needed — then call submit_pin. |
| submit_pinA | Submit SMS/PIN code after login returned pin_required. |
| logoutA | Logout from webQUIK and remove this MCP connection's session. |
| session_statusA | Return this MCP connection's webQUIK session state. |
| webquik_list_classesA | List instrument classes available after login (e.g. TQBR for MOEX equities). |
| webquik_search_securitiesB | Search securities by ticker or name within loaded class lists. |
| webquik_get_portfolioB | Subscribe to and return client portfolio positions. |
| webquik_get_ordersC | Subscribe to and return active orders. |
| webquik_get_tradesC | Subscribe to and return recent trades. |
| webquik_get_limitsB | Return cash and depo limits. |
| webquik_get_quotesC | Get order book quotes for an instrument (e.g. class_code=TQBR, sec_code=SBER). |
| webquik_get_security_infoC | Get static parameters for a security (lot size, price step, etc.). |
| webquik_send_orderC | Place a new order on MOEX via webQUIK. side: buy | sell order_type: limit | market account: trading account (e.g. L01-00000F00) client_code: broker client code |
| webquik_cancel_orderB | Cancel an active order by order number and class code. |
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 14 tools
Each tool targets a clearly distinct action or resource: session lifecycle (login, logout, session_status, submit_pin), market data (list_classes, search_securities, get_quotes, get_security_info), account data (get_portfolio, get_orders, get_trades, get_limits), and order actions (send_order, cancel_order). There is no meaningful overlap between any pair.
Most trading/market-data tools use a consistent webquik_verb_noun pattern, but the session tools (login, logout, session_status, submit_pin) lack the prefix and mix verb-only and noun-only styles. The mixed convention is still readable but not fully predictable.
14 tools is well within the ideal range and each tool earns its place for a trading integration. The set covers session, market data, account data, and order operations without redundancy.
Core lifecycle for trading is well covered: login/logout, session status, market data, portfolio/orders/trades/limits, and order placement/cancellation. A modify/replace order tool is a minor but noticeable gap, and there is no order-history beyond recent trades, but agents can work around these limitations.