Lordevo Shop (x402 website checks)

Can I fetch this URL? robots.txt + AI-crawler permission gate ($0.002/call)

can_fetch

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Fetch and read the web] Pre-fetch gate for agents and scrapers: is this exact URL allowed by robots.txt (RFC 9309: missing = allow, 5xx/unreachable = disallow) for generic agents and 16 named AI agents/crawlers (ChatGPT-User, Claude-User, PerplexityBot, GPTBot, ClaudeBot, Google-Extended, CCBot...), plus Crawl-delay, Content-Signal (search / ai-input / ai-train), X-Robots-Tag noai/noindex from a HEAD request, and sitemaps. Verdict allowed / disallowed / allowed_but_no_ai_use / allowed_with_crawl_delay. Never downloads the page body. Cached up to 10 min. ~0.3-2 s.

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": "can_fetch"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Exact URL you plan to fetch, e.g. https://example.com/blog/post (a bare domain checks the home page)
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.

Output Schema

Name	Required	Description
`url`	No
`noai`	No
`page`	No
`path`	No
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`agents`	No
`origin`	No
`allowed`	No
`summary`	No
`verdict`	No
`provider`	No
`sitemaps`	No
`price_usd`	No
`robots_txt`	No
`content_signal`	No
`robots_http_status`	No
`crawl_delay_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / url / description

Previous value: -"Public http(s) URL or bare domain, e.g. https://example.com"New value: +"Exact URL you plan to fetch, e.g. https://example.com/blog/post (a bare domain checks the home page)"

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "url",
+        "verdict",
+        "allowed",
+        "agents",
+        "robots_txt"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "agents": {
+      "additionalProperties": {
+        "type": "boolean"
+      },
+      "type": "object"
+    },
+    "allowed": {
+      "type": "boolean"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "content_signal": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "crawl_delay_seconds": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "noai": {
+      "type": "boolean"
+    },
+    "origin": {
+      "type": "string"
+    },
+    "page": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "path": {
+      "type": "string"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "robots_http_status": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "robots_txt": {
+      "enum": [
+        "present",
+        "missing",
+        "unreachable"
+      ],
+      "type": "string"
+    },
+    "sitemaps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "verdict": {
+      "enum": [
+        "allowed",
+        "disallowed",
+        "allowed_but_no_ai_use",
+        "allowed_with_crawl_delay"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds a lot beyond them: RFC 9309 edge-case resolution (missing = allow, 5xx/unreachable = disallow), HEAD-request sourcing of X-Robots-Tag, a 10-minute cache, a 0.3-2s latency band, and an explicit 'never downloads the page body' guarantee. Pricing and the free-trial path are also disclosed, which matters for a paid endpoint.

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?

Effectively one dense paragraph, front-loaded with price and the category tag, then the core question, then edge cases, then cost/latency. Every clause carries information, but the heavy parenthetical enumerations (16 agents, signal types) make it a single unbroken block that is harder to scan than a short bulleted split would be.

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?

An output schema exists, so return values need not be explained, and the description nonetheless names the verdict vocabulary an agent will branch on. For a paid, cached, single-URL permission check, the agent has everything needed: input meaning, cost, latency, trial path, and the RFC edge-case rules that determine the verdict.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented, and the description stays consistent with the url semantics ('this exact URL'). It adds real value on the trial parameter by pointing to the try_free sibling as an alternative route to the free call, which the schema alone does not convey.

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 precise verb+resource: it answers whether one exact URL is allowed by robots.txt, and enumerates what it evaluates (RFC 9309 rules, 16 named AI agents, Crawl-delay, Content-Signal, X-Robots-Tag, sitemaps) and what it returns (allowed / disallowed / allowed_but_no_ai_use / allowed_with_crawl_delay). The 'permission gate' framing plus 'Never downloads the page body' separates it from fetch/extract siblings like page_markdown without the agent opening a 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?

'Pre-fetch gate for agents and scrapers' clearly signals the when: call it before fetching a URL. It also routes trial users ('add "trial": true or use try_free'). It does not name the nearest overlapping siblings (preflight, url_trust, agent_readiness) or say when this check is unnecessary, so the exclusion side is left to inference.

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

All Lordevo Shop (x402 website checks) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?