Skip to main content
Glama

Check a site's security headers and cookies

headers
Read-only

Security headers of a URL's final response: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options (or CSP frame-ancestors), X-Content-Type-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Opener-Policy and Cross-Origin-Resource-Policy, each with present, value, ok and advice. Also cookies missing Secure, HttpOnly or SameSite (names only), version leaks in Server or X-Powered-By, and a grade from A to F. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL or domain, e.g. example.com

Output Schema

NameRequiredDescriptionDefault
urlNo
gradeNo
leaksNo
scoreNo
statusNo
cookiesNo
headersNo
finalUrlNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "cookies": {},
      +    "finalUrl": {},
      +    "grade": {},
      +    "headers": {},
      +    "leaks": {},
      +    "score": {},
      +    "status": {},
      +    "url": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses pricing ($0.002 per successful call), the payment rail (x402, USDC across multiple networks), and failure behavior (failed calls are not charged) — cost details an agent needs before invoking a paid tool. It also clarifies that cookies are reported by name only, which sets privacy/return expectations not visible in the annotations.

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 output scope is front-loaded and the pricing/failure terms are placed at the end where they belong. The long enumeration of header names is dense but each item is informative for selection; a slightly tighter phrasing could trim the list without losing meaning.

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?

Given a rich output schema (returned fields need no explanation) and annotations covering safety and open-world behavior, the description supplies the remaining essentials: what is inspected, the depth of the report, the grading scale, and the paid-call cost model. Nothing material for correct invocation appears to be missing.

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?

With a single parameter at 100% schema coverage, the baseline is 3; the description adds real meaning by specifying that the URL is inspected at its 'final response' (i.e., after redirects), which the schema's 'URL or domain' wording does not convey. It does not, however, discuss URL format edge cases or validation behavior beyond the schema's example.

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?

The description names a specific verb ('Check') and resource ('security headers and cookies' of a URL's final response), then enumerates the exact headers, cookie flags, version leaks, and A–F grade returned. That level of specificity makes it unmistakably distinct from adjacent tools such as web_security_txt, which concerns a policy file rather than live HTTP response headers.

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 rather than stated: an agent can infer this is the tool for auditing a live site's response headers, and 'final response' hints that redirects are followed. However, there is no explicit when-to-use/when-not guidance and no named alternative for related checks, so the selection logic must be inferred from the feature list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources