Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-30 · 1 day ago
vet402Back to the registerMethodology

api.teardrop.dev/tools/mcp

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.teardrop.dev/tools/mcp#web_search
Sourcecdp_bazaar
Declared methodundeclared
Catalog networkeip155:8453
Receiving address0xf2eec9de86274913f85a8aa6427ad65a9b0bc90a
Declared price (base units)15000
Catalog statusactive
First seen / last seen2026-10-01 01:03 UTC / 2026-10-31 00:07 UTC
Catalog-reported calls / payers (30d)0 / 0

2.Probe history

2026-10-012026-10-30
Figure 1. Probe timeline, last 22 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-10-30 22:40 UTCGETpass402452 ms—
2026-10-29 04:40 UTCGETfail402460 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-27 13:40 UTCGETfail402357 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-25 18:40 UTCGETfail402588 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-23 16:40 UTCGETfail402687 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-22 04:40 UTCGETfail402642 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-20 16:40 UTCGETfail402492 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-18 22:40 UTCGETfail402438 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-17 16:40 UTCGETfail402629 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-16 12:40 UTCGETfail402861 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-14 21:40 UTCGETfail402552 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-13 15:40 UTCGETfail402563 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-12 12:40 UTCGETfail402631 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-11 12:40 UTCGETfail402739 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-10 12:40 UTCGETfail402610 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-08 22:40 UTCGETfail402810 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-07 22:40 UTCGETfail402594 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-06 22:40 UTCGETfail402569 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-06 04:41 UTCGETfail402449 msprice_mismatchDeclared 15000 of 0x8335…2913; the 402 offered 5000 of 0x8335…2913.
2026-10-02 22:40 UTCGETfail406586 msno_402HTTP 406 instead of 402 to an unpaid GET.
2026-10-02 04:40 UTCGETfail406398 msno_402HTTP 406 instead of 402 to an unpaid GET.
2026-10-01 10:30 UTCGETfail406342 msno_402HTTP 406 instead of 402 to an unpaid GET.

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. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-06relisted{"status":"delisted"}{"status":"active"}
2026-10-03delisted{"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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far