Endpoint Diligence MCP Server

by x402supply Your server? Claim it

answering

Endpoint Diligence is answering right now. Last checked 15 min ago. It exposes 3 tools.

Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

177 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Endpoint Diligence every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add endpoint-diligence --transport http https://diligence.x402supply.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "endpoint-diligence": {
      "url": "https://diligence.x402supply.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.endpoint-diligence]
url = "https://diligence.x402supply.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "endpoint-diligence": {
      "url": "https://diligence.x402supply.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "endpoint-diligence": {
      "url": "https://diligence.x402supply.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compare

compare_price

Compares an x402 endpoint's price (or a given price/category pair) against market percentiles from our daily radar snapshot of the x402 ecosystem.

endpoint

check_endpoint

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.

reseller

reseller_check

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.

Endpoints

URL	Transport	State	Latency	Checked
https://diligence.x402supply.com/mcp	streamable-http	answering	161 ms	15 min ago

Alternatives to Endpoint Diligence

same job, measured the same way

Deadchannel

by plus8bit

Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.005 in USDC.

35 installs/wk local only

Mizan

by higgsfield-mizan-bazar

Check an x402 endpoint before your agent pays it: avoid / caution / ok, proven on-chain.

3 tools answering

X402 Trust MCP

by jonasfuchss

Trust & reliability data for x402 endpoints before your agent pays them.

707 installs/wk local only

Pulsefeed X402

by nikolife2016

Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.

76 installs/wk 11 tools answering

Provenance MCP

by apeirontrade

Wash-traffic risk checks for Algorand x402 endpoints before your agent trusts or pays them.

36 installs/wk local only

YouTube data for agents

by fetcher-youtube

15 YouTube endpoints. Pay per call in USDC via x402.

17 tools answering

App Store data for agents

by fetcher-appstore

9 App Store endpoints. Pay per call in USDC via x402.

11 tools answering

Yelp data for agents

by fetcher-yelp

4 Yelp endpoints. Pay per call in USDC via x402.

6 tools answering

Endpoint Diligence — questions

Answers built from our own checks of this server.

What can Endpoint Diligence do?

It exposes 3 tools, read directly from the server on our last check. Among them: check_endpoint, compare_price, reseller_check. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Endpoint Diligence working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 177 ms. The bar chart above shows every period we have measured.

How do I connect Endpoint Diligence?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Endpoint Diligence need an API key?

No. Endpoint Diligence completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Endpoint Diligence?

It answers our handshake in 177 ms on average, which is faster than 71% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.