# x402lint (remote · x402lint.something-agent.workers.dev)

Free x402 endpoint linter: unpaid 402 challenge, payTo/asset/amount, CORS, directory readiness.

- Trust score: 63/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `x402lint.something-agent.workers.dev`: 63/100 (this document), [markdown](https://verifymcp.io/servers/something-agent-x402lint/x402lint.md), [page](https://verifymcp.io/servers/something-agent-x402lint/x402lint)

## Channel facts

- Endpoint: `https://x402lint.something-agent.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 373 tokens (~124/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the x402lint MCP server?

x402lint is a hosted endpoint at https://x402lint.something-agent.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http something-agent-x402lint 'https://x402lint.something-agent.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "something-agent-x402lint": {
      "url": "https://x402lint.something-agent.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "something-agent-x402lint": {
      "type": "http",
      "url": "https://x402lint.something-agent.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.something-agent-x402lint]
url = "https://x402lint.something-agent.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "something-agent-x402lint": {
      "type": "remote",
      "url": "https://x402lint.something-agent.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add something-agent-x402lint --url 'https://x402lint.something-agent.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  something-agent-x402lint:
    url: "https://x402lint.something-agent.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "something-agent-x402lint": {
      "Transport": "http",
      "Url": "https://x402lint.something-agent.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add something-agent-x402lint -t streamable-http -u 'https://x402lint.something-agent.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "something-agent-x402lint": {
      "type": "http",
      "url": "https://x402lint.something-agent.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 61, +1)

- [functional] Server version: 0.2.4 → 0.2.5

### 2026-10-29 (score 60, 0)

- [functional] Server version: 0.2.0 → 0.2.4

### 2026-10-28 (score 60, 0)

- [functional regression] Schema quality: 238 → 373
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.1.0 → 0.2.0
- [functional] New tool “check_directory_readiness”

### 2026-10-27 (score 60)

First indexed and scored.

## MCP tools (3)

### `lint_x402_endpoint` (~120 tokens)

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.

Input parameters:

- `method` (string): Default auto: tries both
- `url` (string, required): The paid x402 URL

### `check_directory_readiness` (~135 tokens)

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.

Input parameters:

- `method` (string): Default auto: tries both
- `url` (string, required): The paid x402 URL

### `lint_payment_required` (~89 tokens)

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.

Input parameters:

- `payment_required` (required): Object, JSON string, or base64 header value
- `url` (string): Optional: the URL it was served from, to check resource.url

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/something-agent-x402lint/x402lint#diagnostics

## Score history

- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 62
- 2026-11-01: 62
- 2026-10-31: 61
- 2026-10-30: 61
- 2026-10-29: 60
- 2026-10-28: 60
- 2026-10-27: 60

## Common questions

### What is the x402lint MCP server?

x402lint is an MCP server listed in the public MCP registry as io.github.something-agent/x402lint. Free x402 endpoint linter: unpaid 402 challenge, payTo/asset/amount, CORS, directory readiness. This page covers its hosted endpoint (https://x402lint.something-agent.workers.dev/mcp).

### Is the x402lint MCP server safe to use?

x402lint scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the x402lint MCP server expose?

x402lint exposes 3 tools: lint_x402_endpoint, check_directory_readiness, lint_payment_required. Their descriptions and schemas cost roughly 344 tokens of context every time the server is loaded.

### Does the x402lint MCP server require authentication?

No. We connected to x402lint without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the x402lint MCP server still maintained?

x402lint is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://x402lint.something-agent.workers.dev/mcp
- Repository: https://github.com/something-agent/x402lint
- Website: https://x402lint.something-agent.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/something-agent-x402lint/x402lint.xml
- Changelog JSON feed: https://verifymcp.io/servers/something-agent-x402lint/x402lint.json
- HTML version of this page: https://verifymcp.io/servers/something-agent-x402lint/x402lint