mcp server
endpoint-diligence
Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-07-15.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_endpoint(url)- Runs live diligence on an x402-metered endpoint before you pay it: verifies its 402 payment challenge is spec-compliant, checks the price against market baselines, inspects the payTo address on-chain (Base), checks third-party directory presence, and checks basic infra hygiene, and detects possible upstream API resale with evidence-based markup estimates. Returns a 0-100 score, a pass/caution/fail verdict, and per-check evidence. Required: url.
compare_price(url, category, priceUsd)- Compares an x402 endpoint's price (or a given price/category pair) against market percentiles from our daily radar snapshot of the x402 ecosystem.
reseller_check(url, priceUsd, description)- Free possible-reseller preview. Matches an endpoint's live unpaid 402 description/schema, or a supplied description and price, against a dated catalog of well-known upstream APIs and reports confidence, matched signals, and documented markup math without asserting resale as fact.
Last successful function declaration observed on . Source: https://diligence.x402supply.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://diligence.x402supply.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | diligence.x402supply.com | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | diligence.x402supply.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json