Lordevo Shop (x402 website checks)

CORS check (preflight + allowed origins) ($0.002/call)

cors_check

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Web and domain checks] CORS check. Will a browser on a given origin be allowed to call this URL: sends a CORS preflight (OPTIONS) and a GET with Origin, reports Access-Control-Allow-Origin / Credentials / Methods / Headers / Max-Age, Vary: Origin, and flags arbitrary-origin reflection, wildcard with credentials and null origin. Cached 5 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": "cors_check"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	API or page URL to test, e.g. https://example.com/
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`method`	No	Method for the preflight	GET
`origin`	No	Origin to test, e.g. https://app.example.com	https://example.com

Output Schema

Name	Required	Description
`url`	No
`tool`	No
`cache`	No
`_trial`	No	Present when the call was a free trial call.
`issues`	No
`origin`	No
`allowed`	No
`provider`	No
`price_usd`	No
`allow_origin`	No
`allow_credentials`	No
`reflects_arbitrary_origin`	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 4, 2026

changedInput schema / properties / url / description

Previous value: -"API or page URL to test, e.g. https://api.example.com/v1/items"New value: +"API or page URL to test, e.g. https://example.com/"

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: +"API or page URL to test, e.g. https://api.example.com/v1/items"

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",
+        "allowed"
+      ]
+    },
+    {
+      "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"
+    },
+    "allow_credentials": {
+      "type": "boolean"
+    },
+    "allow_origin": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "allowed": {
+      "type": "boolean"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "issues": {
+      "type": "array"
+    },
+    "origin": {
+      "type": "string"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "reflects_arbitrary_origin": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent), which already cover the safety profile. It discloses pricing ($0.002/call, x402/USDC on Base), a free-trial route with quota (3 per IP per UTC day), result caching (5 min) and expected latency (0.3-2 s), plus exactly which requests are emitted and which misconfigurations are flagged. That is precisely the operational context an agent needs before paying for a call.

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?

Information is front-loaded and the bracketed category tag plus one dense explanatory sentence is efficient. The leading price sentence is justified for a paid tool, though the free-trial mechanics are restated in both the description and the schema, which is slight redundancy.

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?

With an output schema present and full parameter coverage, the description only needs to establish purpose, cost and side effects, and it does all three, including cache TTL and runtime. The one gap is that it never positions itself against the similarly named 'preflight' and 'can_fetch' siblings.

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%, so the schema already documents url, trial, method and origin including the origin regex and method enum. The description adds a little (the 'given origin' framing, trial:'true' hint duplicating the schema, and that method governs the preflight) but no syntax or defaults beyond what the schema states. Baseline 3 is appropriate.

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 resource (CORS check) and frames it as a concrete question: 'Will a browser on a given origin be allowed to call this URL'. It then names the exact mechanism (OPTIONS preflight plus GET with Origin) and the headers reported, so an agent can distinguish it from generic security/header siblings like security_headers or canonical_check.

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 question framing gives clear context for when to reach for it: verifying browser-side cross-origin accessibility of an endpoint. What's missing is an explicit exclusion or pointer to a near-sibling such as 'preflight' or 'can_fetch', which an agent could plausibly confuse with this tool.

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?