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.
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-22 | Answered | 14 | hourly runs |
| 2026-11-21 | Answered | 23 | hourly runs |
| 2026-11-20 | Answered | 24 | hourly runs |
| 2026-11-19 | Answered | 23 | hourly runs |
| 2026-11-18 | Some runs failed | 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 | 24 | 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 |
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 | 153 | 334 | 14 |
| 2026-11-21 | 147 | 366 | 23 |
| 2026-11-20 | 129 | 397 | 24 |
| 2026-11-19 | 146 | 325 | 23 |
| 2026-11-18 | 166 | 316 | 23 |
| 2026-11-17 | 158 | 325 | 23 |
| 2026-11-16 | 149 | 407 | 24 |
| 2026-11-15 | 154 | 301 | 23 |
| 2026-11-14 | 141 | 373 | 23 |
| 2026-11-13 | 135 | 388 | 23 |
| 2026-11-12 | 136 | 380 | 23 |
| 2026-11-11 | 140 | 259 | 23 |
| 2026-11-10 | 131 | 392 | 24 |
| 2026-11-09 | 143 | 367 | 22 |
| 2026-11-08 | 152 | 285 | 24 |
| 2026-11-07 | 160 | 330 | 18 |
| 2026-11-06 | 138 | 336 | 23 |
| 2026-11-05 | 152 | 250 | 24 |
| 2026-11-04 | 146 | 352 | 15 |
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 162 ms, p95 329 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-22 14:00 (now) | — | 0 | 0 |
| 2026-11-22 13:00 | 162 | 1 | 0 |
| 2026-11-22 12:00 | 143 | 1 | 0 |
| 2026-11-22 11:00 | 138 | 1 | 0 |
| 2026-11-22 10:00 | 167 | 1 | 0 |
| 2026-11-22 09:00 | 162 | 1 | 0 |
| 2026-11-22 08:00 | 202 | 1 | 0 |
| 2026-11-22 07:00 | 139 | 1 | 0 |
| 2026-11-22 06:00 | 211 | 1 | 0 |
| 2026-11-22 05:00 | 136 | 1 | 0 |
| 2026-11-22 04:00 | 180 | 1 | 0 |
| 2026-11-22 03:00 | 153 | 1 | 0 |
| 2026-11-22 02:00 | 142 | 1 | 0 |
| 2026-11-22 01:00 | 176 | 1 | 0 |
| 2026-11-22 00:00 | 150 | 1 | 0 |
| 2026-11-21 23:00 | 145 | 1 | 0 |
| 2026-11-21 22:00 | 165 | 1 | 0 |
| 2026-11-21 21:00 | 151 | 1 | 0 |
| 2026-11-21 20:00 | 134 | 1 | 0 |
| 2026-11-21 19:00 | 147 | 1 | 0 |
| 2026-11-21 18:00 | 191 | 1 | 0 |
| 2026-11-21 17:00 | 212 | 1 | 0 |
| 2026-11-21 16:00 | 157 | 1 | 0 |
| 2026-11-21 15:00 | 167 | 1 | 0 |
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.
1 tools on the last day the list was read, fingerprint 9e99bd5577e4eb52853.
Clarity OS
Use Clarity OS when a person needs help making sense of a difficult moment—such as overthinking, emotional activation, uncertainty, decision friction, conflicting priorities, a repeating pattern, or a difficult conversation. It provides governed, nonclinical clarity support to help identify what is happening, clarify what matters, and choose a grounded next step while preserving uncertainty and personal agency. It may return protective safety routing when appropriate. Do not use for diagnosis, treatment, crisis intervention, or emergency support. Provide the person’s situation in `user_text`.
read-onlyadditive onlysafe to repeatclosed worldas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| user_text | string | yes | Required. The person’s current message or situation, preserved as provided. Include enough context to understand the moment; do not add facts the person did not provide. |
| explicit_request | string | no | Optional. The specific help or clarification the person explicitly requested. Omit when no explicit request was stated; do not infer one. |
| safety_evidence | object | no | Optional. Structured safety facts directly provided by the person or established by the caller. Omit unsupported fields; never manufacture safety evidence. |
| capacity_signals | object | no | Optional. Structured, directly supported signals about current attention, readiness, or ability to engage. Omit rather than infer. |
| emotions | string[] | no | Optional emotional-state labels supported by the person’s language, such as anxiety, worry, frustration, or uncertainty. These are provisional matching hints; omit them rather than guess. |
| topic_tags | string[] | no | Optional concise topics supported by the situation. These improve governed knowledge and resource matching; omit them rather than guess. |
| pattern_refs | string[] | no | Optional supported pattern labels, such as overthinking loop or anxiety pattern. These improve matching and are not required. |
| requested_resource | string | no | Optional. A governed HGICG resource identifier only when a specific resource is requested. This does not grant access; resource access remains separately governed. |
2 agent registrations name this server. A registration is a claim by whoever wrote it, which is why the server itself is asked.