Skip to content

tools MCP server

dev.workers.sebastiaan-ba3.x402lint/toolsx402lint.sebastiaan-ba3.workers.devstreamable-httpv1.0.0Scanned

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

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the tools MCP server can do

The tools MCP server is published by x402lint.sebastiaan-ba3.workers.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: deep_lint_x402_endpoint and conform_x402_endpoint), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (lint_x402_endpoint); 3 tools can send data out of your system (lint_x402_endpoint, deep_lint_x402_endpoint and conform_x402_endpoint).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • conform_x402_endpointLive adversarial test: fires malformed/garbage/fake payment proofs at a target to see if any trick it into returning 200 without a real payment.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Live adversarial test: fires malformed/garbage/fake payment proofs at a target to see if any trick it into returning 200 without a real payment. Requires payment (0.05 USDC on Base, x402) -- NOT callable for free over MCP. Calling this tool returns the exact HTTP request to make instead; it does not run the check itself. See GET /conform?url=... on this same origin.
  • deep_lint_x402_endpointCross-checks a target's live 402 body against its /.well-known/x402.json manifest (payTo/asset/network mismatches).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Cross-checks a target's live 402 body against its /.well-known/x402.json manifest (payTo/asset/network mismatches). Requires payment (0.01 USDC on Base, x402) -- NOT callable for free over MCP. Calling this tool returns the exact HTTP request to make instead; it does not run the check itself. See GET /deep-lint?url=... on this same origin.
Only reads 1Show 1 read-only tool
  • lint_x402_endpointFetch a URL, expect an HTTP 402 response, and validate the JSON body against the x402 protocol shape (x402Version, accepts[] fields, resource/description).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://x402lint.sebastiaan-ba3.workers.dev/mcp: tools/list returned 3 tools to an anonymous client, including deep_lint_x402_endpoint (write), conform_x402_endpoint (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 0 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 1 changed.+2 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 2.View diff
    • Tools that change things, listed without credentials: 0 to 2

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tools https://x402lint.sebastiaan-ba3.workers.dev/mcp
claude mcp add --transport http tools https://x402lint.sebastiaan-ba3.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__tools__lint_x402_endpoint",
      "mcp__tools__deep_lint_x402_endpoint",
      "mcp__tools__conform_x402_endpoint"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tools. Review it before you use it.

Capability tags behind 3 rules
  • mcp__tools__lint_x402_endpoint untrusted-input, outbound
  • mcp__tools__deep_lint_x402_endpoint outbound
  • mcp__tools__conform_x402_endpoint outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.sebastiaan-ba3.x402lint/tools/verify?hash=c4903a7139c9677bb08493388bb08ad729d069b4290e8af367a0edd0e7c9c942" | jq -e '.changed == false'

Pinned hash c4903a7139c9, from Nov 17, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.sebastiaan-ba3.x402lint/tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.sebastiaan-ba3.x402lint/tools
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.sebastiaan-ba3.x402lint/tools.svg)](https://radar.anlyon.com/servers/dev.workers.sebastiaan-ba3.x402lint/tools)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

tools MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the tools MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the tools MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the tools MCP server have?

3 tools: 2 write, 1 read. deep_lint_x402_endpoint, conform_x402_endpoint and lint_x402_endpoint.

Does the tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the tools MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): lint_x402_endpoint, deep_lint_x402_endpoint and conform_x402_endpoint.

Has the tools MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.