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 | 564 | 711 | 12 |
| 2026-11-04 | 607 | 824 | 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.
2 tools on the last day the list was read, fingerprint fe1f70f755ed96802a5.
Runs JavaScript code to interact with the Coingecko API. You are a skilled TypeScript programmer writing code to interface with the service. Define an async function named "run" that takes a single parameter of an initialized SDK client and it will be run. For example: ``` async function run(client) { const price = await client.simple.price.get({ vs_currencies: 'usd', ids: 'bitcoin' }); } ``` You will be returned anything that your function returns, plus the results of any console.log statements. Do not add try-catch blocks for single API calls. The tool will handle errors for you. Do not add comments unless necessary for generating better code. Code will run in a container, and cannot interact with the network outside of the given SDK client. Variables will not persist between calls, so make sure to return or log any data you might need later. Remember that you are writing TypeScript code, so you need to be careful with your types. Always type dynamic key-value stores explicitly as Record<string, YourValueType> instead of {}.
read-onlyas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| code | string | yes | Code to execute. |
| intent | string | no | Task you are trying to perform. Used for improving the service. |
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 | Answered | 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 667 ms, p95 687 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-05 12:00 (now) | — | 0 | 0 |
| 2026-11-05 11:00 | 667 | 1 | 0 |
| 2026-11-05 10:00 | 716 | 1 | 0 |
| 2026-11-05 09:00 | 567 | 1 | 0 |
| 2026-11-05 08:00 | 621 | 1 | 0 |
| 2026-11-05 07:00 | 630 | 1 | 0 |
| 2026-11-05 06:00 | 539 | 1 | 0 |
| 2026-11-05 05:00 | 649 | 1 | 0 |
| 2026-11-05 04:00 | 484 | 1 | 0 |
| 2026-11-05 03:00 | 539 | 1 | 0 |
| 2026-11-05 02:00 | 564 | 1 | 0 |
| 2026-11-05 01:00 | 564 | 1 | 0 |
| 2026-11-05 00:00 | 508 | 1 | 0 |
| 2026-11-04 23:00 | 607 | 1 | 0 |
| 2026-11-04 22:00 | 517 | 1 | 0 |
| 2026-11-04 21:00 | 553 | 1 | 0 |
| 2026-11-04 20:00 | 807 | 1 | 0 |
| 2026-11-04 19:00 | 609 | 1 | 0 |
| 2026-11-04 18:00 | 750 | 1 | 0 |
| 2026-11-04 17:00 | 676 | 1 | 0 |
| 2026-11-04 16:00 | 548 | 1 | 0 |
| 2026-11-04 15:00 | 616 | 1 | 0 |
| 2026-11-04 14:00 | 555 | 1 | 0 |
| 2026-11-04 13:00 | 598 | 1 | 0 |