Trading212 MCP Server

Created By
RohanAnandPandita year ago
Overview

What is Trading212 MCP Server?

The Trading212 MCP Server is an implementation of the Model Context Protocol that facilitates seamless data connectivity to the Trading212 trading platform, enabling advanced interaction capabilities for users.

How to use Trading212 MCP Server?

To use the Trading212 MCP Server, clone the repository from GitHub, configure your environment, and run the server using Docker or Python. You will need to generate an API key from your Trading212 account settings.

Key features of Trading212 MCP Server?

  • Comprehensive account management including cash balance monitoring and portfolio management.
  • Advanced order handling with support for market, limit, and stop-limit orders.
  • Real-time market data access and historical trading data.
  • Financial analysis tools for professional trading insights.
  • Full support for the MCP protocol with resource-based API endpoints.

Use cases of Trading212 MCP Server?

  1. Managing trading accounts and monitoring cash balances.
  2. Executing and managing various types of orders on the Trading212 platform.
  3. Analyzing trading data for better financial decision-making.
  4. Integrating with other tools for enhanced trading capabilities.

FAQ from Trading212 MCP Server?

  • Can I use this server for live trading?

Yes, you can use it for live trading by setting the appropriate environment in your configuration.

  • Is this an official Trading212 product?

No, this is an unofficial implementation of the Trading212 MCP protocol.

  • What are the technical requirements?

You need Python >= 3.11 and specific libraries as mentioned in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RohanAnandPandit
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago