# Autrady

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

- name: com.autrady/strategy-audits
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 80/100 flags: no-repository
- quality: 96/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.autrady%2Fstrategy-audits
- tools: https://api.protogrid.dev/v1/servers/com.autrady%2Fstrategy-audits/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "strategy-audits": {
      "type": "http",
      "url": "https://autrady.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 93
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-82% +updated-25d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 96/100 (strong)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 443 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 443 tokens to load them all
- tool set hash: 079e2fb9afead13ded4050a4ff6dca04
- badge: [![protogrid quality](https://protogrid.dev/badge/com.autrady/strategy-audits.svg)](https://protogrid.dev/servers/com.autrady/strategy-audits)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://autrady.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.82191783)

## Packages

_none_

## Tools (2)

- `explain_audit`: 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.
- `luck_check`: 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.