This MCP tool will allow AI agents to connect to your Trading212 account in order to manage your portfolio for you
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":"mcp-server-trading212","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.
# Trading212 MCP Server <div style="color: #856404; background-color: #fff3cd; border-left: 4px solid #ffeeba; padding: 10px;"> ⚠️ **Warning**: Putting an AI in charge of your stock broker is inherently risky. Do not use this connector unless you have considered the risks and put appropriate controls in place to manage those risks. By using this connector you agree to the terms of the MIT license, which includes indemnity from any financial losses resulting from it's use. You should test the connector using "demo" mode before deploying to your live account. **Use at your own risk** </div> ## Overview The purpose of this MCP tool is to allow you to connect agentic AI to your Trading212 brokerage account. This will allow you to perform actions such as the following: - Allow an AI to analyse and critique your portfolio - Get the AI to suggest some stocks and order them on your behalf (due to a restriction in the Trading212 API, orders can only be created in practice mode currently) - Allow the AI to manage/update a Trading212 investment pie on your behalf - Allow the AI to create a Trading212 investment pie on your behalf (coming soon) Due to aggressive API rate limits imposed by the Trading212 API, this tool will attempt to cache API results in-memory (the default TTL is 5 minutes). If you deploy a local Redis server on port 6379 the tool will use it instead of the in-memory cache. ## Security tips - If you are hosting the tool server remotely and connecting over the internet, make sure you deploy a reverse proxy with HTTPS, and ideally with Mutual TLS verification. - You should avoid saving your Trading212 API key in plaintext. Try using an automated secret manager like keyring or 1password - Always test the connector on the demo account before connecting to your real account ## Components ### Resources The server exposes some dynamic resources: - `trading212://equity/portfolio`: My Portfolio - All assets within your trading portfolio - `trading212://equ…
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.