x402lint
Server Details
Free x402 endpoint linter: unpaid 402 challenge, payTo/asset/amount, CORS, directory readiness.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- something-agent/x402lint
- GitHub Stars
- 0
- Server Listing
- x402lint
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
The three tools split cleanly by input mode: remote endpoint fetch (lint_x402_endpoint), offline object (lint_payment_required), and per-directory listing readiness (check_directory_readiness). The only real overlap is that check_directory_readiness and lint_x402_endpoint both inspect the unpaid 402 challenge and discovery files, so an agent may hesitate over which to call first, but the directory-vs-spec framing in the descriptions resolves it.
All three names are snake_case verb_noun (check_*, lint_*), which is predictable and readable. Minor deviation: two different verbs (check vs lint) for what is essentially the same activity, and the noun phrases vary in specificity (directory_readiness vs payment_required vs x402_endpoint).
Three tools is well-matched to a narrow linting purpose, and each covers a genuinely distinct input path (network fetch, supplied object, directory-listing criteria). Nothing looks padded or redundant.
The lint lifecycle is covered: live endpoint, offline object, and third-party directory acceptance criteria, all returning findings with fixes. Gaps are minor but real — no batch/multi-endpoint lint, no standalone check for the non-directory transport/discovery items outside a full endpoint fetch, and no way to re-validate after applying fixes without re-running the whole endpoint lint.
Available Tools
3 toolscheck_directory_readinessAInspect
Lint an x402 endpoint's unpaid 402 and report, per directory, whether it meets what x402dash (unpaid GET must return 402), x402scan (OpenAPI x-payment-info or /.well-known/x402, input schema), the402 (validator 'payable') and the CDP/PayAI Bazaar (bazaar extension, description <= 500 chars, non-tunnel https host; listing then needs one settled payment) were known to check. Never pays. Free.
Inputs: url (required), method.
lint_payment_requiredAInspect
Lint a PaymentRequired object you already have (decoded JSON, a JSON string, or the raw base64 PAYMENT-REQUIRED header). Same field/value checks as lint_x402_endpoint, no network access. Free.
Inputs: payment_required (required), url.
lint_x402_endpointAInspect
Unpaid lint of an x402 endpoint: fetches the 402 (GET and POST), then checks the challenge (version, accepts[] fields, CAIP-2 network, payTo/asset/amount sanity, EIP-712 name/version, timeouts, resource), transport (redirects, cache headers, CORS) and discovery files. Returns findings with ids, severities and fixes. Never pays. Free.
Inputs: url (required), method.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
Lints whether a paid API's 402 response speaks the x402 protocol correctly.
Test any x402 paid URL without paying: 402, PAYMENT-REQUIRED, USDC, amounts, payTo, EIP-712, CORS.
Audits any URL for HTTP 402 x402 V2 compliance, PAYMENT-REQUIRED headers, Bazaar schema, and MCP.
Related MCP Servers
- AlicenseAqualityBmaintenanceNon-custodial x402 payment checks: decode 402 responses, verify settlements against on-chain balance changes, lint scheme specs, and test facilitators.6Apache 2.0
- 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
- AlicenseAqualityBmaintenanceMCP server that checks an x402 paid endpoint before an agent pays it, and checks afterwards that the receipt opens to exactly one real on-chain settlement. Two tools, no account, no API key.2166 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables agents to probe one or more paid HTTP endpoints and verify they actually return a usable 402 payment challenge — checking status, Base64/JSON envelope validity, required payment fields, MPP dual-stack discoverability, and whether gated content leaks for free. Results come back with A–F grades and plain-English findings, backed by batch scanning and live catalog health stats, without ever sending a payment.3141 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.