Observe
Independent collection jobs run continuously with paced requests and adaptive retries.
SERVICE AVAILABILITY INTELLIGENCE
Une API pour vos services essentiels. État, signaux régionaux et historique pour votre produit, tableau de bord ou IA.
Services observés, sans partenariat.
01 / SIGNAL EXPLORER
Des observations réelles enregistrées. Sélectionnez un service pour consulter son historique.
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
Recherchez un service ou consultez plusieurs états. Chaque réponse inclut date et fraîcheur.
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
Sept outils MCP en lecture seule pour les signaux et l’historique. Une seule licence Evelode.
Streamable HTTP · Bearer authentication · Read-only tools
https://mcp.uptimescout.com/mcpuptimescout_statusuptimescout_summaryuptimescout_history+ 4 tools05 / SIMPLE BY DESIGN
Choisissez votre volume et votre historique. Catalogue, lots, REST et MCP dans tous les forfaits.
$4.99/ mois
$9.99/ mois
$19.99/ mois
$39.99/ mois
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.
