io.github.tradingale/mcp
REMOTE · TRADINGALE.COM
Read-only martingale data: Martingale Score & Startingale for 250+ cryptos and US stocks.
Available components
Last scanned (22 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1535 tokens (~219/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 28 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 199 → 219 ▼ functional
- 25 Oct 26 0
- “search_instruments” reworded the description of “rounds” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 22 Oct 26 0
- “get_instrument” reworded the description of “type” cosmetic
- “list_top_crypto” reworded the description of “min_startingale” cosmetic
- “list_top_stocks” reworded the description of “min_startingale” cosmetic
- “search_instruments” reworded the description of “min_startingale” cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Tool “get_instrument” rewrote its description, which is the text the model reads security
- Tool “list_top_crypto” rewrote its description, which is the text the model reads security
- Tool “list_top_stocks” rewrote its description, which is the text the model reads security
- Tool “market_overview” rewrote its description, which is the text the model reads security
- Server version: 1.0.0 → 1.1.2 functional
- “list_top_crypto” reworded the description of “limit” cosmetic
- “list_top_crypto” reworded the description of “min_startingale” cosmetic
- “list_top_stocks” reworded the description of “limit” cosmetic
- “list_top_stocks” reworded the description of “min_startingale” cosmetic
- “search_instruments” reworded the description of “limit” cosmetic
- “search_instruments” reworded the description of “min_startingale” cosmetic
- “search_instruments” reworded the description of “rounds” cosmetic
- 23 Sept 26 0
- Tool “crypto_overview” rewrote its description, which is the text the model reads security
- Tool “get_instrument” rewrote its description, which is the text the model reads security
- Tool “list_top_crypto” rewrote its description, which is the text the model reads security
- Tool “list_top_stocks” rewrote its description, which is the text the model reads security
- Tool “market_overview” rewrote its description, which is the text the model reads security
- Tool “search_instruments” rewrote its description, which is the text the model reads security
- Tool “stock_overview” rewrote its description, which is the text the model reads security
- Schema quality: 158 → 194 ▼ functional
- “search_instruments” reworded the description of “exchange” cosmetic
- 18 Sept 26 0
- Tool “crypto_overview” rewrote its description, which is the text the model reads security
- Tool “get_instrument” rewrote its description, which is the text the model reads security
- Tool “list_top_crypto” rewrote its description, which is the text the model reads security
- Tool “list_top_stocks” rewrote its description, which is the text the model reads security
- Tool “market_overview” rewrote its description, which is the text the model reads security
- Tool “search_instruments” rewrote its description, which is the text the model reads security
- Tool “stock_overview” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “get_instrument” reworded the description of “symbol” cosmetic
- “get_instrument” reworded the description of “type” cosmetic
- “list_top_crypto” reworded the description of “limit” cosmetic
- “list_top_crypto” reworded the description of “min_startingale” cosmetic
- “list_top_stocks” reworded the description of “limit” cosmetic
- “list_top_stocks” reworded the description of “min_startingale” cosmetic
- “search_instruments” reworded the description of “exchange” cosmetic
- “search_instruments” reworded the description of “limit” cosmetic
- “search_instruments” reworded the description of “min_martingale” cosmetic
- “search_instruments” reworded the description of “min_startingale” cosmetic
- “search_instruments” reworded the description of “rounds” cosmetic
- “search_instruments” reworded the description of “type” cosmetic
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 4 Nov 2026 · Probed https://tradingale.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tradingale.com | CN=YR1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 62a638732286ec8e8b9d2204101381e99c6 |
| SANs: tradingale.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tradingale.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tradingale.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://tradingale.com/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://tradingale.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-MDZhZDRhZjEtZmMxMi00Yzc1LWFkNGUtMDQ1ZDJkNmMyNDIz' https://auth.tradingale.com https://vercel.live; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://vercel.live; img-src 'self' data: blob: https://auth.tradingale.com https://s.gravatar.com https://secure.gravatar.com https://vercel.live https://vercel.com; font-src 'self' https://fonts.gstatic.com https://vercel.live https://assets.vercel.com; frame-src 'self' https://auth.tradingale.com https://vercel.live; frame-ancestors 'self'; connect-src 'self' https://auth.tradingale.com https://api.binance.com https://api.kraken.com https://api.hyperliquid.xyz https://*.sentry.io https://vercel.live wss://ws-us3.pusher.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self' https://auth.tradingale.com; upgrade-insecure-requests; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Protected resource metadata
| Document | https://tradingale.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://tradingale.com/mcp |
| Authorisation server | https://tradingale.com/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tradingale.com/mcp | Verified | 200 | |
| http (plaintext) | http://tradingale.com/mcp | HTTPS enforced | 308 | https://tradingale.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 →
crypto_overview ~92
ONE SNAPSHOT OF CRYPTO ONLY, no arguments: the top 5 cryptos by Martingale Score (0-5) with their Startingale readings. Use this for a quick picture of crypto alone. To choose how many or apply a Startingale floor, use list_top_crypto; to cover stocks as well, use market_overview. Answers in formatted text. Costs 5 units of the monthly quota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_instrument ~239
ONE named instrument, in full. Returns the Martingale Score (0-5), the current Startingale reading, the score breakdown, the sequence structure (spacing, rounds, quantity multipliers) and exchange availability for a single crypto or US stock. Use this when you already know the symbol; use search_instruments to find symbols. Answers in formatted text, not JSON. Costs 1 unit of the monthly quota: the cheapest call, so walking a handful of known symbols one by one is fine.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Ticker symbol, not a name: BTC (not Bitcoin), ETH, SOL for crypto; AAPL, NVDA, MELI for US stocks. Case-insensitive. Use search_instruments if you only know the name. |
| type | string | – | Which catalogue to answer from: crypto or stock. Optional. Without it, both are searched; if the symbol exists in both (some tickers are a coin and a US stock), the answer lists both and asks you to… |
No output schema declared.
No examples provided.
list_top_crypto ~205
A RANKED LIST OF CRYPTOS, sized by you: choose how many (1-20) and an optional minimum Startingale. Use this when those two are the ONLY conditions; anything else (a venue, a round count, a minimum Martingale Score) needs search_instruments. For a fixed top 5 with no arguments, use crypto_overview. Answers in formatted text. Costs 3 units of the monthly quota.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return, highest Martingale Score first. 1-20, default 10. |
| min_startingale | number | – | Keep only entries at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which ranks them. Scale 0-5: 4.3 and above reads Strong, 3.7… |
No output schema declared.
No examples provided.
list_top_stocks ~203
A RANKED LIST OF US STOCKS, sized by you: choose how many (1-20) and an optional minimum Startingale. Use this when those two are the ONLY conditions; anything else (a round count or a minimum Martingale Score) needs search_instruments. For a fixed top 5 with no arguments, use stock_overview. Answers in formatted text. Costs 3 units of the monthly quota.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return, highest Martingale Score first. 1-20, default 10. |
| min_startingale | number | – | Keep only entries at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which ranks them. Scale 0-5: 4.3 and above reads Strong, 3.7… |
No output schema declared.
No examples provided.
market_overview ~130
ONE SNAPSHOT OF BOTH MARKETS, no arguments. Top instruments across crypto AND US stocks together, ranked by Martingale Score (0-5), with their Startingale readings. Use this to open a conversation or answer "how do things look right now". For a single asset class use crypto_overview or stock_overview; to choose the count or filter, use search_instruments. Answers in formatted text. Costs 10 units of the monthly quota: the most expensive call, since it reads both catalogues; the single-class overviews cost half, so do not call this in a loop.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_instruments ~432
THE QUERY TOOL: find instruments matching criteria across an asset class. Filter by minimum Martingale score, minimum Startingale, exchange and more; returns a ranked list. Use it when a filter OTHER than count or Startingale floor is needed: exchange, round count, or a minimum Martingale Score. If the only conditions are how many and a Startingale floor, list_top_crypto or list_top_stocks do the same in one step; for no conditions at all, use an overview. Answers in formatted text. Costs 3 units of the monthly quota.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | string | – | Keep only instruments that venue lists. Exactly one of: binance, kraken_pro (note the underscore), hyperliquid. This is a listing fact about the market, reported for callers who run their own executi… |
| limit | integer | – | How many to return, highest Martingale Score first. 1-20, default 10. |
| min_martingale | number | – | Keep only instruments at or above this Martingale Score. Scale 0-5, higher means the price behaviour fits the sequence structure better. Above 4 is the usual starting point for a shortlist. Default:… |
| min_startingale | number | – | Keep only instruments at or above this Startingale reading: how well the CURRENT price sits versus the structure, unlike the Martingale Score which is about behaviour over time. Scale 0-5: 4.3 and ab… |
| rounds | string | – | Keep only instruments whose sequence has this many rounds: the total number of orders, initial round included (4 or 5). Omit for both. |
| type | string | – | Which catalogue to search. One at a time, not both. Default: crypto. |
No output schema declared.
No examples provided.
stock_overview ~93
ONE SNAPSHOT OF US STOCKS ONLY, no arguments: the top 5 stocks by Martingale Score (0-5) with their Startingale readings. Use this for a quick picture of stocks alone. To choose how many or apply a Startingale floor, use list_top_stocks; to cover crypto as well, use market_overview. Answers in formatted text. Costs 5 units of the monthly quota.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.tradingale/mcp server?
io.github.tradingale/mcp is a hosted endpoint at https://tradingale.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 · tradingale.com
claude mcp add --transport http tradingale-mcp 'https://tradingale.com/mcp'
What is the io.github.tradingale/mcp server?
io.github.tradingale/mcp is listed in the public MCP registry as io.github.tradingale/mcp. Read-only martingale data: Martingale Score & Startingale for 250+ cryptos and US stocks. This page covers its hosted endpoint (https://tradingale.com/mcp).
Is the io.github.tradingale/mcp server safe to use?
io.github.tradingale/mcp scores 91 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 io.github.tradingale/mcp server expose?
io.github.tradingale/mcp exposes 7 tools: get_instrument, search_instruments, list_top_crypto, list_top_stocks, market_overview, and 2 more. Their descriptions and schemas cost roughly 1,394 tokens of context every time the server is loaded.
Does the io.github.tradingale/mcp server require authentication?
Yes. io.github.tradingale/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.tradingale/mcp server still maintained?
io.github.tradingale/mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.