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 | 182 | 554 | 12 |
| 2026-11-04 | 182 | 585 | 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.
18 tools on the last day the list was read, fingerprint c1b66aa91391a85284f.
Create Agent Fiat Order
Create a fiat payout from an agent's balance to a recipient. Supports mobile money, paybill, buy goods, and bank transfer using type-specific fields. Requires the agent_id returned from register_agent.
changes stateadditive onlyas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| agent_id | string | yes | ID of the agent returned from register_agent |
| amount | number | yes | Fiat amount to send e.g. 100, 5000 |
| currency_code | string | yes | Currency code e.g. KES, UGX, NGN |
| type | string | yes | Payment type to determine which fields are required |
| shortcode | string | no | Phone number, paybill, or till number. Required for type=mobile, paybill, or buy_goods |
| mobile_network | string | no | Mobile network e.g. mpesa, airtel, mtn. Required for type=mobile |
| bank_code | string | no | Bank code or swift code. Required for type=bank_transfer |
| account_number | string | no | Destination account number. Required for type=paybill or bank_transfer |
| account_name | string | no | Account holder name. Required for type=bank_transfer |
| narration | string | no | Payment narration for bank transfers |
4 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 178 ms, p95 554 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-05 12:00 (now) | — | 0 | 0 |
| 2026-11-05 11:00 | 178 | 1 | 0 |
| 2026-11-05 10:00 | 180 | 1 | 0 |
| 2026-11-05 09:00 | 182 | 1 | 0 |
| 2026-11-05 08:00 | 172 | 1 | 0 |
| 2026-11-05 07:00 | 188 | 1 | 0 |
| 2026-11-05 06:00 | 178 | 1 | 0 |
| 2026-11-05 05:00 | 187 | 1 | 0 |
| 2026-11-05 04:00 | 183 | 1 | 0 |
| 2026-11-05 03:00 | 189 | 1 | 0 |
| 2026-11-05 02:00 | 185 | 1 | 0 |
| 2026-11-05 01:00 | 177 | 1 | 0 |
| 2026-11-05 00:00 | 187 | 1 | 0 |
| 2026-11-04 23:00 | 196 | 1 | 0 |
| 2026-11-04 22:00 | 185 | 1 | 0 |
| 2026-11-04 21:00 | 181 | 1 | 0 |
| 2026-11-04 20:00 | 182 | 1 | 0 |
| 2026-11-04 19:00 | 182 | 1 | 0 |
| 2026-11-04 18:00 | 178 | 1 | 0 |
| 2026-11-04 17:00 | 175 | 1 | 0 |
| 2026-11-04 16:00 | 198 | 1 | 0 |
| 2026-11-04 15:00 | 184 | 1 | 0 |
| 2026-11-04 14:00 | 184 | 1 | 0 |
| 2026-11-04 13:00 | 179 | 1 | 0 |