# HTTP Headers Analyzer API MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-br0ski777-http-headers
- Repository: https://github.com/Br0ski777/http-headers-x402
- Website: https://github.com/Br0ski777/http-headers-x402

## Install
- Endpoint: https://http-headers.api.klymax402.com/mcp
- Auth: Not captured

## Setup notes
- Remote endpoint: https://http-headers.api.klymax402.com/mcp

## Tools
- 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.

Returns: 1. allHeaders (raw key-value map) 2. securityScore (0-100) 3. securityHeaders (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy -- present/missing) 4. server software detected 5. caching config (Cache-Control, ETag, Expires) 6. recommendations array.

Example output: {"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"]}

Use this FOR security audits, DevOps monitoring, compliance checks, and verifying proper header configuration after deployment.

Do NOT use for SSL certificate check -- use security_check_ssl instead. Do NOT use for web scraping -- use web_scrape_to_markdown instead. Do NOT use for GDPR compliance -- use compliance_scan_gdpr instead. Endpoint: https://http-headers.api.klymax402.com/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.Br0ski777
- Version: 1.1.0
- Runtime: Sse
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: May 16, 2026
- Source: https://registry.modelcontextprotocol.io