Skip to content

Thales

by thales.report · remote · no sign-in to list tools · v1.0.0 · published by report.thales

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

Deletes · 1Changes · 5
CompareRegistry entry

7 tools: 1 can delete or cancel things, 5 change things and 1 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

1 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Deletes or cancels 1Claude Code: deny
  • kill_listEvery strategy idea this platform built, tested, and rejected — with dates, verdicts, and honest reasons.No findings

    Why it is in this group

    • The name "kill_list" says "kill": a word for removing or ending something.
    Description, as the server wrote it
    Every strategy idea this platform built, tested, and rejected — with dates, verdicts, and honest reasons. Publishing failures is the credibility mechanism.
Changes things 5Claude Code: ask
  • fleet_overviewSummary of every strategy sleeve: total and evaluation-window returns, drawdown, live days, and the 20 most recent submitted orders.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • research_journalThe live research journal: every internal research document (experiment pre-registrations, incident write-ups, verdicts including nulls), auto-published verbatim by the daily expor…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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_noteFull markdown text of one published research document, by slug (see research_journal for the list).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...r the list). Verbatim internal writing; credential identifiers redacted."

      What this check looks for
    Description, as the server wrote it
    Full markdown text of one published research document, by slug (see research_journal for the list). Verbatim internal writing; credential identifiers redacted.
  • site_guideWhat Thales is, every machine-readable endpoint, and the verification standard the project holds itself to.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    What Thales is, every machine-readable endpoint, and the verification standard the project holds itself to.
  • sleeve_recordFull public record for one sleeve: stats, indexed performance curve (100 = inception), drawdown series, and the complete submitted-order log.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 1Claude Code: allow
  • gate_statusThe pre-registered go-live gate: criteria frozen on 2026-07-05, current progress, and the binding interpretation (this gate tests operational competence, not alpha).No findings

    Why it is in this group

    • The name "gate_status" says "status": a word for reading.
    Description, as the server wrote it
    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).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__thales__gate_status"
    ],
    "ask": [
      "mcp__thales__fleet_overview",
      "mcp__thales__sleeve_record",
      "mcp__thales__research_journal",
      "mcp__thales__research_note",
      "mcp__thales__site_guide"
    ],
    "deny": [
      "mcp__thales__kill_list"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as thales. Review it before you use it.