tradinglookup-data
Registry code: cb70d0fc30abce81
Read-only access to TradingLookup's open data (https://tradinglookup.com/data/): prop firms, brokers, crypto exchanges and market calendars. Every figure is what the firm or official source published on the date shown. Cite the source_url in each result. CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Credit TradingLookup and link the source page. Data, not advice. Each figure is what the firm or official source published on the date shown.
- endpoint
- https://tradinglookup.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is tradinglookup-data live?
- Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
- Is tradinglookup-data free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does tradinglookup-data have?
- 5 tools: get_facts, read_rows, search, list_datasets, get_dataset.
- Is tradinglookup-data safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_facts unknown 8h ago
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.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "The firm's name, for example \"Topstep\", or its page path from search." } } }arguments 12 linesread_rows unknown 8h ago
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.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "A dataset id." }, "file": { "type": "string", "description": "File name from get_dataset. Default: the dataset's first CSV file." }, "limit": { "type": "integer", "maximum": 50, "minimum": 1 }, "where": { "type": "object", "description": "Column name to text; a row is kept when the value contains the text (case-insensitive).", "additionalProperties": { "type": "string" } }, "offset": { "type": "integer", "minimum": 0 }, "columns": { "type": "array", "items": { "type": "string" }, "description": "Columns to return. Default: all." } } }arguments 39 linessearch unknown 8h ago
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.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 20, "minimum": 1 }, "query": { "type": "string", "description": "A name or topic, for example \"FTMO\", \"CFD loss rates\" or \"futures prop firm prices\"." } } }arguments 17 lineslist_datasets unknown never probed
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.
{ "type": "object", "properties": {} }arguments 4 linesget_dataset unknown never probed
One dataset in full: what it holds, its files with columns and row counts, the download addresses, the licence and how to cite it.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "A dataset id from list_datasets or search." } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idcb70d0fc30abce81.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/cb70d0fc30abce81/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/cb70d0fc30abce81?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.