TradingLookup open data
REMOTE · TRADINGLOOKUP.COM
Prop firm, broker and exchange data plus codes firms issued to us. Read-only, CC BY 4.0.
Available components
Last scanned (8 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 640 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 514 → 640 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “get_promo_code” functional
- 20 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://tradinglookup.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tradinglookup.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d5402cd1788c8ef90e148ffd947fc56b |
| SANs: tradinglookup.com, *.tradinglookup.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tradinglookup.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tradinglookup.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tradinglookup.com/mcp | Verified | 200 | |
| http (plaintext) | http://tradinglookup.com/mcp | HTTPS enforced | 301 | https://tradinglookup.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_dataset Describe one dataset ~53
One dataset in full: what it holds, its files with columns and row counts, the download addresses, the licence and how to cite it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A dataset id from list_datasets or search. |
No output schema declared.
No examples provided.
get_facts Facts for one firm ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The firm's name, for example "Topstep", or its page path from search. |
No output schema declared.
No examples provided.
get_promo_code Promo code for a prop firm ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| firm | string | – | The firm's name, for example "PropXP". Leave empty for every code. |
No output schema declared.
No examples provided.
list_datasets List open datasets ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_rows Read rows from a dataset file ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | array | – | Columns to return. Default: all. |
| file | string | – | File name from get_dataset. Default: the dataset's first CSV file. |
| id | string | yes | 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). |
No output schema declared.
No examples provided.
search Search TradingLookup ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | A name or topic, for example "FTMO", "CFD loss rates" or "futures prop firm prices". |
No output schema declared.
No examples provided.
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.
remote · tradinglookup.com
claude mcp add --transport http tradinglookup-data 'https://tradinglookup.com/mcp'
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.