Lints whether a paid API's 402 response speaks the x402 protocol correctly.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Absolute http(s) URL of the paid endpoint to check (should return HTTP 402).
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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.
| Argument | Type | Description |
|---|---|---|
| url* | string | Absolute http(s) URL of the paid endpoint to check (should return HTTP 402). |
{
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "Absolute http(s) URL of the paid endpoint to check (should return HTTP 402)."
}
}
}