mcpcost

io.github.kriton-dev/http-security-headers

HTTP Header Policy Check — HSTS, CSP & Frame Declarations

Is the HTTP Header Policy Check MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.

Check seven declared HTTP security header families without returning raw values

needs auth probed 2026-11-14 · unchanged since 2026-11-11 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Missing or invalid access token. Pass an Apify API token in the 
Endpoint
https://mcp.apify.com/?tools=hermeskd/http-security-headers (streamable-http)
Host
mcp.apify.com
Getting access
OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.apify.com/?tools=hermeskd/http-security-headers registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server console-backend.apify.com, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:device_code.
Scopes full_api_access.
Read from the server's public OAuth metadata, without a token. Method.
Website
https://apify.com/hermeskd/http-security-headers
Registry
active, updated 2026-11-06 · registry entry

Compare this server with others.

More servers

Other registry entries on mcp.apify.com, the ones next to this name; all of them.

Servers that mention security.

Badge for the README

mcpcost: needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.