sc-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SC_MCP_CACHE_TTL | No | Seconds to cache successful responses in-process. Set 0 to disable caching (always hit the broker live). | 300 |
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 |
|---|---|
| sc_overviewB | Get Scalable Capital broker portfolio overview — total value, cash, performance. Returns live data directly from the broker. |
| sc_holdingsC | Get Scalable Capital portfolio holdings — all positions with current prices, quantities, and market values. Live broker data. |
| sc_transactionsB | List Scalable Capital broker transactions with optional filters. Use for reconciliation, tax analysis, or reviewing trade history. |
| sc_analyticsA | Get Scalable Capital portfolio analytics — allocation breakdowns, sector/region exposure, and performance attribution. |
| sc_security_newsA | Get latest news summary for a specific security by ISIN from Scalable Capital. |
| sc_quoteB | Get the current Scalable Capital quote for a security by ISIN. |
| sc_searchC | Search securities within the Scalable Capital broker portfolio context. |
| sc_transactionA | Get details for a single Scalable Capital broker transaction by ID. |
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
Most tools are clearly distinct, but sc_transactions vs sc_transaction and the overlapping portfolio summary tools (sc_overview, sc_holdings, sc_analytics) could cause a mis-selection. The descriptions do clarify the boundaries, so this is only a minor concern.
All tool names follow the same sc_ prefix plus resource noun pattern, using snake_case consistently. The plural/singular distinction between sc_transactions and sc_transaction cleanly signals list vs detail.
Eight tools is well-scoped for a broker-focused MCP server. Each tool covers a meaningful read-only capability without unnecessary bloat or thin redundancy.
The server covers the core read-only portfolio workflow: overview, holdings, transactions, analytics, quotes, search, and news. There are minor gaps around order management or deeper security metadata, but these seem outside the apparent scope and can be worked around.