Search / com.autrady/strategy-audits
Is a trading strategy's track record luck? Free luck check, plus what a full strategy audit checks.
v1.0.0 · active · website · descriptor JSON · versions
protogrid{
"mcpServers": {
"strategy-audits": {
"type": "http",
"url": "https://autrady.com/mcp"
}
}
}claude mcp add --transport http strategy-audits https://autrady.com/mcp[mcp_servers.strategy-audits]
url = "https://autrady.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"strategy-audits": {
"type": "remote",
"url": "https://autrady.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"strategy-audits": {
"type": "http",
"url": "https://autrady.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=strategy-audits&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYXV0cmFkeS5jb20vbWNwIn0%3D"
}{
"servers": {
"strategy-audits": {
"type": "http",
"url": "https://autrady.com/mcp"
}
}
}{
"mcpServers": {
"strategy-audits": {
"httpUrl": "https://autrady.com/mcp"
}
}
}extensions:
"strategy-audits":
enabled: true
name: "strategy-audits"
type: streamable_http
uri: "https://autrady.com/mcp"
timeout: 300
protocol.modernsupports 2026-07-28 (server/discover)protocol.statelessanswers without a sessionprotocol.transportstreamable HTTPprotocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every useauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_lengthdescriptions are concisetools.schemasevery tool has an object input schematools.annotations2 of 2 tools declare readOnlyHint or destructiveHinttools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHinttools.token_costabout 443 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website -unreachable(3 failures) +updated-24d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://autrady.com/mcp streamable-http | none | no (3 failures) | 83% | 587 ms | 2026-07-28 | 2026-10-15 |
explain_auditread-only | 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_checkread-only | 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. |
Schemas: list_tools.
{
"name": "com.autrady/strategy-audits",
"title": "Autrady",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://autrady.com/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"websiteUrl": "https://autrady.com",
"description": "Is a trading strategy's track record luck? Free luck check, plus what a full strategy audit checks."
}