mcpbeat Sign in

Tools MCP Server

by workers-sebastiaan-ba3-x402lint Your server? Claim it
answering

Tools is answering right now. Last checked moments ago. It exposes 1 tools.

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

Uptime history 17 days of history · worst day 99%
17 days agonow
100.0%
Uptime 24h
92 of 92 checks
1
Tools
read from the server
118 ms
Response time
average over 24h
open, no key
Access
streamable-http

Tools missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add tools --transport http https://x402lint.sebastiaan-ba3.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://x402lint.sebastiaan-ba3.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.tools]
url = "https://x402lint.sebastiaan-ba3.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "tools": {
      "url": "https://x402lint.sebastiaan-ba3.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "tools": {
      "type": "http",
      "url": "https://x402lint.sebastiaan-ba3.workers.dev/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lint
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.

Endpoints

URLTransportStateLatencyChecked
https://x402lint.sebastiaan-ba3.workers.dev/mcp streamable-http answering 119 ms 0 min ago

Alternatives to Tools

same job, measured the same way
X402score MCP
by zagchk

Check an x402-paid API endpoint's trust score before paying it - live-probed, not self-reported.

75 installs/wk local only
x402lint
by something-agent

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

3 tools answering
Axiom Solana Token Risk
by vercel-axiom-risk-mcp

Solana SPL token risk checks: free preview tool plus links to paid x402 (USDC) full reports.

3 tools answering
X402 Codesearch MCP
by liminalpepe

Free MCP server: index a repo's files into the x402-codesearch Worker's search index.

37 installs/wk local only
Scrape-LE
by nolindnaidoo

Analyse robots.txt content and report whether a path may be crawled.

318 installs/wk local only
KHOTEM
by khotem

Paid API bazaar for agents: seals, audits, wallet intel, codec ops. x402.

24 tools answering
x402-code-mcp
by 6mickswagger9

x402 paid API for AI agents. USDC on Base. CDP facilitator.

13 installs/wk local only
PrufGate
by guardianvigil-labs

Read-only tools that check whether code, and the tests that claim it works, are real.

1 324 installs/wk local only

Tools — questions

Answers built from our own checks of this server.

What can Tools do?
It exposes 1 tools, read directly from the server on our last check. Among them: lint_x402_endpoint. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Tools working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 118 ms. The bar chart above shows every period we have measured.
How do I connect Tools?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tools need an API key?
No. Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tools?
It answers our handshake in 118 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.