Skip to main content
Glama

Endpoints that contradict their own listing

endpoint_disagreements
Read-onlyIdempotent

WHICH ENDPOINTS CONTRADICT THEIR OWN LISTING: they ask to be paid at an address the catalogue entry they published does not name. This is the one reading here that cannot be reproduced from anywhere else — an uptime checker sees a live endpoint and a catalogue reader sees a published payee, and only holding BOTH shows the contradiction. A disagreement is between two statements by the SAME party, so it is theirs to explain and never ours to resolve, and it is NOT evidence of fraud: a seller may have moved their payee and not relisted. Measured only over endpoints we have knocked on, which is our reach and not the catalogue; comparable is the denominator, because an endpoint that names no payee cannot disagree and is counted neither way. THE COUNTS ARE FREE AND THE LIST IS NOT: items comes back NULL without a plan rather than empty, since an empty list would say we found none. Any SINGLE endpoint is free — test_purchase and list_x402_endpoints both carry its own reading — because that one is reproducible in two requests and because withholding something that can cost a buyer money is not a thing we do.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows once a plan is held. Default 50, capped at 200.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
saysYesThe finding in a sentence, with its denominator.
itemsNoOne per disagreeing endpoint: `resource`, `listedPayee`, `quotedPayee`, `seenAt`. NULL without a plan — never an empty array, which would say we found none.
limitsYesWhat this is measured over and what a disagreement is not.
knockedYesEndpoints we have knocked on at all. The population every other figure here is drawn from.
sellersYesHow many distinct listed payees those belong to. Worth more than the endpoint count: it says whether this is scattered or a few parties contradicting themselves repeatedly.
servingNoOf those, how many answered with a price at the most recent knock.
comparableYesHow many could be compared at all: both the endpoint and its listing named a payee. The DENOMINATOR for `disagreeing`.
notServingNoGone, unreachable or erroring at the most recent knock. A fact about our last look, not a verdict on the seller.
disagreeingYesHow many name a payee their own listing does not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources