# TradingLookup open data (remote · tradinglookup.com)

Prop firm, broker and exchange data plus codes firms issued to us. Read-only, CC BY 4.0.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tradinglookup.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/tradinglookup-data/tradinglookup.md), [page](https://verifymcp.io/servers/tradinglookup-data/tradinglookup)

## Channel facts

- Endpoint: `https://tradinglookup.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 640 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the TradingLookup open data MCP server?

TradingLookup open data is a hosted endpoint at https://tradinglookup.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http tradinglookup-data 'https://tradinglookup.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tradinglookup-data": {
      "url": "https://tradinglookup.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tradinglookup-data": {
      "type": "http",
      "url": "https://tradinglookup.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tradinglookup-data]
url = "https://tradinglookup.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tradinglookup-data": {
      "type": "remote",
      "url": "https://tradinglookup.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tradinglookup-data --url 'https://tradinglookup.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tradinglookup-data:
    url: "https://tradinglookup.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tradinglookup-data": {
      "Transport": "http",
      "Url": "https://tradinglookup.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tradinglookup-data -t streamable-http -u 'https://tradinglookup.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tradinglookup-data": {
      "type": "http",
      "url": "https://tradinglookup.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 70, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 514 → 640
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “get_promo_code”

### 2026-11-20 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-19 (score 68)

First indexed and scored.

## MCP tools (6)

### `search` (~80 tokens)

Search TradingLookup

Find prop firms, brokers, crypto exchanges and open datasets on TradingLookup by name or topic. Returns matches with their page address. Use get_facts or get_dataset next.

Input parameters:

- `limit` (integer)
- `query` (string, required): A name or topic, for example "FTMO", "CFD loss rates" or "futures prop firm prices".

### `get_facts` (~72 tokens)

Facts for one firm

The dated facts TradingLookup publishes for one prop firm, broker or crypto exchange (for example cheapest plan, profit split, platforms), each read from the firm's own pages, with the page to cite.

Input parameters:

- `name` (string, required): The firm's name, for example "Topstep", or its page path from search.

### `list_datasets` (~54 tokens)

List open datasets

Every open dataset TradingLookup publishes (CC BY 4.0): prop firm prices and rules, CFD loss rates, broker and exchange fees, market calendars and macro series. Returns id, name, page and data date.

### `get_dataset` (~53 tokens)

Describe one dataset

One dataset in full: what it holds, its files with columns and row counts, the download addresses, the licence and how to cite it.

Input parameters:

- `id` (string, required): A dataset id from list_datasets or search.

### `read_rows` (~151 tokens)

Read rows from a dataset file

Rows from one CSV file of a dataset, at most 50 a call. Filter with "where" (column: text the value must contain). Files over 200 KB are not read whole: filter by firm_slug to read one firm, or use the download address in the result.

Input parameters:

- `columns` (array): Columns to return. Default: all.
- `file` (string): File name from get_dataset. Default: the dataset's first CSV file.
- `id` (string, required): A dataset id.
- `limit` (integer)
- `offset` (integer)
- `where` (object): Column name to text; a row is kept when the value contains the text (case-insensitive).

### `get_promo_code` (~105 tokens)

Promo code for a prop firm

The discount code a prop firm issued to TradingLookup, if we hold one: the code, what it gives, the date the firm issued it, the firm's own website and our page for it. Leave "firm" empty to list every code we hold. We only list codes the firm gave us; if we hold none for a firm, it says so.

Input parameters:

- `firm` (string): The firm's name, for example "PropXP". Leave empty for every code.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tradinglookup-data/tradinglookup#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 68

## Common questions

### What is the TradingLookup open data MCP server?

TradingLookup open data is an MCP server listed in the public MCP registry as io.github.tradinglookup/data. Prop firm, broker and exchange data plus codes firms issued to us. Read-only, CC BY 4.0. This page covers its hosted endpoint (https://tradinglookup.com/mcp).

### Is the TradingLookup open data MCP server safe to use?

TradingLookup open data scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the TradingLookup open data MCP server expose?

TradingLookup open data exposes 6 tools: search, get_facts, list_datasets, get_dataset, read_rows, get_promo_code. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.

### Does the TradingLookup open data MCP server require authentication?

No. We connected to TradingLookup open data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TradingLookup open data MCP server still maintained?

TradingLookup open data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the TradingLookup open data MCP server?

VerifyMCP ran 13 checks on TradingLookup open data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tradinglookup.com/mcp
- Website: https://tradinglookup.com/data/
- Changelog RSS feed: https://verifymcp.io/servers/tradinglookup-data/tradinglookup.xml
- Changelog JSON feed: https://verifymcp.io/servers/tradinglookup-data/tradinglookup/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tradinglookup-data/tradinglookup.json
- HTML version of this page: https://verifymcp.io/servers/tradinglookup-data/tradinglookup
