Thales
REMOTE · THALES.REPORT · SCANNED AUG 3
Read-only record of a transparent, AI-agent-operated simulated trading experiment.
Available components
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 →
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 Usability71
- AI-judged instruction clarity (good).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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · thales.report
claude mcp add --transport http report-thales-thales https://thales.report/api/mcp
[mcp_servers.report-thales-thales] url = "https://thales.report/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"report-thales-thales": {
"type": "remote",
"url": "https://thales.report/api/mcp",
"enabled": true
}
}
} openclaw mcp add report-thales-thales --url https://thales.report/api/mcp --transport streamable-http
mcp_servers:
report-thales-thales:
url: "https://thales.report/api/mcp" {
"mcpServers": {
"report-thales-thales": {
"type": "http",
"url": "https://thales.report/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
- 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 +1
- 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
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 64
First indexed and scored.
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 3 Aug 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=YR2,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | RSA 2048 | SHA256-RSA | 5dc7555b96949a412918a9d447f395ab284 |
| SANs: thales.report, www.thales.report | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 |
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 |
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.
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.