Skip to content

Autrady

by autrady.com · remote · no sign-in to list tools · v1.0.0 · published by com.autrady

Is a trading strategy's track record luck? Free luck check, plus what a full strategy audit checks.

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 only read.

Scanned Oct 21, 2026

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

claude mcp add --transport http strategy-audits https://autrady.com/mcp

Tools

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

2 tools

Changes things 1Claude Code: ask
  • luck_checkTests whether a trading strategy's claimed track record could be luck.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Tests whether a trading strategy's claimed track record could be luck. Returns how often the best of that many strategies with no edge at all would look this good, the record's t-statistic against the bar for that many tries, and how many months a real edge of this size needs to clear the bar with 80% probability. A rough check: it assumes independent months and ignores costs, so a real audit of the signals usually looks worse.

    Annotations the server declares

    • title: Check whether a track record could be luck
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 1Claude Code: allow
  • explain_auditDescribes a full Autrady audit of a strategy's actual signals: what to upload, how it works, the five questions it answers with what each caught in Autrady's own research, the pric…No findings

    Why it is in this group

    • The name "explain_audit" says "explain": a word for reading.
    Description, as the server wrote it
    Describes a full Autrady audit of a strategy's actual signals: what to upload, how it works, the five questions it answers with what each caught in Autrady's own research, the price, the free trial and where to start. Use it when someone asks how to test a bot, a newsletter or a backtest properly, what Autrady does, or what it costs.

    Annotations the server declares

    • title: What an Autrady audit checks and costs
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

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 strategy-audits https://autrady.com/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__strategy-audits__explain_audit"
    ],
    "ask": [
      "mcp__strategy-audits__luck_check"
    ],
    "deny": []
  }
}

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 strategy-audits. Review it before you use it.