ISHOB

Uptime & TLS Check

Is a URL up: status, response time, redirects, security headers and TLS expiry.

Uptime / API health check: is a URL up, HTTP status, response time, redirect chain, headers and security headers (edge), plus the TLS certificate (issuer, expiry date, days remaining, SAN, verification errors). A down target is a valid answer.

What agents use it for

  • Health-check an API before depending on it
  • Alert on expiring TLS certificates
  • Debug redirect chains

Parameters

ParameterTypeRequiredDescription
urlstringyesPublic http(s) URL
method"HEAD" | "GET" · default "HEAD"noHTTP method used for the check
check_sslboolean · default truenoAlso inspect the TLS certificate (issuer, expiry, verification)
follow_redirectsboolean · default truenoFollow HTTP redirects to the final URL

Call it

MCP · tools/calljson
{
  "name": "ping_status",
  "arguments": {
    "url": "https://api.example.com/health"
  }
}
HTTPSreturns 402, then pay with an x402 client
curl -i -X POST "https://api.ishob.com/v1/ping-status" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://api.example.com/health"}'

Paid with x402: the first call returns HTTP 402 with the price; an x402 client (for example @x402/fetch or @x402/mcp) signs a USDC payment and retries. Calls that fail are not charged. Connect the MCP server: setup for Claude, Cursor and other clients.

More web data & browser tools