Security Headers
OCI · GHCR.IO/BASITALISANDHU/MCP-SECURITY-HEADERS
Fetch a URL's response headers and grade CSP, HSTS, X-Frame-Options and related security headers.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of OCI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 527 tokens (~175/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_url_headers" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 2 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 83 functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 0 functional
- First check of Schema quality: good functional
- 13 Oct 26 0
- Package version: 0.2.0 → 0.2.1 functional
- 12 Oct 26 0
- Package version: 0.1.1 → 0.2.0 functional
- 7 Oct 26 20
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed oci/ghcr.io/basitalisandhu/mcp-security-headers@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | basitalisandhu/dev-mcp-servers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/basitalisandhu/dev-mcp-servers/.github/workflows/publish-github-packages.yml@refs/tags/v0.2.1 |
| Rekor log index | 3244679281 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:e13ea1c6dca71e1a2b2d2bef8097adb35bd8eccd9c2ff062d8299f46dd21dc9c |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_url_headers Fetch and grade a URL's security headers ~173
Send a HEAD request (GET when the server answers 405 or 501, or when method is GET) to a public http or https URL, follow up to max_redirects redirects (default 5) and grade the final response's security headers. Returns the final URL, status, redirect chain, every response header, and per-header pass/warn/fail/info checks with explanations, recommendations and an overall grade from A+ to F. Refuses URLs whose host is localhost, a .local or .internal name, or resolves to a private, loopback, link-local or cloud-metadata address. The response body is never downloaded.
| Name | Type | Req | Description |
|---|---|---|---|
| max_redirects | integer | – | Default 5. |
| method | string | – | Default HEAD. |
| url | string | yes | Absolute http:// or https:// URL. |
No output schema declared.
No examples provided.
explain_header Explain a security header ~83
Describe what one response header does, the recommended value and a reference link. Headers: content-security-policy, strict-transport-security, x-frame-options, x-content-type-options, referrer-policy, permissions-policy, cross-origin-opener-policy, cross-origin-resource-policy, x-xss-protection, server, x-powered-by, set-cookie.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | – |
No output schema declared.
No examples provided.
grade_headers Grade a supplied header set ~100
Grade response headers you already have, without any network access. Pass headers as an object of name to value (names are case-insensitive; Set-Cookie may be an array). Returns the same per-header checks and overall grade as check_url_headers. Set https to false when the response came over plain HTTP.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | yes | Response headers, name to value. |
| https | boolean | – | Whether the response was served over HTTPS. Default true. |
No output schema declared.
No examples provided.
How do I install the Security Headers MCP server?
Security Headers runs locally as a container image, launched with docker run --rm -i ghcr.io/basitalisandhu/mcp-security-headers:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/basitalisandhu/mcp-security-headers
claude mcp add basitalisandhu-mcp-security-headers -- docker run --rm -i ghcr.io/basitalisandhu/mcp-security-headers:0.2.1
What is the Security Headers MCP server?
Security Headers is an MCP server listed in the public MCP registry as io.github.basitalisandhu/mcp-security-headers. Fetch a URL's response headers and grade CSP, HSTS, X-Frame-Options and related security headers. This page covers its container image (ghcr.io/basitalisandhu/mcp-security-headers).
Is the Security Headers MCP server safe to use?
Security Headers scores 49 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Security Headers MCP server expose?
Security Headers exposes 3 tools: check_url_headers, grade_headers, explain_header. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the Security Headers MCP server still maintained?
Security Headers is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Security Headers MCP server under?
Security Headers declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.