9 verified, 0 failed, 0 observed risk, 1 not checked, on 22 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
No x402 catalogue entry we hold names an address this server takes payment at, so we cannot attribute any income to it. That is a gap in what we can attribute, not evidence that it earns nothing.
84 tools on the last day the list was read, fingerprint 8545f9cdd7fe685b2d0.
Run the Strategy Engine route in one call. Use it FIRST whenever someone asks to build or make a strategy and names no signals -- 'build me a strategy', 'build me a BTC strategy on 1h', 'make me something for ETH'. Give the asset, and the candle size only when they named one. The server reads the 180-day regime, searches the engine's completed runs once with the agreed floors (more than 10 trades, Sharpe at least 1, IRR at least 10%, beats benchmarks) in that regime, keeps the runs whose entry the regime admits, picks one at random, saves it from its own run and backtests it on recent data ending today, over a window its candle size sets: 5m 1 month, 15m 2 months, 30m 3 months, 1h 4 months, 4h 12 months, 1d 12 months (a month is 30 days). Returns as soon as the backtest is submitted; when running, show the saved strategy and invite the person to check results shortly using get_backtest with the returned backtest_id. Do not submit another backtest. Do not pass filters, a regime or dates: they are fixed. When nothing fits it answers with outcome no_match and saves and spends nothing. A fresh build selects its market automatically; do not ask for a venue or quote. It does not search the marketplace. [Access: pay 0.10 USDC via x402 (PAYMENT-SIGNATURE header) OR authenticate with an API key. An x402-capable client will auto-pay; API-key clients pay nothing per call.]
changes stateadditive onlyreaches outside servicesas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| asset | string | yes | Asset symbol, e.g. BTC or ETH. |
| candle_size | string | no | Duration of one candle, e.g. 1h or 1d. |
No agent registration names this server; we probe it on our own list.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 5 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-22 | Answered | 14 | hourly runs |
| 2026-11-21 | Some runs failed | 23 | hourly runs |
| 2026-11-20 | Answered | 24 | hourly runs |
| 2026-11-19 | Answered | 23 | hourly runs |
| 2026-11-18 | Answered | 24 | hourly runs |
| 2026-11-17 | Answered | 23 | hourly runs |
| 2026-11-16 | Answered | 24 | hourly runs |
| 2026-11-15 | Answered | 23 | hourly runs |
| 2026-11-14 | Some runs failed | 24 | hourly runs |
| 2026-11-13 | Answered | 23 | hourly runs |
| 2026-11-12 | Answered | 23 | hourly runs |
| 2026-11-11 | Answered | 23 | hourly runs |
| 2026-11-10 | Answered | 24 | hourly runs |
| 2026-11-09 | Some runs failed | 23 | hourly runs |
| 2026-11-08 | Answered | 24 | hourly runs |
| 2026-11-07 | Answered | 18 | hourly runs |
| 2026-11-06 | Answered | 23 | hourly runs |
| 2026-11-05 | Answered | 4 | hourly runs |
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-22 | 165 | 260 | 14 |
| 2026-11-21 | 171 | 232 | 22 |
| 2026-11-20 | 172 | 234 | 24 |
| 2026-11-19 | 172 | 291 | 23 |
| 2026-11-18 | 171 | 250 | 24 |
| 2026-11-17 | 172 | 247 | 23 |
| 2026-11-16 | 170 | 253 | 24 |
| 2026-11-15 | 170 | 231 | 23 |
| 2026-11-14 | 172 | 230 | 23 |
| 2026-11-13 | 166 | 238 | 23 |
| 2026-11-12 | 166 | 269 | 23 |
| 2026-11-11 | 171 | 253 | 23 |
| 2026-11-10 | 168 | 242 | 24 |
| 2026-11-09 | 174 | 381 | 22 |
| 2026-11-08 | 164 | 230 | 24 |
| 2026-11-07 | 162 | 234 | 18 |
| 2026-11-06 | 173 | 236 | 23 |
| 2026-11-05 | 169 | 234 | 4 |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 22 November 2026, 13:38 UTC: 5 of 5 requests answered, p50 257 ms, p95 534 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-22 14:00 (now) | — | 0 | 0 |
| 2026-11-22 13:00 | 257 | 1 | 0 |
| 2026-11-22 12:00 | 160 | 1 | 0 |
| 2026-11-22 11:00 | 164 | 1 | 0 |
| 2026-11-22 10:00 | 165 | 1 | 0 |
| 2026-11-22 09:00 | 225 | 1 | 0 |
| 2026-11-22 08:00 | 263 | 1 | 0 |
| 2026-11-22 07:00 | 181 | 1 | 0 |
| 2026-11-22 06:00 | 159 | 1 | 0 |
| 2026-11-22 05:00 | 161 | 1 | 0 |
| 2026-11-22 04:00 | 166 | 1 | 0 |
| 2026-11-22 03:00 | 172 | 1 | 0 |
| 2026-11-22 02:00 | 196 | 1 | 0 |
| 2026-11-22 01:00 | 162 | 1 | 0 |
| 2026-11-22 00:00 | 164 | 1 | 0 |
| 2026-11-21 23:00 | 172 | 1 | 0 |
| 2026-11-21 22:00 | 194 | 1 | 0 |
| 2026-11-21 21:00 | 164 | 1 | 0 |
| 2026-11-21 20:00 | 160 | 1 | 0 |
| 2026-11-21 19:00 | 162 | 1 | 0 |
| 2026-11-21 18:00 | 174 | 1 | 0 |
| 2026-11-21 17:00 | 237 | 1 | 0 |
| 2026-11-21 16:00 | 252 | 1 | 0 |
| 2026-11-21 15:00 | — | 1 | 1 |