mcp.barker.money/barker_vault_position
1.Catalog declaration
| Resource URL | https://mcp.barker.money/barker_vault_position |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:196 |
| Receiving address | 0x83f15f5bea445109e255ab82622fbdfecd1e4c9f |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-09-12 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-11 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-11 16:40 UTC | GET | fail | 400 | 1077 ms | no_402HTTP 400 instead of 402 to an unpaid GET. |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 434 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 1354 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 1107 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 1103 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 1172 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 1104 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 1053 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 1032 ms | — |
| 2026-09-06 17:40 UTC | GET | pass | 402 | 1055 ms | — |
| 2026-09-06 05:40 UTC | GET | pass | 402 | 1033 ms | — |
| 2026-09-05 17:40 UTC | GET | pass | 402 | 1180 ms | — |
| 2026-09-05 05:40 UTC | GET | pass | 402 | 1321 ms | — |
| 2026-09-04 17:40 UTC | GET | pass | 402 | 1065 ms | — |
| 2026-09-04 05:40 UTC | GET | pass | 402 | 1057 ms | — |
| 2026-09-03 17:40 UTC | GET | pass | 402 | 1526 ms | — |
| 2026-09-03 05:40 UTC | GET | pass | 402 | 1034 ms | — |
| 2026-09-02 17:40 UTC | GET | pass | 402 | 1114 ms | — |
| 2026-09-02 05:40 UTC | GET | pass | 402 | 1052 ms | — |
| 2026-09-01 23:40 UTC | GET | pass | 402 | 1070 ms | — |
| 2026-08-25 10:47 UTC | GET | pass | 402 | 1115 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-25 12:542026-08-25 12:54 UTC | settled (amount + payee) | 200 | 0xc1a34fab…df87 | 3276 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/8bded24d-bc3f-4651-a600-af330e3d02dc)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-12 | 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.