# io.github.CloudCorpRecords/headguard (npm · @reneturcios/headguard)

Paste HTTP response headers and get seven security checks with copy-paste fixes. No fetching.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/headguard`: 67/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-headguard/reneturcios-headguard.md), [page](https://verifymcp.io/servers/cloudcorprecords-headguard/reneturcios-headguard)
- oci · `ghcr.io/cloudcorprecords/headguard`: 40/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-headguard/ghcr-io-cloudcorprecords-headguard.md), [page](https://verifymcp.io/servers/cloudcorprecords-headguard/ghcr-io-cloudcorprecords-headguard)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/headguard`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1459 tokens (~364/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: 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.

## Install

### How do I install the io.github.CloudCorpRecords/headguard MCP server?

io.github.CloudCorpRecords/headguard runs locally as an npm package, launched with npx -y @reneturcios/headguard mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-headguard -- npx -y @reneturcios/headguard mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-headguard": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/headguard",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-headguard": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/headguard",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-headguard -- npx -y @reneturcios/headguard mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-headguard": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/headguard",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-headguard --command npx --arg -y --arg @reneturcios/headguard --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-headguard:
    command: "npx"
    args: ["-y", "@reneturcios/headguard", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-headguard": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/headguard",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-headguard -t stdio -c npx -a -y @reneturcios/headguard mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-headguard": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/headguard",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-17 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-16 (score 52)

First indexed and scored.

## MCP tools (4)

### `analyze_headers` (~1006 tokens)

Check raw HTTP response headers from a deployment you already operate. Returns the same object as POST /v1/analyze. Unknown fields are ignored. A url field is not fetched. Nothing is stored. Nothing is for sale.

Input parameters:

- `config_text` (string): Optional config text. Not copied into the response. When platform is caddy and this is non-empty, GLC-HSTS-MISSING includes config_header present or absent for one Caddy Strict-Transport-Security for…
- `headers_raw` (string, required): Raw HTTP response headers from a deployment this agent already operates, including an optional status line, as curl -sI prints them. This server does not request a URL.
- `paths_tested` (array): Optional paths. Accepted and not checked. This server does not request them.
- `platform` (string): Platform whose config the caller can edit. A fix snippet is attached only for caddy, nginx, vercel, netlify, or nextjs. Any other declared platform, or an omitted platform, returns fix null. This ser…

### `explain_finding` (~107 tokens)

Explain one finding id from the seven. Returns id, severity, why, and answer_page. answer_page is the CSP and clickjacking page for GLC-CSP-MISSING and GLC-FRAME-MISSING, and null for the other five. Unknown fields are ignored. A url field is not fetched. Nothing is stored. Nothing is for sale.

Input parameters:

- `id` (string, required): One finding id from the seven. Unknown fields are ignored. A url field is not fetched.

### `get_fix` (~194 tokens)

Return the registry snippet for one finding id and one platform. The platforms are caddy, nginx, vercel, netlify, nextjs. The result is id and fix. fix has platform, snippet, source_url, and last_verified, and note when the registry file has one. An omitted or unknown platform returns fix null. Unknown fields are ignored. A url field is not fetched. source_url is not fetched. Nothing is stored. Nothing is for sale.

Input parameters:

- `id` (string, required): One finding id from the seven. Unknown fields are ignored. A url field is not fetched.
- `platform` (string): Platform whose config the caller can edit. caddy, nginx, vercel, netlify, nextjs returns that registry snippet. Any other value, or an omitted platform, returns fix null. This server does not guess t…

### `report_feedback` (~152 tokens)

Report one finding id and one outcome. The outcomes are false_positive, fix_worked, fix_failed. The result is id, outcome, and stored false. Nothing is written: no file, no counter, and no log line. A note, a url, and headers are ignored. A url field is not fetched. This server does not guess the platform from the Server header. Nothing is for sale.

Input parameters:

- `id` (string, required): One finding id from the seven. A note, a url, and headers are ignored. A url field is not fetched.
- `outcome` (string, required): Exactly one of false_positive, fix_worked, fix_failed. Any other value is unknown_outcome. Nothing is written.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-headguard/reneturcios-headguard#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 67
- 2026-11-17: 67
- 2026-11-16: 52

## Common questions

### What is the io.github.CloudCorpRecords/headguard MCP server?

io.github.CloudCorpRecords/headguard is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/headguard. Paste HTTP response headers and get seven security checks with copy-paste fixes. No fetching. This page covers its npm package (@reneturcios/headguard).

### Is the io.github.CloudCorpRecords/headguard MCP server safe to use?

io.github.CloudCorpRecords/headguard scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/headguard MCP server expose?

io.github.CloudCorpRecords/headguard exposes 4 tools: analyze_headers, explain_finding, get_fix, report_feedback. Their descriptions and schemas cost roughly 1,459 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/headguard MCP server still maintained?

io.github.CloudCorpRecords/headguard is still listed as active in the MCP registry. We last reached this channel on 21 November 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 io.github.CloudCorpRecords/headguard MCP server under?

io.github.CloudCorpRecords/headguard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/headguard MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/headguard, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/headguard: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/headguard
- Socket report: https://socket.dev/npm/package/@reneturcios/headguard
- Repository: https://github.com/CloudCorpRecords/headguard
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-headguard/reneturcios-headguard.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-headguard/reneturcios-headguard/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-headguard/reneturcios-headguard.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-headguard/reneturcios-headguard
