About Http Headers X402
Http Headers X402 is an MCP server and pay-per-call API for auditing HTTP response headers. It returns a security score, header checks, server and caching details, and recommendations for security and configuration reviews.
Key features
- 01HTTP header security score
- 02HSTS and CSP checks
- 03Server and caching detection
- 04JSON audit with recommendations
- 05x402 USDC pay-per-call
Use cases
- 01Audit a URL's security headers
- 02Verify headers after deployment
- 03Review caching configuration
MCP support
Exposes the `network_analyze_headers` tool to MCP clients. It accepts a URL and returns a JSON header audit.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://http-headers.api.klymax402.com/mcpclaude mcp add --transport sse http-headers-x402 https://http-headers.api.klymax402.com/mcp{"mcpServers":{"http-headers-x402":{"type":"sse","url":"https://http-headers.api.klymax402.com/mcp"}}}Open in Cursor{"servers":{"http-headers-x402":{"type":"sse","url":"https://http-headers.api.klymax402.com/mcp"}}}Open in VS Code{"mcpServers":{"http-headers-x402":{"type":"sse","url":"https://http-headers.api.klymax402.com/mcp"}}}{"mcpServers":{"http-headers-x402":{"serverUrl":"https://http-headers.api.klymax402.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEHTTP Headers Analyzer API
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.):
{
"mcpServers": {
"http-headers": {
"url": "https://http-headers.api.klymax402.com/mcp"
}
}
}
Quickstart -- HTTP (x402)
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
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
network_analyze_headers | POST | /api/analyze | $0.003 | Analyze 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
| Name | Type | Required | Description |
|---|---|---|---|
url | string | yes | Full URL to analyze (e.g. https://example.com) |
Example response:
{"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.
- Catalog: https://klymax402.com/llms.txt
- Full API reference: https://klymax402.com/llms-full.txt
- Live stats: https://klymax402.com/stats
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.