Skip to content

Security Headers + TLS Audit

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

build.protocol_tooling.mcp

What our last check of Security Headers + TLS Audit found

Stork connects to every MCP server it lists that has a public endpoint and records what came back: every week when the server answers without an account, every month otherwise. These are the results for Security Headers + TLS Audit.

Result
AnsweredThe endpoint completed an MCP handshake with no account.
Last checked
Tools listed
2
Context cost of the tool definitions
About 641 tokensWhat Security Headers + TLS Audit adds to a model's context before you ask anything, unless your client loads tools on demand. Estimated from the length of the definitions at 4 characters a token.
Test call
Tool asked for a keyOn 17 November 2026 we called one read-only tool, audit_secheaders, once with a plain test input. Security Headers + TLS Audit lists its tools without an account, but this tool would not run without a key or account from the publisher.

Changes to the tool definitions

We have seen no change to Security Headers + TLS Audit's tool definitions since we began checking it.

A check is one initialize request and one tools/list request from Stork's servers, with no account. Where a server answers without an account we also call one read-only tool once. Neither can tell you that every tool does its job or that the server is safe to connect.

Install Security Headers + TLS Audit in your MCP client

Security Headers + TLS Audit is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.

  1. Locate your client's MCP config file.
    • Cursor: ~/.cursor/mcp.json
    • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
    • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
    • VS Code: Settings → Extensions → MCP
    • Windsurf: Settings → MCP Servers
  2. Add Security Headers + TLS Audit to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing mcpServers object.
  3. Restart your client so it picks up the new server.
  4. Verify — ask the assistant to list available tools; Security Headers + TLS Audit's tools should appear.
{
  "mcpServers": {
    "security-headers---tls-audit": {
      "url": "https://secheaders-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}

Maintain Security Headers + TLS Audit, or spotted a wrong detail on this page? Report a problem and we will correct it. Corrections are free.

Install Security Headers + TLS Audit in Cursor

Open ~/.cursor/mcp.json in your editor, paste the snippet above into mcpServers, save, and restart Cursor. Security Headers + TLS Audit will show up in the assistant's tool list on next launch.

Install Security Headers + TLS Audit in Claude Desktop (macOS)

Open ~/Library/Application Support/Claude/claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (macOS). Security Headers + TLS Audit will show up in the assistant's tool list on next launch.

Install Security Headers + TLS Audit in Claude Desktop (Windows)

Open %APPDATA%\Claude\claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (Windows). Security Headers + TLS Audit will show up in the assistant's tool list on next launch.

Install Security Headers + TLS Audit in VS Code

Open Settings → Extensions → MCP in your editor, paste the snippet above into mcpServers, save, and restart VS Code. Security Headers + TLS Audit will show up in the assistant's tool list on next launch.

Tools exposed by Security Headers + TLS Audit

Once installed, Security Headers + TLS Audit exposes the following MCP tools to your AI assistant. Each tool can be called directly by the assistant whenever its capability is relevant to your prompt.

  • audit_secheaders

    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 v

  • audit_secheaders_lite

    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 fixe

Transport

Security Headers + TLS Audit supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.

streamable-http

Other Model Context Protocol servers in the same space as Security Headers + TLS Audit. Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.

Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.