@true402.dev/mcp-server

robots_check

Fetch a site's robots.txt + llms.txt and report whether the major AI crawlers are allowed/blocked, plus sitemaps. POST { url }; unpaid returns 402.

Instructions

Fetch a site's robots.txt + llms.txt and report whether the major AI crawlers are allowed/blocked, plus sitemaps. POST { url }; unpaid returns 402. (PAID x402 service — USDC on Base; the MCP server needs a funded wallet to settle.) Price: $0.003 USD (fixed).

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": {
      "url": "<url>"
    },
    "name": "robots_check"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Any URL on the site

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.1Jun 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical behavior an agent would otherwise trip on: POST body shape, 402 on unpaid requests, x402/USDC-on-Base settlement, the need for a funded wallet, and a fixed $0.003 price. It stops short of describing response structure, caching, or failure modes beyond the 402.

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

Conciseness4/5

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

The capability is front-loaded in the first sentence and the payment caveats are compressed into the remainder. The parenthetical is dense but every clause (402, x402, USDC/Base, funded wallet, price) is decision-relevant for an agent, so little waste remains.

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

Completeness4/5

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

For a single-parameter read tool with no output schema and no annotations, the description covers what it returns at a high level (crawler allow/block, sitemaps) and the payment gate that would otherwise cause silent failures. A bit more on response shape would be the only remaining gap.

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?

Schema coverage is 100% and the single `url` param is documented as "Any URL on the site," so the schema already does the work. The description only adds that the value is POSTed, which is marginal extra meaning; baseline 3 applies.

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: fetch robots.txt + llms.txt and report AI-crawler allow/block status plus sitemaps. That scope is distinct from the nearest siblings (headers_check, seo_audit), so an agent can pick it 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 Guidelines3/5

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

Usage is implied by the output described (AI crawler access + sitemaps), but there is no explicit when-to-use/when-not or named alternative such as headers_check or seo_audit. The only explicit guidance is the payment prerequisite, not task routing.

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