Tools

dev.workers.sebastiaan-ba3.x402lintPublished by x402lint.sebastiaan-ba3.workers.devOfficial publisherv1.0.0Updated Oct 24, 2026

Lints whether a paid API's 402 response speaks the x402 protocol correctly.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant check whether a paid API's 402 response follows the x402 protocol shape and get a pass/fail report.

What you can do
Exposes one tool, lint_x402_endpoint, which fetches a given URL, expects an HTTP 402 response, and validates the JSON body against the x402 protocol shape, including x402Version, the accepts[] fields, and resource/description. It returns a pass/fail report with concrete errors and warnings. It is free and needs no account.
When to use it
Use it when you need to confirm that a paid API's 402 response follows the x402 protocol shape, such as a quick check before wiring up or debugging an x402 payment flow.
Requirements
Needs network access to the remote endpoint; no local runtime, account, or API key is required.
Before you install
The tool fetches any URL you give it, so avoid pointing it at internal or sensitive addresses; it is free and needs no account, but the URL you supply is sent to the remote service.

Installation

In SourceWeft

  1. Open Tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.sebastiaan-ba3.x402lint%2Ftools/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tools": {
      "type": "http",
      "url": "https://x402lint.sebastiaan-ba3.workers.dev/mcp"
    }
  }
}

Tools

1

lint_x402_endpoint

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.

Parametersurlrequired

Version history

1
  1. v1.0.0LatestOct 15, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.