Kote Charts — Bitcoin on-chain analytics
v1.2.1Bitcoin on-chain analytics API & MCP server: MVRV, NUPL, SOPR, exchange flows, whales
Endpoint health
online- Last checked
- 11/20/2026, 4:16:06 AM
- Latency
- 341 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.kotecharts%2Fcharts
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.kotecharts/charts": {
"url": "https://kotecharts.com/api/v1/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
4 shown · authentication unknown
Describe a chart
describe_chart
Explain one metric before using its numbers: what it shows, how to read it, caveats, formula, payload fields with units, input data categories, update cadence, known limitations and freshness (last data day, published_at, granularities), plus the page URL, the REST endpoint and a ready citation string. Call it when the user asks what a metric means or before interpreting get_chart output.
Schema valid · SHA-256 3615651fd262…
View input schema
{ "type": "object", "properties": { "id": { "type": "string", "minLength": 1, "maxLength": 80, "description": "Chart id from list_charts, e.g. \"sopr\"." } }, "required": [ "id" ], "additionalProperties": false, "$schema": "http://json-schema.org/draft-07/schema#" }Get chart data
get_chart
Fetch the historical values of one chart as JSON rows {t, …fields} (units per field: describe_chart → fields). Use for trends, history and comparisons; use get_latest when only the current value matters. Time series are downsampled to maxPoints (default 500, max 2000; first/last points preserved). Use from/to (YYYY-MM-DD or an exact UTC timestamp) to window and granularity (5m|day|3day|week|month|year) where available. Five-minute data is retained for 30 days; daily data is closed-only unless includePartial=true explicitly requests the still-open UTC day. That row is partial:true with partialMethod (trailing24h: rolling 24h ending at asOf, comparable with closed days; asOf: a level as of asOf), estimated (true = blended from yesterday, not exact 5m data) and coverage (share of the UTC day elapsed); never sum it with closed days.
Schema valid · SHA-256 9e29bb398549…
Connections
streamable-http
https://kotecharts.com/api/v1/mcp