API health check

Is this API endpoint healthy? Liveness check, response headers, and TLS certificate status in one pass.

When to use this pack

An agent needs to verify an API is up and properly configured before making production calls: is it reachable (status + latency), what do the response headers say (rate limits, auth requirements, CORS), and is the TLS cert valid and not expiring soon?

Tools in this pack

• HTTP check $0.003 POST /api/http-check Check any public URL: status code, latency, final URL after redirects, and response headers. The uptime primitive for agent monitors.
• HTTP headers + security analysis $0.003 POST /api/http-headers Fetch a URL and return every response header plus a security analysis: HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/CORP/COEP. Scores 0–100 by presence, flags weak HSTS, and warns on Server/X-Powered-By identity leaks. SSRF-protected.
• TLS certificate $0.003 POST /api/tls-cert Inspect the TLS certificate of any public host: subject, issuer, validity window, days remaining, SANs, and SHA-256 fingerprint.

Workflow

1. Call http-check to verify the endpoint is reachable — status code, response time, redirect chain.
2. Call http-headers to inspect the response headers — rate limit headers, auth requirements, CORS policy, cache directives.
3. Call tls-cert with the host extracted from the URL to check certificate validity, issuer, expiry, and chain trust.

Run it in Claude

claude mcp add agent402 -s user -- npx -y agent402-mcp@latest

Then paste this prompt into Claude:

Check the health of https://api.github.com using Agent402's api-health skill pack: (1) http-check for liveness and latency, (2) http-headers for rate limits and security headers, (3) tls-cert for certificate status. Report whether the endpoint is production-ready.

← All skill packs