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 | 72 | 97 | 12 |
| 2026-11-04 | 90 | 152 | 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.
53 tools on the last day the list was read, fingerprint dcdc622e2bd3dd8252d.
Signed observation of a URL (paid, x402)
PAID: we fetch a URL from OUR vantage point and return a signed, timestamped attestation of what we saw -- hash, byte count, HTTP status and headers, never the body itself. Read it back afterwards for free with attest_read, so the id can be cited to a THIRD PARTY who never paid us and who can verify the signature themselves. A fetch that fails to connect, times out, or is refused for safety is still billed and still signed: the observation is what is sold, not a guaranteed 200. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Solana USDC where offered); call it again with a signed payment in _meta['x402/payment'] to complete it. The receipt comes back in _meta['x402/payment-response']. No account, no API key. Complaints, questions, quote requests, or a service you wish we had: POST /feedback on this host -- free, no account. Every report is read and analysed daily; there is no individual reply.
changes stateadditive onlyclosed worldas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| url | string | yes | An absolute http:// or https:// URL, at most 2048 UTF-8 bytes. The body is never returned to you. |
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 105 ms, p95 119 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-05 12:00 (now) | — | 0 | 0 |
| 2026-11-05 11:00 | 105 | 1 | 0 |
| 2026-11-05 10:00 | 84 | 1 | 0 |
| 2026-11-05 09:00 | 72 | 1 | 0 |
| 2026-11-05 08:00 | 91 | 1 | 0 |
| 2026-11-05 07:00 | 70 | 1 | 0 |
| 2026-11-05 06:00 | 62 | 1 | 0 |
| 2026-11-05 05:00 | 78 | 1 | 0 |
| 2026-11-05 04:00 | 71 | 1 | 0 |
| 2026-11-05 03:00 | 70 | 1 | 0 |
| 2026-11-05 02:00 | 73 | 1 | 0 |
| 2026-11-05 01:00 | 73 | 1 | 0 |
| 2026-11-05 00:00 | 68 | 1 | 0 |
| 2026-11-04 23:00 | 115 | 1 | 0 |
| 2026-11-04 22:00 | 59 | 1 | 0 |
| 2026-11-04 21:00 | 91 | 1 | 0 |
| 2026-11-04 20:00 | 66 | 1 | 0 |
| 2026-11-04 19:00 | 93 | 1 | 0 |
| 2026-11-04 18:00 | 107 | 1 | 0 |
| 2026-11-04 17:00 | 90 | 1 | 0 |
| 2026-11-04 16:00 | 72 | 1 | 0 |
| 2026-11-04 15:00 | 84 | 1 | 0 |
| 2026-11-04 14:00 | 100 | 1 | 0 |
| 2026-11-04 13:00 | 72 | 1 | 0 |