Thales
REMOTE · THALES.REPORT
Read-only record of a transparent, AI-agent-operated simulated trading experiment.
Available components
Last scanned (9 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 392 tokens (~56/item across 7 items; 7 tools + 0 resources), lean.Pass
- 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "kill_list" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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 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
- 26 Aug 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
- 11 Aug 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
- 3 Aug 26 0
- Tool “fleet_overview” rewrote its description, which is the text the model reads security
- Tool “sleeve_record” rewrote its description, which is the text the model reads security
- Schema quality: 47 → 56 ▼ functional
- New tool “research_journal” functional
- New tool “research_note” functional
- “sleeve_record” reworded the description of “include” cosmetic
- 1 Aug 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
- 31 Jul 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
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Nov 2026 · Probed https://thales.report/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=thales.report | CN=YR1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 61e4328ca3c95a06349c72a4413cd58891e |
| SANs: thales.report, www.thales.report | ||||||
| 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 thales.report. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| report. | present | 23221 | 8 | Verified |
| thales.report. | absent | 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 |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://thales.report/api/mcp | Verified | 200 | |
| http (plaintext) | http://thales.report/api/mcp | HTTPS enforced | 308 | https://thales.report/api/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 →
fleet_overview ~65
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gate_status ~44
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kill_list ~37
Every strategy idea this platform built, tested, and rejected — with dates, verdicts, and honest reasons. Publishing failures is the credibility mechanism.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
research_journal ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
research_note ~68
Full markdown text of one published research document, by slug (see research_journal for the list). Verbatim internal writing; credential identifiers redacted.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | slug from research_journal, e.g. 2026-08-01_c2_null_calibration_memo |
No output schema declared.
No examples provided.
site_guide ~29
What Thales is, every machine-readable endpoint, and the verification standard the project holds itself to.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sleeve_record ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | stats = summary only; curve (alias: equity) = + indexed performance/drawdown series; trades = + full order log; all = everything |
| sleeve | string | yes | Which sleeve to fetch |
No output schema declared.
No examples provided.
How do I install the Thales MCP server?
Thales is a hosted endpoint at https://thales.report/api/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 · thales.report
claude mcp add --transport http report-thales-thales 'https://thales.report/api/mcp'
What is the Thales MCP server?
Thales is an MCP server listed in the public MCP registry as report.thales/thales. Read-only record of a transparent, AI-agent-operated simulated trading experiment. This page covers its hosted endpoint (https://thales.report/api/mcp).
Is the Thales MCP server safe to use?
Thales scores 80 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 Thales MCP server expose?
Thales exposes 7 tools: fleet_overview, sleeve_record, gate_status, research_journal, research_note, and 2 more. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.
Does the Thales MCP server require authentication?
No. We connected to Thales without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Thales MCP server still maintained?
Thales is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.