IA-QA — 152 QA & Dev Tools for AI Agents

security_headers_check

Read-only

Analyse the HTTP security headers of a public URL OR of raw response headers you paste in. Grades each header (A–F) for: Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, X-XSS-Protection, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy, and Cross-Origin-Embedder-Policy. Returns an overall score (0–100), per-header grades, missing headers, and fix snippets for Express, Nginx, and Apache. For localhost/private targets the remote server cannot reach, pass the headers parameter instead of url.

Input Schema

Name	Required	Description	Default
`url`	No	Optional. Full public URL to check (e.g. https://example.com). Omit it entirely when using `headers`. The server cannot reach localhost/private IPs.
`headers`	No	Optional, and sufficient on its own (no url needed). The response headers to grade, either as an object {"strict-transport-security": "max-age=...", ...} or as the raw header block pasted as a string (e.g. `curl -sI` output). Use this to audit a local server the remote MCP cannot reach.

Output Schema

Name	Required	Description	Default
`fix`	No
`key`	No
`url`	No
`weak`	No
`grade`	No
`score`	No
`value`	No
`header`	No
`source`	No
`weight`	No
`details`	No
`missing`	No
`weak_count`	No
`missing_count`	No
`overall_grade`	No
`headers_checked`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / examples

Added value: +[
+  {
+    "url": "https://www.ia-qa.com"
+  }
+]

Changed2 schema fields changedJun 23, 2026

changedInput schema / properties / headers / description

Previous value: -"Alternative to `url`: the response headers to grade, either as an object {\"strict-transport-security\": \"max-age=...\", ...} or as the raw header block pasted as a string (e.g. `curl -sI` output). Use this to audit a local server the remote MCP cannot reach."New value: +"Optional, and sufficient on its own (no url needed). The response headers to grade, either as an object {\"strict-transport-security\": \"max-age=...\", ...} or as the raw header block pasted as a string (e.g. `curl -sI` output). Use this to audit a local server the remote MCP cannot reach."

changedInput schema / properties / url / description

Previous value: -"Full public URL to check (e.g. https://example.com). The server cannot reach localhost/private IPs — use `headers` for those."New value: +"Optional. Full public URL to check (e.g. https://example.com). Omit it entirely when using `headers`. The server cannot reach localhost/private IPs."

Changed4 schema fields changedJun 23, 2026

addedInput schema / properties / headers

Added value: +{
+  "description": "Alternative to `url`: the response headers to grade, either as an object {\"strict-transport-security\": \"max-age=...\", ...} or as the raw header block pasted as a string (e.g. `curl -sI` output). Use this to audit a local server the remote MCP cannot reach."
+}

changedInput schema / properties / url / description

Previous value: -"Full URL to check (e.g. https://example.com)"New value: +"Full public URL to check (e.g. https://example.com). The server cannot reach localhost/private IPs — use `headers` for those."

removedInput schema / required
```
Removed value: -[
-  "url"
-]
```
addedOutput schema / properties / source
```
Added value: +{}
```

Changed1 schema field changedJun 21, 2026

addedOutput schema / properties

Added value: +{
+  "details": {},
+  "fix": {},
+  "grade": {},
+  "header": {},
+  "headers_checked": {
+    "type": "number"
+  },
+  "key": {},
+  "missing": {},
+  "missing_count": {
+    "type": "number"
+  },
+  "overall_grade": {},
+  "score": {},
+  "url": {},
+  "value": {},
+  "weak": {},
+  "weak_count": {
+    "type": "number"
+  },
+  "weight": {}
+}

Changed1 schema field changedJun 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedMay 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare a read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds genuinely behavioral context beyond that: the A–F grading scheme, the fixed set of ten headers, the 0–100 score, and the reachability limitation for private targets; it loses a point only because the return-value sentence partly duplicates the existing output schema.

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 the url/headers split are front-loaded in the first sentence, and the localhost fallback closes usefully. The long enumeration of ten header names and the return-format sentence are somewhat redundant with the schema and output schema, but they are not padding.

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?

With an output schema, full annotation coverage, and 100% schema description coverage, the description only needs to cover purpose, routing, and edge cases, which it largely does. The remaining gap is that both parameters are optional and the description never says what happens if neither `url` nor `headers` is supplied.

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 `url` and `headers` are already fully documented, including accepted formats and the localhost caveat. The description restates the same guidance rather than adding new meaning, so the baseline of 3 is appropriate.

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 states a specific verb and resource: analysing HTTP security headers of a URL or pasted header block, and enumerates exactly which headers are graded. It is clear what the tool does, but it never differentiates itself from overlapping siblings such as `web_security_audit`, `cors_checker`, or `parse_http_headers`, so an agent must infer the boundary.

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?

It gives an explicit routing rule: use `url` for public targets, but pass `headers` instead for localhost/private targets the remote server cannot reach. That is a concrete when-to-use condition, though it offers no guidance on when to prefer this tool over the broader `web_security_audit` sibling.

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

All IA-QA — 152 QA & Dev Tools for AI Agents 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.