tools
Lints whether a paid API's 402 response speaks the x402 protocol correctly.
Should I use this
Quality & Safety
A
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
~112Tokens (tool definitions)
~504 BTypical response size
Minimal attention impact (0.09% of 128k context)
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"tools": {
"url": "https://x402lint.sebastiaan-ba3.workers.dev/mcp"
}
}
}Remote endpoints
https://x402lint.sebastiaan-ba3.workers.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢lint_x402_endpoint(url)
Fetch a URL, expect an HTTP 402 response, and validate the JSON body against the x402 protocol shape (x402Version, accepts[] fields, resource/description). Free, no account. Returns a pass/fail report with concrete errors and warnings.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "Absolute http(s) URL of the paid endpoint to check (should return HTTP 402)."
}
},
"required": [
"url"
]
}Community
Evidence
Recent observations
verifiedversion not recorded1 tools