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
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | yes | Public http(s) URL |
method | "HEAD" | "GET" · default "HEAD" | no | HTTP method used for the check |
check_ssl | boolean · default true | no | Also inspect the TLS certificate (issuer, expiry, verification) |
follow_redirects | boolean · default true | no | Follow HTTP redirects to the final URL |
Call it
{
"name": "ping_status",
"arguments": {
"url": "https://api.example.com/health"
}
}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.