go_mcp_server_tinvest
A lightweight MCP server in Go that integrates with the Tinkoff Invest API, exposing tools for searching instruments, placing market buy/sell orders, retrieving portfolio state, and getting market data (last price, order book, candles, trading status). It can run over MCP stdio and also includes an SSE HTTP server mode.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses an API token and account id via environment variables. README does not describe how the server logs secrets (assumed to be handled via env usage, but not proven). No mention of fine-grained scopes, IP allowlisting, TLS/HTTP security specifics beyond Tinkoff endpoint using :443, or operational controls for safe order placement. Buy/sell are market orders, which increases risk if an agent misbehaves.
⚡ Reliability
Best When
When you want to prototype or automate agent-driven research/trading workflows against Tinkoff Invest using a local MCP server and are comfortable adding your own safety and reliability layers.
Avoid When
When you need strong, documented operational guarantees (SLA, retries/idempotency semantics) or when you cannot ensure secure handling of brokerage credentials.
Use Cases
- • Trading assistants that need tool-based access to search instruments and place orders
- • Portfolio viewers via an MCP tool (current portfolio state)
- • Market data enrichment for agents (last price, order book depth, historical candles, trading status)
- • Building agent workflows that call typed MCP tool inputs/outputs to interact with Tinkoff Invest
Not For
- • Production-grade brokerage execution without additional safeguards (risk checks, order confirmation, idempotency, and audit controls)
- • Users who cannot securely manage an API token and account id
- • Use cases requiring strict compliance/audit controls without further review
Interface
Authentication
Authentication is by providing a Tinkoff API token via environment variables; README mentions error codes like Unauthenticated 40003 when environment does not match (production vs sandbox) and NotFound 50004 when account id is incorrect.
Pricing
No pricing information is provided for the MCP server itself; costs would primarily come from Tinkoff Invest API usage and your hosting.
Agent Metadata
Known Gotchas
- ⚠ Placing buy/sell sends market orders and the server determines which account/choice applies (as per environment variables); agents may place irreversible orders if not safeguarded.
- ⚠ Token and endpoint must match the intended environment (production vs sandbox) or Unauthenticated 40003 may occur.
- ⚠ Portfolio requires a correct TINKOFF_ACCOUNT_ID or will fail (NotFound 50004).
- ⚠ candles output is limited to the first 50 candles for compactness (agents may assume full range unless they handle truncation).
- ⚠ orderbook depth is constrained to 1–50; agents should validate depth inputs.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for go_mcp_server_tinvest.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.