Pentest requests, security headers checker, guides

Check a website's security headers

check_security_headers

Read-onlyIdempotent

Fetch one public web page (one GET per redirect, like a browser visit) and grade its HTTP security headers: HTTPS, HSTS, Content-Security-Policy, clickjacking protection, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, version disclosure and cookie flags. Reads headers only. This is not a penetration test.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http or https address, for example https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real behavioral context beyond that: one GET per redirect hop like a browser visit, headers-only inspection, and a scope disclaimer. It stops short of saying what the returned grade looks like or how failures are reported.

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?

Three tightly packed sentences, front-loaded with the action and scope, followed by the enumerated checks and a closing exclusion. No filler or redundant restatement of the title.

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, the description lists the graded checks so the agent knows the content of the response. The only gap is the shape of the result (per-header verdicts vs. an overall grade), which is a minor omission given how much is already specified.

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% and fully documents the single url parameter, so the schema carries the weight. The description still adds constraint meaning beyond the schema by specifying 'one public web page', clarifying no crawling or multi-page scanning occurs.

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 one public web page ... and grade its HTTP security headers') and enumerates exactly which header classes are graded. An agent can distinguish it from get_page (raw fetch) and request_pentest (deeper testing) without opening any 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?

Explicitly scopes usage to a single public page and rules out penetration testing, which implicitly routes the agent to request_pentest for deeper work. It does not explicitly contrast with get_page or search_site, so the alternative-selection guidance is clear but not complete.

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

All Pentest requests, security headers checker, guides 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?