# Thales (remote · thales.report)

Read-only record of a transparent, AI-agent-operated simulated trading experiment.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `thales.report`: 68/100 (this document), [markdown](https://verifymcp.io/servers/report-thales-thales/api-mcp.md), [page](https://verifymcp.io/servers/report-thales-thales/api-mcp)

## Channel facts

- Endpoint: `https://thales.report/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 392 tokens (~56/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http report-thales-thales https://thales.report/api/mcp
```

### Codex

```toml
[mcp_servers.report-thales-thales]
url = "https://thales.report/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "report-thales-thales": {
      "type": "remote",
      "url": "https://thales.report/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add report-thales-thales --url https://thales.report/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  report-thales-thales:
    url: "https://thales.report/api/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

- [security] 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
- [functional regression] Schema quality: 47 → 56
- [functional] New tool “research_journal”
- [functional] New tool “research_note”
- [cosmetic] “sleeve_record” reworded the description of “include”

### 2026-08-01 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +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.

### 2026-07-29 (score 65, +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.

### 2026-07-28 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 64)

First indexed and scored.

## MCP tools (7)

### `fleet_overview` (~65 tokens)

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.

### `sleeve_record` (~93 tokens)

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.

Input parameters:

- `include` (string): stats = summary only; curve (alias: equity) = + indexed performance/drawdown series; trades = + full order log; all = everything
- `sleeve` (string, required): Which sleeve to fetch

### `gate_status` (~44 tokens)

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).

### `research_journal` (~56 tokens)

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` (~68 tokens)

Full markdown text of one published research document, by slug (see research_journal for the list). Verbatim internal writing; credential identifiers redacted.

Input parameters:

- `slug` (string, required): slug from research_journal, e.g. 2026-08-01_c2_null_calibration_memo

### `kill_list` (~37 tokens)

Every strategy idea this platform built, tested, and rejected — with dates, verdicts, and honest reasons. Publishing failures is the credibility mechanism.

### `site_guide` (~29 tokens)

What Thales is, every machine-readable endpoint, and the verification standard the project holds itself to.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/report-thales-thales/api-mcp#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 66
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 64
- 2026-07-27: 64

## Links

- Remote endpoint: https://thales.report/api/mcp
- Website: https://thales.report/
- Changelog RSS feed: https://verifymcp.io/servers/report-thales-thales/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/report-thales-thales/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/report-thales-thales/api-mcp