HTTP Headers Analyzer API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

HTTP header analysis — security headers, cache, server detection. x402 micropayment.

VerifiedSSEWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that audits a URL's HTTP response headers for security, caching and server details, returning a 0-100 score and paid per call.

What you can do
  • Analyze the HTTP response headers of a given URL and return a JSON audit.
  • Check security headers such as HSTS, CSP, X-Frame-Options, X-Content-Type-Options and Referrer-Policy.
  • Report the detected server and caching configuration (Cache-Control, ETag).
  • Return a 0-100 security score plus recommendations for missing headers.
When to use it
Useful for security audits, DevOps monitoring, compliance checks, or verifying header configuration after a deployment, when an assistant needs a quick header assessment of a live URL.
Requirements
A remote MCP client pointed at the hosted endpoint; no API key or signup. Each call is paid per use via x402 in USDC on Base L2, so an x402-aware client with a funded wallet is needed to complete the payment challenge.
Before you install
Calls cost money: $0.003 per analysis, settled in USDC on Base through an x402 payment challenge, so a wallet and spending are involved. The URL you submit is sent to a third-party service, and the README notes it is part of a larger commercial API marketplace.

Installation

In SourceWeft

  1. Open HTTP Headers Analyzer API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fhttp-headers/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "http-headers-analyzer-api": {
      "type": "sse",
      "url": "https://http-headers.api.klymax402.com/mcp"
    }
  }
}

README

HTTP Headers Analyzer API

[MCP Server] [x402] [License: MIT]

Analyze HTTP response headers -- security score, HSTS/CSP check, server detection, caching config. Score 0-100. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "http-headers": {      "url": "https://http-headers.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl -X POST "https://http-headers.api.klymax402.com/api/analyze" \  -H "Content-Type: application/json" \  -d '{"url":"https://example.com"}'# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
network_analyze_headersPOST/api/analyze$0.003Analyze HTTP response headers for a URL

network_analyze_headers

Use this when you need to analyze HTTP response headers of a URL for security and configuration. Returns a full header audit in JSON.

Parameters

NameTypeRequiredDescription
urlstringyesFull URL to analyze (e.g. https://example.com)

Example response:

json
{"url":"https://example.com","securityScore":85,"securityHeaders":{"hsts":true,"csp":true,"xFrameOptions":true,"xContentType":true,"referrerPolicy":false},"server":"nginx","caching":{"cacheControl":"max-age=3600","etag":true},"recommendations":["Add Referrer-Policy header"]}

When to use: security audits, DevOps monitoring, compliance checks, and verifying proper header configuration after deployment.

Not for: SSL certificate check (use security_check_ssl), web scraping (use web_scrape_to_markdown), GDPR compliance (use compliance_scan_gdpr).

Example agent prompts

  • "Analyze HTTP response headers of a URL for security and configuration"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit f76b8b9

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts