Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

HTTP security header audit of a URL in one call: HSTS, CSP, nosniff, frame protection, referrer, permissions and COOP po

security_headers
Read-onlyIdempotent

HTTP security header audit of a URL in one call: HSTS, CSP, nosniff, frame protection, referrer, permissions and COOP policies, score and A to D grade (url=https://example.com). Live request, public hosts only. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "security_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNopublic URL to inspect
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the request is live (not cached), targets are restricted to public hosts, and each call costs $0.002 USDC on Base via x402. It does not describe failure modes or what a partial/failed audit returns, which keeps it short of a 5.

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 core purpose and header list are front-loaded in a single dense statement, with the example URL and payment note appended compactly. It is efficient with no filler, though the one-sentence packing of headers, payment, and host restrictions makes it slightly dense to parse.

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 purpose, scope limits (public hosts), live-request behavior, and the paid two-step invocation. Missing pieces are minor: it does not explain what the returned report contains beyond 'score and grade', nor how non-2xx or non-public URLs are handled.

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 parameters (url, x_payment) are already documented, including the two-step payment flow in the schema itself. The description only adds a concrete URL example, which is marginal value over the schema; baseline 3 applies.

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 — an HTTP security header audit of a URL — and enumerates exactly which headers are checked (HSTS, CSP, nosniff, frame protection, referrer, permissions, COOP) plus the score and A–D grade produced. This distinguishes it from sibling tools like url_status or page_meta, which would not report header policies or grades.

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?

Provides two useful constraints: it performs a live request and works on public hosts only, and shows an example (url=https://example.com). However, it never says when to prefer this over neighbouring tools such as url_status or page_meta, nor what happens for private/internal hosts, leaving selection guidance implied rather than explicit.

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