MCP.Market

Trade Chart MCP server

online · 100% uptime
by openkrill.app·app.openkrill/trade-chart·v1.0.1

A candlestick chart for a public ticker, with volume, the indicators you name and a plain read.

C65/100grade C
What users say
No reviews yet
Be the first
Safety scan
C65/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Trade Chart yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Trade Chart tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Trade Chart compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 20% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
109 ms
faster than 82% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-03, latest 2026-10-21, typically one every 18 days.

Install Trade Chart in Claude Code, Cursor or VS Code

claude mcp add --transport http trade-chart https://chart.openkrill.app/mcp
Add to Cursor

Trade Chart: common questions

Is Trade Chart MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Trade Chart safety report
How do I install Trade Chart?
It runs remotely at chart.openkrill.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Trade Chart need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Trade Chart maintained?
The latest release is v1.0.1.
Is Trade Chart up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Trade Chart compare with other MCP servers?
safety score 65/100 (higher than 20% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 109 ms (faster than 82% of 30,031 servers). Full comparison.