_ registry / mcp http-sse · checked 2h ago

Autrady

https://autrady.com

Registry code: aa5b05b1350384d4

api record

Autrady audits trading strategies. This public server needs no sign-in and has two tools. luck_check: given a claimed track record (average monthly return, typical monthly swing, months of results, versions tried), it says how often pure luck produces a record that good and how many months a real edge of that size needs before anyone can tell it apart from luck. If the user does not know how many versions were tried, assume at least 10 and say so. explain_audit: what a full audit of the actual signals checks, what it costs and where to start. Audits of a user's own signal files run in the web…

endpoint
https://autrady.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Autrady live?
Yes — it answered the hub's last check (checked 2h ago). It answered 91% of checks over the last 30 days.
Is Autrady free to use?
Yes — the hub reached it with no key and no payment.
What tools does Autrady have?
2 tools: luck_check, explain_audit.
Is Autrady safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
90.5%

90 days 91%· all time 91%

latency
606ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 167 checks · signed record
  • degraded → live
  • live → degraded· HTTP 530
  • degraded → live
  • live → degraded· HTTP 530
  • degraded → live
_ what it is for
used for
  • check if trading strategy performance is due to luck
  • understand full audit process for trading signals
  • get pricing for trading strategy audits
takes → gives
data → text
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • explain_audit reads open 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • luck_check reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "averageMonthlyReturnPercent",
        "monthlySwingPercent",
        "months"
      ],
      "properties": {
        "months": {
          "type": "integer",
          "description": "Months of results in the track record, from 2 to 1200."
        },
        "versionsTried": {
          "type": "integer",
          "default": 10,
          "description": "How many versions or variations were tried before this one was picked. If unknown, use 10."
        },
        "monthlySwingPercent": {
          "type": "number",
          "description": "Typical monthly swing: the standard deviation of monthly returns, in percent. Stock strategies usually sit between 4 and 8."
        },
        "averageMonthlyReturnPercent": {
          "type": "number",
          "description": "Average return per month, in percent. 1.5 means +1.5% a month."
        }
      }
    }
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id aa5b05b1350384d4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa5b05b1350384d4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/aa5b05b1350384d4/badge.svg)](https://brick.blue/agent/aa5b05b1350384d4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.