MCP.so
ログイン

Http Headers X402

@Br0ski777

Http Headers X402 について

Analyze HTTP response headers -- security score, HSTS/CSP check, server detection, caching config. Score 0-100. -- x402 micropayment API + MCP server for AI agents

基本情報

カテゴリ

開発者ツール

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

Br0ski777

投稿者

Br0ski777

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "http-headers": {
      "url": "https://http-headers-production.up.railway.app/mcp",
      "transport": "sse"
    }
  }
}

ツール

1

POST

概要

What is Http Headers X402?

Http Headers X402 is an MCP server that analyzes HTTP response headers of a given URL. It returns a security score (0–100), checks for HSTS, CSP, X‑Frame‑Options, and other security headers, detects the server software, and reports caching configuration. Payment is handled per‑call via the x402 protocol (USDC on Base L2) — no API key, no signup, no rate limits. It is part of the klymax402 marketplace of 100 x402 micropayment APIs for AI agents.

How to use Http Headers X402?

Add the server URL to your MCP client configuration (Claude Desktop, Cursor, ElizaOS, etc.) using the endpoint https://http-headers.api.klymax402.com/mcp. The server exposes one tool: network_analyze_headers. To call it from an x402‑aware client (e.g., @x402/fetch, x402-agent-tools, ATXP), send a POST request to https://http-headers.api.klymax402.com/api/analyze with a JSON body containing the url parameter. The client automatically handles the 402 payment challenge, signs it, and retries the request.

Key features of Http Headers X402

  • Security score from 0 to 100 based on headers
  • Checks HSTS, CSP, X‑Frame‑Options, X‑Content‑Type‑Options
  • Detects server software (e.g., nginx, Apache)
  • Reports caching configuration (Cache‑Control, ETag)
  • Pay‑per‑call via x402 (USDC on Base L2)
  • No API key, no signup, no rate‑limit walls

Use cases of Http Headers X402

  • Security audits of website HTTP response headers
  • DevOps monitoring to verify header configuration after deployment
  • Compliance checks for security header best practices
  • Automated reconnaissance of server software and caching behavior

FAQ from Http Headers X402

How does payment work?

The server uses the x402 protocol. When you call the API without payment, it returns a 402 Payment Required response containing a payment challenge. An x402‑aware client automatically signs the challenge, pays USDC on Base L2, and retries the request. No API key or signup is needed.

What is the cost per request?

Each call to network_analyze_headers costs $0.001 (USDC on Base L2).

Can Http Headers X402 check SSL certificates?

No. The tool analyzes only HTTP response headers. For SSL certificate checks, use the separate security_check_ssl API (also part of the klymax402 marketplace).

What parameters does the tool require?

It requires one required parameter: url (string) — the full URL to analyze, e.g., https://example.com.

What runtime dependencies are needed?

The only requirement is an MCP client that supports remote MCP servers (e.g., Claude Desktop, Cursor, ElizaOS) or an HTTP client that understands the x402 payment protocol (like @x402/fetch or x402-agent-tools).

コメント

「開発者ツール」の他のコンテンツ