Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-27 · today
vet402Back to the registerMethodology

coverbureau.com/mcp

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://coverbureau.com/mcp
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x4d664fd43ab055dfcb3582afd9d9152d8b6bc29a
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-09-12 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-09-122026-09-27
Figure 1. Probe timeline, last 20 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-27 04:40 UTCPOSTfail400200 msno_402
2026-09-26 13:40 UTCPOSTfail400179 msno_402
2026-09-25 16:40 UTCPOSTfail400102 msno_402
2026-09-24 22:40 UTCPOSTfail400113 msno_402
2026-09-24 04:40 UTCPOSTfail400282 msno_402
2026-09-23 13:40 UTCPOSTfail400281 msno_402
2026-09-22 16:40 UTCPOSTfail400186 msno_402
2026-09-21 22:40 UTCPOSTfail400112 msno_402
2026-09-21 04:40 UTCPOSTfail400509 msno_402
2026-09-20 13:40 UTCPOSTfail4002143 msno_402
2026-09-19 16:40 UTCPOSTfail400132 msno_402
2026-09-19 04:40 UTCPOSTfail400166 msno_402
2026-09-18 13:40 UTCPOSTfail400829 msno_402
2026-09-17 16:40 UTCPOSTfail400600 msno_402
2026-09-16 22:40 UTCPOSTfail400310 msno_402
2026-09-16 13:40 UTCPOSTfail400234 msno_402
2026-09-15 13:40 UTCPOSTfail400111 msno_402
2026-09-14 22:40 UTCPOSTfail400242 msno_402
2026-09-13 11:24 UTCPOSTfail400225 msno_402
2026-09-12 11:24 UTCPOSTfail400225 msno_402

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

4.Catalog listing events

No listing changes observed.

unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.

5.Dispute this record

Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.