Observe
Independent collection jobs run continuously with paced requests and adaptive retries.
SERVICE AVAILABILITY INTELLIGENCE
Eine API für die Dienste, auf die es ankommt. Status, regionale Signale und Verlauf für dein Produkt, Dashboard oder deine KI.
Beobachtete Dienste, keine Partnerschaften.
01 / SIGNAL EXPLORER
Echte gespeicherte Beobachtungen. Wähle einen Dienst für seinen Verlauf.
Reported availability signals, not direct uptime measurements. Regional conditions may differ. Missing and stale data remain unknown.
02 / THE SIGNAL PATH
Independent collection jobs run continuously with paced requests and adaptive retries.
Regional observations become consistent statuses with timestamps and explicit freshness.
REST, MCP, and SDKs read the same stored snapshots without triggering collection.
03 / BUILT FOR BUILDERS
Katalog durchsuchen, einen Dienst prüfen oder mehrere Statuswerte abrufen. Jede Antwort enthält Zeitstempel und Aktualität.
OpenAPI reference ↗/v1/servicesGET /v1/statusGET /v1/statusesGET /v1/summaryGET /v1/historyGET /v1/statsGET /v1/incidentscurl https://api.uptimescout.com/v1/status \ -G --data-urlencode "service=github" \ -H "Authorization: Bearer $EVELODE_LICENSE_KEY"
{
"status": "ok",
"data_type": "cached_observations",
"service": {
"id": "github",
"status": "unknown",
"observed_at": null,
"stale": true,
"signal": "reported_availability"
}
}
AI ↔ UptimeScout04 / MODEL CONTEXT PROTOCOL
Sieben schreibgeschützte MCP-Werkzeuge für Dienstsignale und Verlauf. Dieselbe Evelode-Lizenz gilt überall.
Streamable HTTP · Bearer authentication · Read-only tools
https://mcp.uptimescout.com/mcpuptimescout_statusuptimescout_summaryuptimescout_history+ 4 tools05 / SIMPLE BY DESIGN
Wähle Anfragevolumen und Verlauf. Alle Tarife enthalten Katalog, Sammelabfragen, REST und MCP.
$4.99/ Monat
$9.99/ Monat
$19.99/ Monat
$39.99/ Monat
A batch call counts as one request within the plan’s batch size. Payments, subscriptions, upgrades, and license management are handled by Evelode.com. History accumulates from launch; a longer plan does not create earlier observations.
No. Collection runs independently. Your request reads the latest stored snapshot, so high client traffic never multiplies collection traffic.
No. These are reported availability observations. Check the region, timestamp, and freshness. They are useful signals, not a measured uptime guarantee.
At Evelode.com. One UptimeScout license covers REST requests, MCP tool calls, and SDK requests. Each successful data call uses one request.
The collector retries with backoff. Older observations become stale, and public status becomes unknown after the freshness window. We never turn missing data into a healthy status.
