Security Headers + TLS Audit

● Active

io.github.theharrisontruong-web/secheaders-audit

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

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "secheaders-audit": {
      "url": "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http secheaders-audit https://secheaders-al6bxcngia-ue.a.run.app/mcp
VS Code
code --add-mcp '{"name":"secheaders-audit","type":"http","url":"https://secheaders-al6bxcngia-ue.a.run.app/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Security & Identity
Version
1.0.0
Registry
active
Published
11/17/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Security Headers + TLS Audit is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 6 days ago (Nov 15, 2026), 1 open issues.
Official registry
Active
Published as io.github.theharrisontruong-web/secheaders-audit in the official MCP registry, version 1.0.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to secheaders-al6bxcngia-ue.a.run.app: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Working138 msprotocol 2025-06-18tools

The endpoint answered the MCP handshake as "secheaders-audit" and listed 2 tools. Answering since Nov 18, 2026.

Context cost ≈ 692 tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 2 tools.

Tools (2)

  • audit_secheaders1 param

    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.

    Show parameters
    • urlstringrequiredWebsite URL to audit (https preferred), e.g. https://example.com
  • audit_secheaders_lite1 param

    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.

    Show parameters
    • urlstringrequiredWebsite URL to audit (https preferred), e.g. https://example.com

Checked by Serverdex with a plain initialize + tools/list call to secheaders-al6bxcngia-ue.a.run.app/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 15, 2026
License
MIT

Python

From the README

Paid Agent APIs — Storefront Grader & GEO Audit Two pay-per-call APIs built for AI agents. No accounts, no API keys, no subscriptions — payment is the auth. Each call is paywalled with the x402 protocol: send a request, get an HTTP 402 with payment requirements, pay in USDC on Base, get the result. Operated by Harrison Truong · Contact: theharrisontruong@gmail.com 1. AI Storefront Readiness Grader — $1.00 / call Grades any storefront URL A–F across 20 weighted conversion-readiness checks (checkout friction, trust signals, mobile readiness, page performance basics, merchandising completeness, and more) and returns the grade plus the failing checks. 2. GEO Audit — $1.50 / call Scores any URL's visibility to AI search engines (ChatGPT, Perplexity, Claude, Google AI Overviews) across 20 weighted checks — crawlability for AI bots, structured data, content extractability, entity signals — and returns the score plus concrete fixes. 3.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://secheaders-al6bxcngia-ue.a.run.app/mcp

The most-starred Security & Identity servers in the index, with their live-check result.

ServerStarsLast pushLive check
Handsy AI5,215Nov 2026Local / not checked
HOL Guard1,118Nov 2026Local / not checked
SonarQube MCP Server689Nov 2026Local / not checked
MCP Ssh Manager545Nov 2026Local / not checked
Security Detections529Nov 2026Local / not checked

Security Headers + TLS Audit: questions people ask

Is Security Headers + TLS Audit a remote or a local MCP server?
According to its entry in the official MCP registry, Security Headers + TLS Audit ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Security Headers + TLS Audit need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Security Headers + TLS Audit safe to use?
Looks healthy: Security Headers + TLS Audit is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Security Headers + TLS Audit still maintained?
Active: the repository's last commit 6 days ago. Last push Nov 15, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
What tools does Security Headers + TLS Audit expose?
2 tools as listed by the server itself during the live check, including audit_secheaders, audit_secheaders_lite. The full list with parameters is in the Live check section above.
How do I add Security Headers + TLS Audit to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.

More from theharrisontruong-web

All 12 servers by theharrisontruong-web →
  1. NEET RadarNEET narrative radar + canonical-or-clone verify for Solana mints. $0.02 / $0.005 via x402.
  2. Token Pressure + Holder HealthBuying-pressure ladder + holder health for Solana memecoins. $0.02/call via x402.
  3. Cluster & ConsensusTracked-wallet cluster detection + 0-100 consensus score for Solana/Base tokens. $0.02/call.
  4. Racket CheckRacket check for local service sites: CLEAN / PLAN_PUSH / RACKET verdict. $1.00/call via x402.
Browse all Security & Identity →

Add the badge to your site

Show visitors that Security Headers + TLS Audit is listed here — it’s also the link we check for a free listing.

Security Headers + TLS Audit — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-theharrisontruong-web-secheaders-audit?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Security Headers + TLS Audit — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Security Headers + TLS Audit — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-theharrisontruong-web-secheaders-audit?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-theharrisontruong-web-secheaders-audit) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-theharrisontruong-web-secheaders-audit) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-theharrisontruong-web-secheaders-audit)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-theharrisontruong-web-secheaders-audit"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-theharrisontruong-web-secheaders-audit"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-theharrisontruong-web-secheaders-audit"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).