Lordevo Shop (x402 website checks)

Security headers + TLS quick grade ($0.002/call)

security_headers

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [SEO, security and site verdicts] Security headers check. Passive check of a public website's HTTPS setup: TLS version and certificate expiry, HTTP->HTTPS redirect, HSTS, CSP, X-Frame-Options/frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, cookie flags, version disclosure. Returns grade A+..F and fixes. ~1-3 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": "security_headers"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Website to check: a public http(s) URL or bare domain, 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.

Output Schema

Name	Required	Description
`tls`	No
`url`	No
`tool`	No
`cache`	No
`grade`	No
`https`	No
`score`	No
`_trial`	No	Present when the call was a free trial call.
`issues`	No
`headers`	No
`provider`	No
`price_usd`	No
`http_to_https`	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: +"Website to check: a public http(s) URL or bare domain, e.g. https://example.com"

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"
+      ]
+    },
+    {
+      "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"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "grade": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "headers": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "http_to_https": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "https": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "issues": {
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "tls": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description adds real context beyond them: the check is passive, runs in ~1-3s, returns a letter grade with fixes, and is metered at $0.002/call via x402 with a per-IP daily trial cap. It could still say more about what is not covered (e.g. deep scanning or authenticated pages).

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

Conciseness3/5

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

The lead sentence is pricing boilerplate and a bracketed tag line rather than the tool's purpose, which delays the front-loaded value. The core enumeration is dense but efficient; the '$0.002 per call' wording is repeated between title and description, costing space without new information.

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 read-only, single-URL diagnostic with a full input schema and an existing output schema, the description covers cost, latency, passivity, and the shape of the result (grade A+..F plus fixes). It is nearly complete; only the boundary against overlapping scanning tools is left unaddressed.

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 description coverage is 100%, so both `url` and `trial` are already documented, including the URL format example and the trial limit. The description repeats the trial mechanism and adds no new syntax or constraint on the required `url`, so the baseline of 3 applies.

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

Purpose4/5

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

The description gives a specific verb+resource ('Security headers check', 'Passive check of a public website's HTTPS setup') and enumerates exactly what is inspected (TLS version, cert expiry, redirect, HSTS, CSP, X-Frame-Options, cookie flags, version disclosure), which implicitly separates it from narrower siblings like ssl_cert. It never names an alternative sibling explicitly, so differentiation still requires inference.

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 through the enumerated scope plus the note that the check is passive and takes ~1-3s, and there is practical guidance on the free trial ('add "trial": true or use try_free'). There is no explicit when-to-use/when-not statement nor a pointer to the obvious overlapping siblings (ssl_cert, security_scan_lite, site_verdict).

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?