x402 Endpoint Scanner

Scan up to 10 x402 endpoints at once

scan_batch

Read-onlyIdempotent

Probe up to 10 x402 endpoint URLs in one batch without sending payment, returning per-URL results and a health summary while isolating any failures.

Instructions

Runs scan_endpoint sequentially over a list of URLs (max 10) and returns each full result plus a one-line summary, e.g. '7/10 healthy, 2 dead, 1 broken envelope'. One bad URL never aborts the batch — its error is reported per-item instead. Same no-spend, SSRF-guarded probe as scan_endpoint applied to every URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "urls": "<urls>"
    },
    "name": "scan_batch"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.9Nov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, non-destructive, open-world, so the bar is lower, yet the description still adds real behavior: sequential execution, per-item error isolation ('one bad URL never aborts the batch'), the return shape (full result plus one-line summary), and the no-spend, SSRF-guarded probe semantics. That is exactly the extra context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool does, then the return format, then failure behavior, then safety semantics. No filler, and the concrete summary example earns its place by making the output shape tangible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe returns, and it does (per-URL full result plus aggregate one-line summary, per-item errors). For a one-parameter batch tool with strong annotations, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter, and the schema already carries the constraints (minItems 1, maxItems 10, maxLength 2048) plus an item-level URL example. The description's 'max 10' and 'list of URLs' restate rather than extend the schema; the added meaning is about processing order rather than the parameter itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Runs scan_endpoint sequentially over a list of URLs') and immediately scopes it (max 10), which cleanly separates it from the single-URL sibling scan_endpoint. An agent can tell batch from single without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The batch-over-single framing makes the selection condition clear: multiple URLs go here, one URL goes to scan_endpoint. It does not explicitly say 'do not use this for a single URL', so it stops short of full when/when-not guidance, but the implied routing is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server