Uptime Check
Check whether a URL is up: status code, latency, redirects, TLS and server headers.
uptime-check Example
{
"tls": true,
"url": "https://example.com",
"error": "fetch failed",
"status": "down",
"checked_at": "2026-03-09T20:03:13.819Z",
"latency_ms": 22,
"status_code": null
} Inputs
| Field | Type | Required | What it is |
|---|---|---|---|
url | string | Yes | — |
method | string | No | — |
timeout_ms | integer | No | — |
Output fields
How reliably each field appears in a successful answer.
| Field | Type | Appears |
|---|---|---|
status | string | Always (present in every successful answer) |
latency_ms | integer | Always (present in every successful answer) |
redirected | boolean | Always (present in every successful answer) |
status_code | integer | Always (present in every successful answer) |
How to call it
The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.
# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
-H "Authorization: Bearer $STRALE_API_KEY" \
-H 'Content-Type: application/json' \
-d '{
"capability_slug": "uptime-check",
"inputs": {
"url": "https://strale.dev"
},
"max_price_cents": 2
}' {
"tool": "strale_execute",
"arguments": {
"slug": "uptime-check",
"inputs": {
"url": "https://strale.dev"
},
"max_price_cents": 2
}
} import { Strale } from "straleio";
const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
capability_slug: "uptime-check",
inputs: {
"url": "https://strale.dev"
},
max_price_cents: 2,
}); import os
from straleio import Strale, DoRequest
strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
capability_slug="uptime-check",
inputs={
"url": "https://strale.dev",
},
max_price_cents=2,
)) # No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i 'https://api.strale.io/x402/v2/uptime-check?url=https%3A%2F%2Fstrale.dev' Limitations
One check does not measure historical or regional uptime
Single point-in-time check from one server location — does not represent historical uptime or multi-region availability
What to do instead: Schedule periodic checks and compute uptime percentage over time rather than relying on a single probe
HTTP 200 can mask missing pages
Only the HTTP status code is inspected. A removed listing or soft-404 page served with HTTP 200 (or even a literal 404 response) is reported as status "up" — this capability answers "does the server respond?", not "does this page still exist?".
What to do instead: Use page-exists to check whether a specific page still resolves to real content.
Related tools
- Mail Server Lookup €0.02
- Page Existence Check €0.02
- Port Check €0.05
- Redirect Trace €0.05
- Robots.txt Parser €0.02
- Sitemap Parser €0.05