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 | 111 | 133 | 12 |
| 2026-11-04 | 116 | 141 | 14 |
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 3e4ac988297f7857a73.
Compare opportunities
Side-by-side comparison of 2–5 opportunities by risk-adjusted score. Pass list_yields opportunities[].id values as poolIds or opportunityIds. Returns ranked list, compact comparison table fields (including protocolSlug for get_protocol_risk), winnerId, and rationale bullets (including when raw APY leader differs from risk-adjusted winner). sourceChainKey is ethereum|base|arbitrum only (unknown → VALIDATION_ERROR; no invented bridge fee). Research only — non-custodial. Example: { "poolIds": ["pool-id-a", "pool-id-b", "pool-id-c"], "horizonDays": 30 }
read-onlyadditive onlysafe to repeatreaches outside servicesas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| poolIds | string[] | no | 2–5 list_yields opportunities[].id values. Example: ["id-a","id-b"]. Alias: opportunityIds. |
| opportunityIds | string[] | no | Alias for poolIds — same list_yields opportunities[].id values. |
| horizonDays | number | no | Holding horizon in days for gas/bridge amortization (default 30). Example: 30 |
| notionalUsd | number | no | Notional USD size for net-yield cost amortization and exitRisk TVL multiples (default 10000). Example: 10000 |
| sourceChainKey | string | no | Agent's current chain for bridge cost estimate: ethereum | base | arbitrum (aliases: eth, ETH, Ethereum, arb, ARB, BASE). Blank/whitespace is VALIDATION_ERROR (omit the field to default). Unknown keys (solana, foo) return VALIDATION_ERROR — no invented bridge fee. |
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 | 14 | 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 121 ms, p95 141 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-05 12:00 (now) | — | 0 | 0 |
| 2026-11-05 11:00 | 121 | 1 | 0 |
| 2026-11-05 10:00 | 101 | 1 | 0 |
| 2026-11-05 09:00 | 105 | 1 | 0 |
| 2026-11-05 08:00 | 129 | 1 | 0 |
| 2026-11-05 07:00 | 98 | 1 | 0 |
| 2026-11-05 06:00 | 105 | 1 | 0 |
| 2026-11-05 05:00 | 116 | 1 | 0 |
| 2026-11-05 04:00 | 111 | 1 | 0 |
| 2026-11-05 03:00 | 112 | 1 | 0 |
| 2026-11-05 02:00 | 114 | 1 | 0 |
| 2026-11-05 01:00 | 108 | 1 | 0 |
| 2026-11-05 00:00 | 119 | 1 | 0 |
| 2026-11-04 23:00 | 116 | 1 | 0 |
| 2026-11-04 22:00 | 129 | 1 | 0 |
| 2026-11-04 21:00 | 108 | 1 | 0 |
| 2026-11-04 20:00 | 115 | 1 | 0 |
| 2026-11-04 19:00 | 97 | 1 | 0 |
| 2026-11-04 18:00 | 95 | 1 | 0 |
| 2026-11-04 17:00 | 116 | 1 | 0 |
| 2026-11-04 16:00 | 133 | 1 | 0 |
| 2026-11-04 15:00 | 106 | 1 | 0 |
| 2026-11-04 14:00 | 113 | 1 | 0 |
| 2026-11-04 13:00 | 126 | 1 | 0 |