Estado del servicio — API, MCP y frescura de los datos | Kote Charts
Estado en vivo de la API, el servidor MCP y el procesamiento on-chain de Kote Charts: bloque analizado, frescura de los gráficos, historial de disponibilidad independiente y pruebas públicas.
What is measured
API and database — the public API answers and can read its charts database (GET /api/v1/health).
MCP server — the Model Context Protocol endpoint for AI agents (/api/v1/mcp).
On-chain processing — the last analysed Bitcoin block and how long ago it was processed; daily charts must cover the previous closed UTC day.
Data delivery — the link that carries freshly computed charts from the processing database to the serving one.
Chart freshness — how many public charts are behind their update cadence, listed by name.
Machine-readable: `GET /api/v1/status` (no key, cached 30 seconds). Only the API or its database can make the service an outage; late data shows as degraded.
Verify it yourself
Public contract tests — keyless tests of the API, OpenAPI, MCP and the chart count run daily on GitHub: contract workflow.
Change history — releases, data corrections and incidents: changelog.