# Security Headers + TLS Audit (remote · secheaders-al6bxcngia-ue.a.run.app)

Audits security headers + TLS (HSTS, CSP, cert, cookies) for any site. $1.50/call via x402.

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

## Components

- remote · `secheaders-al6bxcngia-ue.a.run.app`: 72/100 (this document), [markdown](https://verifymcp.io/servers/theharrisontruong-web-secheaders-audit/secheaders-al6bxcngia-ue.md), [page](https://verifymcp.io/servers/theharrisontruong-web-secheaders-audit/secheaders-al6bxcngia-ue)

## Channel facts

- Endpoint: `https://secheaders-al6bxcngia-ue.a.run.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 559 tokens (~279/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Security Headers + TLS Audit MCP server?

Security Headers + TLS Audit is a hosted endpoint at https://secheaders-al6bxcngia-ue.a.run.app/mcp, so there is nothing to install locally. 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 --transport http theharrisontruong-web-secheaders-audit 'https://secheaders-al6bxcngia-ue.a.run.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theharrisontruong-web-secheaders-audit": {
      "url": "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theharrisontruong-web-secheaders-audit": {
      "type": "http",
      "url": "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theharrisontruong-web-secheaders-audit]
url = "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theharrisontruong-web-secheaders-audit": {
      "type": "remote",
      "url": "https://secheaders-al6bxcngia-ue.a.run.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theharrisontruong-web-secheaders-audit --url 'https://secheaders-al6bxcngia-ue.a.run.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theharrisontruong-web-secheaders-audit:
    url: "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theharrisontruong-web-secheaders-audit": {
      "Transport": "http",
      "Url": "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theharrisontruong-web-secheaders-audit -t streamable-http -u 'https://secheaders-al6bxcngia-ue.a.run.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theharrisontruong-web-secheaders-audit": {
      "type": "http",
      "url": "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-19 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 71, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 71)

First indexed and scored.

## MCP tools (2)

### `audit_secheaders` (~422 tokens)

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.

Input parameters:

- `url` (string, required): Website URL to audit (https preferred), e.g. https://example.com

### `audit_secheaders_lite` (~137 tokens)

FREE lite security headers + TLS audit of a website URL. Runs the same 11 checks as audit_secheaders but returns top-line results only: 0-100 score, A-F grade, exposure-risk level, check counts, and the titles of the top gaps — detail is capped (no per-check evidence, no site block, no detailed fixes). Use this to triage whether a site needs the full audit_secheaders report, or call audit_secheaders directly for the complete evidence-backed scan.

Input parameters:

- `url` (string, required): Website URL to audit (https preferred), e.g. https://example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theharrisontruong-web-secheaders-audit/secheaders-al6bxcngia-ue#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71

## Common questions

### What is the Security Headers + TLS Audit MCP server?

Security Headers + TLS Audit is an MCP server listed in the public MCP registry as io.github.theharrisontruong-web/secheaders-audit. Audits security headers + TLS (HSTS, CSP, cert, cookies) for any site. $1.50/call via x402. This page covers its hosted endpoint (https://secheaders-al6bxcngia-ue.a.run.app/mcp).

### Is the Security Headers + TLS Audit MCP server safe to use?

Security Headers + TLS Audit scores 72 out of 100 on VerifyMCP. 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 + TLS Audit MCP server expose?

Security Headers + TLS Audit exposes 2 tools: audit_secheaders, audit_secheaders_lite. Their descriptions and schemas cost roughly 559 tokens of context every time the server is loaded.

### Does the Security Headers + TLS Audit MCP server require authentication?

No. We connected to Security Headers + TLS Audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Security Headers + TLS Audit MCP server still maintained?

Security Headers + TLS Audit 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 did VerifyMCP test on the Security Headers + TLS Audit MCP server?

VerifyMCP ran 13 checks on Security Headers + TLS Audit, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://secheaders-al6bxcngia-ue.a.run.app/mcp
- Repository: https://github.com/theharrisontruong-web/agent-apis
- Website: https://secheaders-al6bxcngia-ue.a.run.app/
- Changelog RSS feed: https://verifymcp.io/servers/theharrisontruong-web-secheaders-audit/secheaders-al6bxcngia-ue.xml
- Changelog JSON feed: https://verifymcp.io/servers/theharrisontruong-web-secheaders-audit/secheaders-al6bxcngia-ue/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theharrisontruong-web-secheaders-audit/secheaders-al6bxcngia-ue.json
- HTML version of this page: https://verifymcp.io/servers/theharrisontruong-web-secheaders-audit/secheaders-al6bxcngia-ue
