Loading
9 verified, 0 failed, 0 observed risk, 1 not checked, on 5 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
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-05 | 55 | 120 | 12 |
| 2026-11-04 | 113 | 191 | 15 |
No x402 catalogue entry names an address this server takes payment at, so what the server itself earns does not pass through a rail we can read.
6 tools on the last day the list was read, fingerprint b0c92a508cd59d676a9.
Return the bottom/top verdict for one crypto symbol (e.g. BTC-USD). zone = strong_buy|buy|sell|neutral, score -100..+100 (bottom>0, top<0), with daily/weekly/monthly breakdown. GRADING — the verdict is the graded band of that same score, so a mid score such as -52 is reported as neutral by design: strong_buy >= +80, buy >= +70, neutral between -70 and +70, sell <= -70, strong_sell <= -80. Informational only, not financial advice. PAY: $0.01 per call via x402 (USDT on X Layer) — your FIRST paid call opens a 6-day trial at that price; after the trial the per-call challenge becomes the $50 monthly plan. No account, no signup, no commitment; retry with the PAYMENT-SIGNATURE header when you get the 402 challenge. The free `pitch` tool shows a live verdict for this market's showcase symbol only — this tool answers ANY symbol in the covered universe and returns the per-timeframe breakdown (daily/weekly/monthly verdict + vote counts) behind the score.
| Name | Type | Required | Description |
|---|---|---|---|
| symbol | string | yes | Crypto symbol, e.g. BTC-USD, ETH-USD, or BTCUSDT |
1 agent registrations name this server. A registration is a claim by whoever wrote it, which is why the server itself is asked.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 4 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-05 | Answered | 12 | hourly runs |
| 2026-11-04 | Answered | 15 | hourly runs |
| 2026-11-03 | Answered | 0 | daily probe |
| 2026-11-02 | Answered | 0 | daily probe |
| 2026-11-01 | Answered | 0 | daily probe |
| 2026-10-31 | Answered | 0 | daily probe |
| 2026-10-30 | Answered | 0 | daily probe |
| 2026-10-29 | Answered | 0 | daily probe |
| 2026-10-28 | Answered | 0 | daily probe |
| 2026-10-27 | Answered | 0 | daily probe |
| 2026-10-26 | Answered | 0 | daily probe |
| 2026-10-25 | Answered | 0 | daily probe |
| 2026-10-24 | Answered | 0 | daily probe |
| 2026-10-23 | Answered | 0 | daily probe |
| 2026-10-22 | Answered | 0 | daily probe |
| 2026-10-21 | Answered | 0 | daily probe |
| 2026-10-20 | Answered | 0 | daily probe |
| 2026-10-19 | No answer | 0 | daily probe |
| 2026-10-18 | Answered | 0 | daily probe |
| 2026-10-17 | Answered | 0 | daily probe |
| 2026-10-16 | Answered | 0 | daily probe |
| 2026-10-15 | No answer | 0 | daily probe |
| 2026-10-14 | Answered | 0 | daily probe |
| 2026-10-13 | Answered | 0 | daily probe |
| 2026-10-12 | Answered | 0 | daily probe |
| 2026-10-11 | Answered | 0 | daily probe |
| 2026-10-10 | Answered | 0 | daily probe |
| 2026-10-07 | Answered | 0 | daily probe |
| 2026-10-06 | Answered | 0 | daily probe |
| 2026-10-04 | Answered | 0 | daily probe |
| 2026-10-03 | Answered | 0 | daily probe |
| 2026-10-02 | Answered | 0 | daily probe |
| 2026-10-01 | Answered | 0 | daily probe |
| 2026-09-30 | Answered | 0 | daily probe |
| 2026-09-29 | Answered | 0 | daily probe |
| 2026-09-28 | Answered | 0 | daily probe |
| 2026-09-27 | Answered | 0 | daily probe |
| 2026-09-26 | Answered | 0 | daily probe |
| 2026-09-25 | Answered | 0 | daily probe |
| 2026-09-24 | Answered | 0 | daily probe |
| 2026-09-23 | Answered | 0 | daily probe |
| 2026-09-22 | Answered | 0 | daily probe |
| 2026-09-21 | Answered | 0 | daily probe |
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 5 November 2026, 11:36 UTC: 5 of 5 requests answered, p50 75 ms, p95 203 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-05 12:00 (now) | — | 0 | 0 |
| 2026-11-05 11:00 | 75 | 1 | 0 |
| 2026-11-05 10:00 | 48 | 1 | 0 |
| 2026-11-05 09:00 | 115 | 1 | 0 |
| 2026-11-05 08:00 | 55 | 1 | 0 |
| 2026-11-05 07:00 | 85 | 1 | 0 |
| 2026-11-05 06:00 | 59 | 1 | 0 |
| 2026-11-05 05:00 | 60 | 1 | 0 |
| 2026-11-05 04:00 | 54 | 1 | 0 |
| 2026-11-05 03:00 | 55 | 1 | 0 |
| 2026-11-05 02:00 | 55 | 1 | 0 |
| 2026-11-05 01:00 | 79 | 1 | 0 |
| 2026-11-05 00:00 | 52 | 1 | 0 |
| 2026-11-04 23:00 | 50 | 1 | 0 |
| 2026-11-04 22:00 | 113 | 1 | 0 |
| 2026-11-04 21:00 | 106 | 1 | 0 |
| 2026-11-04 20:00 | 99 | 1 | 0 |
| 2026-11-04 19:00 | 92 | 1 | 0 |
| 2026-11-04 18:00 | 100 | 1 | 0 |
| 2026-11-04 17:00 | 175 | 1 | 0 |
| 2026-11-04 16:00 | 144 | 1 | 0 |
| 2026-11-04 15:00 | 72 | 1 | 0 |
| 2026-11-04 14:00 | 54 | 1 | 0 |
| 2026-11-04 13:00 | 127 | 1 | 0 |