Model Context Protocol

Put TradeRange in your AI client.

TradeRange runs a public MCP server. Point a client that speaks the Model Context Protocol at it and your assistant can look up prices, read what we publish, and — if you allow it — read the paper portfolios on your own account. It only reads.

Server URL https://mcp.traderange.net/mcp

What it can do

Thirteen tools, four scopes.

Market data

quotes:read

Prices, OHLCV candles, ticker search and a side-by-side comparison of up to eight symbols. Equities, ETFs and crypto pairs. Delayed data.

  • lookup_quote
  • get_candles
  • search_symbols
  • compare_symbols

Fundamentals

quotes:read

What a company is and what it is worth: sector, headcount, market cap, P/E, margins, growth, the 52-week range, and the next earnings date. Fields a symbol has no figure for come back empty rather than as a zero.

  • company_profile
  • key_stats
  • earnings_calendar

Game catalog

catalog:read

The live TradeRange games — the same catalog the site itself is built from.

  • list_games
  • get_game

Published articles

articles:read

Everything live across Learn, Analysis and Blog. Published pieces only.

  • list_articles
  • get_article

Your portfolios

portfolio:read

Names, benchmarks and holdings on your own account. Nobody else’s, and only if you grant this scope.

  • list_portfolios
  • get_portfolio

Nothing here writes, trades, or reaches another account. An administrator can switch the server or any single tool off, so read tools/list rather than assuming all nine are live.

Connecting

Three steps.

You add the URL

Paste the server URL into your client. It signs itself up — there is no key to request and none to copy.

You approve it

It sends you to a TradeRange screen listing exactly what it is asking for. Sign in and decide.

It gets a token

Approving grants the scopes you picked and nothing else. The tools appear in your assistant.

Every TradeRange account can do this. There is nobody to ask and nothing to be granted — sign in, approve, done. Stuck on a client that will not connect? Our Discord is tradely.dev.

The details

For whoever is wiring it up.

Transport
Streamable HTTP, stateless — POST JSON-RPC to the server URL. No SSE stream and no session, so GET and DELETE answer 405.
Protocol
2025-06-18 (default), 2025-03-26, 2024-11-05.
Auth
OAuth 2.1 with PKCE (S256), then a bearer token. Dynamic client registration is open. Discovery at /.well-known/oauth-protected-resource/mcp, which names https://mcp.traderange.net/mcp as the authorization server.
Scopes
quotes:read, catalog:read and articles:read are the default ask. portfolio:read is granted separately.
Rate limit
Six tool calls a minute and sixty an hour, per token. initialize, tools/list and ping do not count — connecting and looking around are free, so a client that reconnects has its whole allowance for real requests. Over the limit is an HTTP 429 with Retry-After; wait that out rather than retrying straight away.
Status
GET https://mcp.traderange.net/mcp/info

Market data is delayed and may be wrong. Nothing this server returns is financial advice, and some TradeRange content is AI-generated. Using it is using TradeRange — see the Terms and Privacy Policy.