api.agentstools.dev/mcp/scan
1.Catalog declaration
| Resource URL | https://api.agentstools.dev/mcp/scan |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xf22e558a00d91ee12a1f50c52186fecb8ddff493 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-18 01:06 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 1811 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 478 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 1860 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 706 ms | — |
| 2026-10-14 15:40 UTC | POST | pass | 402 | 864 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 358 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 845 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 684 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 407 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 429 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 415 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 182 ms | — |
| 2026-10-05 22:40 UTC | POST | pass | 402 | 230 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 2155 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 196 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 216 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 225 ms | — |
| 2026-09-30 10:30 UTC | POST | pass | 402 | 148 ms | — |
| 2026-09-25 10:30 UTC | POST | pass | 402 | 399 ms | — |
| 2026-09-20 11:24 UTC | POST | pass | 402 | 285 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 673 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-10 11:24 UTC | POST | pass | 402 | 257 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 149 ms | — |
| 2026-09-01 23:14 UTC | POST | pass | 402 | 145 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 (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
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 |
|---|---|---|---|---|
| 10-03 06:012026-10-03 06:01 UTC | settled (nonce-bound) | 200 | 0x1c343316…5ece | 1583 ms |
| 10000 units (≈ $0.01 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/6889ca96-1189-4836-a91a-8396cca191b2)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.