Kote Charts — Bitcoin on-chain analytics MCP server
com.kotecharts/chartskotecharts.comstreamable-httpv1.2.2Scanned
Bitcoin on-chain analytics API & MCP server, new data every block: MVRV, SOPR, exchange/whale flows
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Kote Charts — Bitcoin on-chain analytics MCP server can do
The Kote Charts — Bitcoin on-chain analytics MCP server is published by kotecharts.com, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (describe_chart).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.2.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
describe_chartExplain 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 an…Reads text others writeNo findings
Why it is in this group
- The name "describe_chart" says "describe": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "explain" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_chartFetch the historical values of one chart as JSON rows {t, …fields} (units per field: describe_chart → fields).No findings
Why it is in this group
- The name "get_chart" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_latestAnswer "what is X now?": the most recent data point for one chart (plus the previous point for context) with asOf metadata (last data day, published_at, analysed block height).No findings
Why it is in this group
- The name "get_latest" says "get": a word for reading.
Description, as the server wrote it Answer "what is X now?": the most recent data point for one chart (plus the previous point for context) with asOf metadata (last data day, published_at, analysed block height). Distributions return the current snapshot; ranked lists return the top 10. exchange selects a venue for exchange-netflow only.
Annotations the server declares
- readOnlyHint: true
list_chartsDiscover which Bitcoin on-chain metrics exist.No findings
Why it is in this group
- The name "list_charts" says "list": a word for reading.
Description, as the server wrote it Discover which Bitcoin on-chain metrics exist. Returns every public chart with id, title, one-line blurb, category and formula. Call this FIRST to find a chart id (e.g. "mvrv", "exchange", "whale"), then use describe_chart / get_chart / get_latest with that id. Read-only, no side effects; the human page of each chart is https://kotecharts.com/c/{id}.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:19 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http charts https://kotecharts.com/api/v1/mcpclaude mcp add --transport http charts https://kotecharts.com/api/v1/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__charts__list_charts",
"mcp__charts__get_chart",
"mcp__charts__describe_chart",
"mcp__charts__get_latest"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as charts. Review it before you use it.
Capability tags behind 1 rule
- mcp__charts__describe_chart untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.kotecharts/charts/verify?hash=df088f481f1745776bd9d3bf85153f311891d34f0b4050986f7f1170b32371f9" | jq -e '.changed == false'Pinned hash df088f481f17, from Nov 20, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.kotecharts/charts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.kotecharts/charts)Source: MCP Registry · repository. Synced Nov 20, 2026, 08:17 UTC.
Kote Charts — Bitcoin on-chain analytics MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Kote Charts — Bitcoin on-chain analytics MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Kote Charts — Bitcoin on-chain analytics MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Kote Charts — Bitcoin on-chain analytics MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Kote Charts — Bitcoin on-chain analytics MCP server have?
- 4 tools: 4 read. list_charts, get_chart, describe_chart and get_latest.
Does the Kote Charts — Bitcoin on-chain analytics MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Kote Charts — Bitcoin on-chain analytics MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Kote Charts — Bitcoin on-chain analytics MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.