Observe
Independent collection jobs run continuously with paced requests and adaptive retries.
SERVICE AVAILABILITY INTELLIGENCE
Una API para los servicios de los que dependes. Estado, señales regionales e historial para tu producto, panel o IA.
Servicios observados, sin afiliaciones.
01 / SIGNAL EXPLORER
Observaciones reales guardadas. Selecciona un servicio para consultar su historial.
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
Busca servicios, consulta un estado o solicita varios. Cada respuesta incluye fecha y frescura.
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
Siete herramientas MCP de solo lectura para señales e historial. La misma licencia Evelode en todas partes.
Streamable HTTP · Bearer authentication · Read-only tools
https://mcp.uptimescout.com/mcpuptimescout_statusuptimescout_summaryuptimescout_history+ 4 tools05 / SIMPLE BY DESIGN
Elige peticiones e historial. Todos los planes incluyen catálogo, consultas por lotes, REST y MCP.
$4.99/ mes
$9.99/ mes
$19.99/ mes
$39.99/ mes
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.
