mcp.barker.money/barker_market_overview
1.Catalog declaration
| Resource URL | https://mcp.barker.money/barker_market_overview |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:196 |
| Receiving address | 0x83f15f5bea445109e255ab82622fbdfecd1e4c9f |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 46 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 10:30 UTC | GET | pass | 402 | 1079 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 1293 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 1120 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 1260 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 2664 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 1041 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 921 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 1068 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 1306 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 972 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 1282 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 1126 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 1183 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 994 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 1022 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 1016 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 1019 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 1211 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 1171 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 1195 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 1145 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 1074 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 1269 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 1278 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 1263 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 999 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 1171 ms | — |
| 2026-08-24 11:11 UTC | GET | pass | 402 | 278 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 08-24 23:382026-08-24 23:38 UTC | settled (amount + payee) | 200 | 0xa91e18d3…3c5b | 3582 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/af251d47-15b2-4253-ba6c-df1c608f9d46)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-07 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-27 | delisted | {"status":"active"} | {"status":"delisted"} |
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.