Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.digitalweb33333-creator/x402-endpoints

REMOTE · X402-ENDPOINTS.ONRENDER.COM · SCANNED OCT 4

x402 paid API tools for AI agents on Base: EU/global registries, crypto, wallet & agent trust.

0 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 11933 tokens (~229/item across 52 items; 52 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 52 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 53 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.digitalweb33333-creator/x402-endpoints MCP server?

io.github.digitalweb33333-creator/x402-endpoints is a hosted endpoint at https://x402-endpoints.onrender.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · x402-endpoints.onrender.com

# add to Claude Code
claude mcp add --transport http digitalweb33333-creator-x402-endpoints 'https://x402-endpoints.onrender.com/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "digitalweb33333-creator-x402-endpoints": {
      "url": "https://x402-endpoints.onrender.com/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "digitalweb33333-creator-x402-endpoints": {
      "type": "http",
      "url": "https://x402-endpoints.onrender.com/mcp/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.digitalweb33333-creator-x402-endpoints]
url = "https://x402-endpoints.onrender.com/mcp/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "digitalweb33333-creator-x402-endpoints": {
      "type": "remote",
      "url": "https://x402-endpoints.onrender.com/mcp/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add digitalweb33333-creator-x402-endpoints --url 'https://x402-endpoints.onrender.com/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  digitalweb33333-creator-x402-endpoints:
    url: "https://x402-endpoints.onrender.com/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "digitalweb33333-creator-x402-endpoints": {
      "Transport": "http",
      "Url": "https://x402-endpoints.onrender.com/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add digitalweb33333-creator-x402-endpoints -t streamable-http -u 'https://x402-endpoints.onrender.com/mcp/'
// mcp.json
{
  "mcpServers": {
    "digitalweb33333-creator-x402-endpoints": {
      "type": "http",
      "url": "https://x402-endpoints.onrender.com/mcp/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Oct 2026 · Probed https://x402-endpoints.onrender.com/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 6eb1e3fe7d0631ea1337bfa4a321c137
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of x402-endpoints.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://x402-endpoints.onrender.com/mcp/ Verified 200
http (plaintext) http://x402-endpoints.onrender.com/mcp/ HTTPS enforced 301 https://x402-endpoints.onrender.com/mcp/
MCP tools · 52 exposed · ~11,865 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
x402_seller_audit ~271

Deep audit of an x402/ACP seller before trusting it: give a seller wallet or domain and get a full report — on-chain settlement reputation (settlements, unique counterparties, wash-trade/sybil, OFAC), the seller's advertised endpoints (from its /.well-known/x402.json), on-chain liveness, web reputation and red flags — fused into a TRUSTED/CAUTION/AVOID verdict with a signed, offline-verifiable receipt. Deeper than a pass/fail badge: the full seller due-diligence dossier for agentic payments. Price: $0.50 per call (x402 payment, USDC on Base mainnet). Deep x402 seller audit: on-chain settlement reputation (wash-trade/sybil/OFAC) + advertised endpoints from its /.well-known/x402.json + on-chain liveness + web reputation fused into TRUSTED/CAUTION/AVOID with a signed receipt. Deeper than a pass/fail badge. Input: seller wallet or domain.

NameTypeReqDescription
depthstring–On-chain depth: 'shallow' (~200 settlements) or 'deep' (~500)
sellerstringyesSeller wallet (0x + 40 hex) or domain, e.g. 'api.example.com'

No output schema declared.

No examples provided.

x402_seller_trust ~175

Score an x402 seller wallet BEFORE paying it: verdict TRUSTED/CAUTION/AVOID + confidence from its on-chain settlement graph on Base — settlement count, unique paying counterparties, wallet age, wash-trade and sybil signals — with a signed, offline-verifiable receipt. Vet an unknown x402 endpoint or merchant wallet before you pay: scam, fake-volume wash-trader or sybil cluster? Agent counterparty risk, seller reputation and trust score for x402 / agentic payments. Price: $0.01 per call (x402 payment, USDC on Base mainnet).

NameTypeReqDescription
depthstring–'shallow' (~200 settlements) or 'deep' (~500)
seller_walletstringyesx402 seller payTo wallet (0x + 40 hex)

No output schema declared.

No examples provided.

Common questions

What is the io.github.digitalweb33333-creator/x402-endpoints MCP server?

io.github.digitalweb33333-creator/x402-endpoints is an MCP server listed in the public MCP registry as io.github.digitalweb33333-creator/x402-endpoints. x402 paid API tools for AI agents on Base: EU/global registries, crypto, wallet & agent trust. This page covers its hosted endpoint (https://x402-endpoints.onrender.com/mcp/).

Is the io.github.digitalweb33333-creator/x402-endpoints MCP server safe to use?

io.github.digitalweb33333-creator/x402-endpoints scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.digitalweb33333-creator/x402-endpoints MCP server expose?

io.github.digitalweb33333-creator/x402-endpoints exposes 52 tools: gleif_lei, vies_vat, polymarket_odds, flights_states, ev_charging, and 47 more. Their descriptions and schemas cost roughly 11,865 tokens of context every time the server is loaded.

Does the io.github.digitalweb33333-creator/x402-endpoints MCP server require authentication?

No. We connected to io.github.digitalweb33333-creator/x402-endpoints without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.digitalweb33333-creator/x402-endpoints MCP server still maintained?

io.github.digitalweb33333-creator/x402-endpoints is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.