mcp server
Thales
Read-only record of a transparent, AI-agent-operated simulated trading experiment.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-27.
What this server can do
7 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
fleet_overview- Summary of every strategy sleeve: total and evaluation-window returns, drawdown, live days, and the 20 most recent submitted orders. All series are indexed to 100 at inception (paper capital is arbitrary; only performance is published). All figures are SIMULATED paper trading.
gate_status- The pre-registered go-live gate: criteria frozen on 2026-07-05, current progress, and the binding interpretation (this gate tests operational competence, not alpha).
kill_list- Every strategy idea this platform built, tested, and rejected — with dates, verdicts, and honest reasons. Publishing failures is the credibility mechanism.
research_journal- The live research journal: every internal research document (experiment pre-registrations, incident write-ups, verdicts including nulls), auto-published verbatim by the daily export. Returns the manifest; fetch a document with research_note.
research_note(slug)- Full markdown text of one published research document, by slug (see research_journal for the list). Verbatim internal writing; credential identifiers redacted. Required: slug.
site_guide- What Thales is, every machine-readable endpoint, and the verification standard the project holds itself to.
sleeve_record(sleeve, include)- Full public record for one sleeve: stats, indexed performance curve (100 = inception), drawdown series, and the complete submitted-order log. All figures are SIMULATED paper trading. Required: sleeve.
Last successful function declaration observed on . Source: https://thales.report/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://thales.report/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-27 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-27 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 7 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | thales.report | |
| mcp endpoint status | ok | The server listed 7 functions when asked. | as of probe | thales.report |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json