io.github.tradingale/mcp
io.github.tradingale/mcp · 1.1.2
Read-only martingale data: Martingale Score & Startingale for 250+ cryptos and US stocks.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 35 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://tradingale.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 7 tools.
- Protocol
- 2025-06-18
- Calls itself
- tradingale 1.1.2
- Handshake time
- 130 ms
- HTTP status
- 200
The tools it lists (7, as of 22 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_instrumentONE 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.
search_instrumentsTHE 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.
list_top_cryptoA 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.
list_top_stocksA 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.
market_overviewONE 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
io.github.tradingale/mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 77 days ago. The registry entry