Skip to main content
Glama

Security Headers + TLS Audit

audit_secheaders

Read-onlyIdempotent

Full security headers + TLS audit of a website URL. Fetches the target server-side, probes TLS on port 443, checks whether the plain-HTTP variant redirects to HTTPS, and runs 11 weighted checks: HTTPS redirect enforcement, TLS modernity (negotiated version plus TLS 1.0/1.1 acceptance), certificate validity (days to expiry, issuer), HSTS (max-age against the one-year floor, includeSubDomains/preload), Content-Security-Policy (presence plus 'unsafe-inline'/'unsafe-eval'/bare-* weaknesses), X-Content-Type-Options nosniff, frame protection (X-Frame-Options or CSP frame-ancestors), Referrer-Policy, Permissions-Policy, cookie flags (Secure/HttpOnly/SameSite on every Set-Cookie), and Server/X-Powered-By version disclosure. These are the findings behind failed security reviews, browser warnings, session hijacking, clickjacking, and downgrade attacks. Returns machine-readable JSON: 0-100 score, A-F grade, an exposure-risk level (Low/Moderate/Elevated/High) with the failing transport/header trigger checks named, per-check pass/partial/fail/unknown with evidence, a site block (HTTP status, TLS version, certificate days left and issuer, security headers seen), and the top 3 prioritized fixes. HONEST LIMITS: a single-response snapshot at scan time — header posture can differ per path/app on the same host, TLS is probed on 443 only, and this is not a penetration test. Checks that cannot be evaluated return unknown, never guesses. Cost: $1.50 USDC on Base per call, paid via x402 — the caller's agent pays from its owner's approved wallet; no API key needed. Use this before a launch or security review, after a server or CDN change, or to triage a header/TLS finding.

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

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite URL to audit (https preferred), e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing the paid x402 cost ($1.50 USDC on Base, no API key), that the fetch is server-side, and a candid HONEST LIMITS block (single-response snapshot, TLS probed on 443 only, not a penetration test, unevaluable checks return 'unknown' rather than guesses). That is exactly the operational context an agent needs before spending money on a call.

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 purpose, then mechanics, then return shape, then limits and cost — a logical order. The long enumeration of 11 checks and the return-value inventory is dense but each item carries signal; only mild trimming (e.g. the rhetorical 'findings behind failed security reviews...' sentence) would be possible.

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?

No output schema exists, and the description fully compensates by describing the JSON shape (0-100 score, A-F grade, risk level with named triggers, per-check verdicts with evidence, site block, top 3 fixes). Combined with the cost and limits disclosure, an agent can decide and call without further information.

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 there is only one parameter, so the baseline is 3. The description adds real meaning by explaining how the url is used: the server fetches it, probes TLS on port 443, and separately checks whether the plain-HTTP variant redirects to HTTPS — telling the agent that both schemes of the host are exercised.

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 ('Full security headers + TLS audit of a website URL') and enumerates exactly what is probed, so an agent knows this is the comprehensive scanner. The word 'Full' plus the enumeration of 11 weighted checks implicitly distinguishes it from the sibling audit_secheaders_lite without needing to open either 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?

Gives explicit triggering contexts: 'before a launch or security review, after a server or CDN change, or to triage a header/TLS finding.' It does not name the lite sibling as the cheaper alternative nor state when not to use this tool, so the routing 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.