Read-only MCP server for brokerage data via SnapTrade
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"snaptrade-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# SnapTrade MCP Server A read-only MCP (Model Context Protocol) server that connects AI agents to brokerage data via SnapTrade. Works with Claude Code, Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. **10 tools. Read-only. No trading. Safe by design.** ## What You Can Do | Tool | Description | |------|-------------| | `snaptrade_list_accounts` | List all connected brokerage accounts | | `snaptrade_get_balance` | Cash balances for an account | | `snaptrade_get_positions` | Current holdings (stocks, ETFs) | | `snaptrade_get_orders` | Order history with filters | | `snaptrade_get_activities` | Transaction log (dividends, fees) | | `snaptrade_portfolio_summary` | All accounts + balances + positions in one call | | `snaptrade_search_symbols` | Look up stocks/ETFs by name or ticker | | `snaptrade_list_brokerages` | Supported brokerages | | `snaptrade_check_status` | API health check | | `snaptrade_setup` | Generate URL to connect a new brokerage | ## Prerequisites 1. **SnapTrade API credentials** — a `clientId` and `consumerKey` from [snaptrade.com](https://snaptrade.com). Sign up for a developer account and find your keys in the dashboard. 2. **Python 3.10+** ## Where do my API keys go? Your SnapTrade credentials never leave your machine. Here's what happens: - Your `clientId` and `consumerKey` are stored in a **local config file** on your computer (or in environment variables you set yourself). - The MCP server reads them at startup to authenticate with SnapTrade's API. - They are **never** sent to your AI client, **never** included in tool responses, and **never** logged. - The server is read-only — it cannot trade, modify accounts, or delete anything. This is the same way any API integration handles credentials. Your keys stay on your machine, period. ## Installation ### Option A: Install from PyPI (recommended) ```bash pip install snaptrade-mcp ``` That's it. This installs the `snaptrade-mcp` command and all dependencies. ### Option B…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.