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 | 215 | 285 | 12 |
| 2026-11-04 | 267 | 398 | 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.
44 tools on the last day the list was read, fingerprint 693d98d560143306e83.
Accept a standing offer on an ENS name you own. Returns unsigned Seaport fulfillOrder() calldata. When you submit this transaction, Seaport atomically: - Pulls the offered WETH from the buyer's wallet - Transfers the ENS name from your wallet to the buyer - Pays the fees the offer was signed with out of the WETH you receive You receive the offer amount minus those fees; the response states both, read from the signed offer. The buyer needs a live WETH balance and allowance — if either is missing the tx will revert; you'll have signed but the chain won't execute. A bid settles the UNWRAPPED name: if your name is wrapped, unwrap it first (unwrap_name), then accept. Before accepting: Seaport moves the name and the fee itself (no conduit), so you must have approved Seaport on the BaseRegistrar — use approve_operator if needed — and granted each WETH allowance listed in the response's approvals. Use get_name_details to see the offer hash and confirm the highest offer. ENS v2 names: the offer names the name's exact current token on the ENS v2 registry, and you must hold every role on the name alone. Approve Seaport on the ENS v2 registry (the response's nftApproval says whether you have). If any role on the name changed since the offer was made, it can no longer be accepted and the bidder is asked to sign it again.
changes statemay destroy or overwriteas the server describes it; we do not call tools
| Name | Type | Required | Description |
|---|---|---|---|
| orderHash | string | yes | Seaport order hash of the buyer's offer to accept |
| walletAddress | string | yes | Your wallet address (the seller). Must own the ENS name in the offer. |
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 | No answer | 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 249 ms, p95 336 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-05 12:00 (now) | — | 0 | 0 |
| 2026-11-05 11:00 | 249 | 1 | 0 |
| 2026-11-05 10:00 | 256 | 1 | 0 |
| 2026-11-05 09:00 | 246 | 1 | 0 |
| 2026-11-05 08:00 | 238 | 1 | 0 |
| 2026-11-05 07:00 | 194 | 1 | 0 |
| 2026-11-05 06:00 | 218 | 1 | 0 |
| 2026-11-05 05:00 | 204 | 1 | 0 |
| 2026-11-05 04:00 | 203 | 1 | 0 |
| 2026-11-05 03:00 | 215 | 1 | 0 |
| 2026-11-05 02:00 | 203 | 1 | 0 |
| 2026-11-05 01:00 | 222 | 1 | 0 |
| 2026-11-05 00:00 | 214 | 1 | 0 |
| 2026-11-04 23:00 | 240 | 1 | 0 |
| 2026-11-04 22:00 | 233 | 1 | 0 |
| 2026-11-04 21:00 | 275 | 1 | 0 |
| 2026-11-04 20:00 | 336 | 1 | 0 |
| 2026-11-04 19:00 | 260 | 1 | 0 |
| 2026-11-04 18:00 | 308 | 1 | 0 |
| 2026-11-04 17:00 | 285 | 1 | 0 |
| 2026-11-04 16:00 | 251 | 1 | 0 |
| 2026-11-04 15:00 | 269 | 1 | 0 |
| 2026-11-04 14:00 | 259 | 1 | 0 |
| 2026-11-04 13:00 | 276 | 1 | 0 |