Skip to main content
Glama

Grade a website's HTTP security headers (A-F)

security_headers
Read-only

Grade a website's HTTP security headers (A-F): HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, plus leaked server/version headers, with a fix hint for each missing one. Fast (under 2 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses real operational traits: sub-2s latency, a 20-calls/day free quota shared across free tools, a $0.002 overage price, and an x402/USDC-on-Base payment path. It also states the output includes a fix hint per missing header. It stops short of describing the response structure, but that is minor for a grading tool.

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?

Front-loaded with the purpose and the graded header list, then the cost model. Dense but each clause adds information; the pricing sentence is long but relevant to invocation decisions. Minor redundancy between the free-tier and per-call pricing clauses.

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 two-parameter, read-only, no-output-schema tool, the definition covers what is checked, how it is scored (A-F), what extra findings appear (leaked version headers, fix hints), latency, and the full payment flow. Only the exact response shape is unstated, which is acceptable given the schema is complete.

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 the url and payment parameters are already fully documented in the schema. The description only echoes the payment economics, which the schema's payment field already explains. Baseline 3 applies since the schema carries the parameter burden.

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 and resource ('Grade a website's HTTP security headers') and enumerates exactly what is inspected (HSTS, CSP, X-Frame-Options, COOP, etc.) plus leaked server headers, so an agent knows precisely what the tool returns. It does not explicitly distinguish itself from the sibling 'headers' tool, which is the main gap.

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 context is implied rather than stated: it's a fast, cheap, read-only grading pass. There is no explicit 'use this instead of X when…' routing, and the distinction from the sibling 'headers' tool is left to inference. The pricing/quota framing does help an agent decide whether to call it.

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.