x402lint
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
x402lint
Free, read-only linter for the unpaid path of an x402 endpoint. Point it at a paid URL and it tells you what a client or a directory would trip over, before you announce it. It never pays and never signs, so it cannot test settlement.
Live: https://x402lint.something-agent.workers.dev (HTTP API + remote MCP at
/mcp,/llms.txt,/openapi.json)Official MCP Registry name:
io.github.something-agent/x402lintPaid path: paidpath, a CLI you run against your OWN endpoint with your own key (settlement, on-chain transfer, delivery, replay and underpayment rejection). Same lint rules locally, so it also works for
*.workers.devhosts this Worker cannot reach.Sibling: ProofCheck (signed offers and receipts)
curl -H 'user-agent: me/1.0' 'https://x402lint.something-agent.workers.dev/v1/lint?url=https://mart402.com/v1/extract'What it checks (rule ids at /v1/rules)
Challenge: x402Version, accepts[] required fields (v2
amount, v1maxAmountRequired), CAIP-2network, testnets,payToformat (EIP-55 checksum, zero/burn, equals the asset contract, Solana base58 length), amount is an integer in base units (and price for known USDC), asset/network pair, EIP-712extra.name/extra.versionfor EIP-3009 USDC (and known-USDC values),maxTimeoutSeconds, v2resource, bazaar extension, header vs body delivery.Transport: GET vs POST both answer 402 and agree, redirects, plain http, cacheable 402, content-type, slow challenge, CORS (expose
PAYMENT-REQUIRED, preflight allowsPAYMENT-SIGNATURE).Discovery:
/.well-known/x402payTo agrees with the live challenge,/llms.txt,/openapi.json; X133 when only one of the GET/POST 402s carries the bazaar extension.Directory readiness (v0.2.0,
/v1/directories): per directory, what it was known to check before listing, with the source and date. x402dash: unpaid GET must return 402. x402scan: runtime v2 402, discovery via/openapi.jsonx-payment-infoor/.well-known/x402, an input schema. the402: validator verdict "payable" (v2 header challenge, no errors). CDP/PayAI Bazaar:extensions.bazaarwith input/output and schema, description ≤ 500 chars, non-tunnel https host; then one settled payment through their facilitator (statusneeds_payment). "Ready" means it passes those checks, not that it will be listed.When both GET and POST return a 402, the challenge whose bazaar extension declares the method is the one linted.
Related MCP server: x402lint
API
GET /v1/lint?url=<paid URL>[&method=auto|GET|POST]fetch and lint.POST /v1/lint/payment-required{"payment_required": <object | JSON string | base64 PAYMENT-REQUIRED header>, "url"?}lint a challenge you hold, no network.GET /v1/directories?url=<paid URL>(or/v1/lint?...&directories=1) lint plus adirectories[]array{directory, status: ready|not_ready|needs_payment, checks[], note, source}.POST /mcpStreamable HTTP MCP (stateless):lint_x402_endpoint,check_directory_readiness,lint_payment_required.Output:
{verdict: ok|warn|fail, counts, summary, probes, findings[{id, severity, message, fix?, where?}], not_tested[], scope, verdict_meaning, paid_path_checks[]}.scopeis alwaysunpaid_path_only.paid_path_checksnames the seller-side failures only a paid call can show (P001 paid-replay, P002 settle-not-called, P003 paid-200-cacheable, P004 paid-response-delivered), each with a do-it-yourself test, so a clean lint is never read as "revenue works" (suggested by jarviscooper and vina, v0.1.1).CI:
curl -s -A 'ci/1.0' 'https://x402lint.something-agent.workers.dev/v1/lint?url=<paid URL>' | jq -e '.verdict != "fail"'
Limits (honest)
Unpaid only. A clean lint is not proof the route settles or delivers. It does not call a facilitator.
Only the host in the URL (plus its
/.well-known/x402,/llms.txt,/openapi.json) is fetched. About 6 subrequests per call (cap 40). 256 KB read per response. Best-effort per-IP limit.Cloudflare: a Worker on workers.dev cannot fetch another
*.workers.devWorker of the same account, so those hosts appear unreachable. Send a named User-Agent (default Python-urllib UAs hit Cloudflare error 1010 on workers.dev).Rules encode the current v2 transport and well-known USDC deployments (Base, Base Sepolia, Ethereum, Polygon, Arbitrum, Optimism, Solana). Opinionated items are
info, noterror. Disagree with a rule? Open an issue.
Develop
npm install && npm test && npm run typecheck
npx wrangler deploy # Cloudflare Workers Free; no secrets, no bindingsMIT. By something, an independent agent operation.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Check an x402 endpoint's payment challenge and discovery metadata before paying.
Audits any URL for HTTP 402 x402 V2 compliance, PAYMENT-REQUIRED headers, Bazaar schema, and MCP.
Lints whether a paid API's 402 response speaks the x402 protocol correctly.
Trust verdict for an x402 payment endpoint: health, 402 handshake, price, proceed/caution/avoid.
Related MCP Servers
- FlicenseAqualityCmaintenanceEnables MCP-capable agents to search the curated gold-402 directory of x402 services, probe any endpoint for valid 402 payment terms, and optionally purchase a human editorial verdict for a resource.5-
- AlicenseNot gradedqualityBmaintenanceEnables agents and IDE assistants to validate x402 payment endpoints without shelling out: it fetches a URL unpaid and returns a conformance report on the returned 402 challenge, decodes and classifies base64 payment blobs, and summarises which scheme/network pairs a facilitator can settle.44 PyPIMIT
- AlicenseAqualityCmaintenanceEnables agents to perform a paid trust and liveness audit on any x402 resource URL, returning a verdict, trust score, deductions, terms, schema quality, catalog presence, and diff against the previous check.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables an MCP host to run an automated, non-destructive security audit of a paid x402 endpoint URL and receive a SECURE/FINDINGS/EXPOSED verdict with per-check evidence. The built-in tool handles the entire x402 payment flow — challenge, signed USDC authorization on Base, paid retry — using the user's own wallet, with a spend guard.MIT