Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TradeCanvas

NPM · @TRADECANVAS/MCP

Look up TradeCanvas chart indicators, options and drawing tools, and check options before use.

Available components

82 Trust /100

Last scanned (10 hours ago)

Scores higher than 72% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to bonguynvan/tradecanvas). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 870 tokens (~124/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 67

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@tradecanvas/mcp@1.61.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo bonguynvan/tradecanvas
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/bonguynvan/tradecanvas/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637873382
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c92505a38377146c523bb2226af82e63619cd81d8ad6a8334d0cd26d0564de4e296d444fc0a948248912f2722db3efa47718a988105781fb30bbc9fb1

Background: How many MCP packages publish verified provenance →

Dependencies 1 package
Packages resolved 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~754 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_indicator ~101

One built-in indicator in full: its default params (what addIndicator takes), its inputs, its lines (the keys getIndicatorOutput returns per bar, which are often not the indicator id: RSI's line is `value`), its levels, and code that adds it and reads it. Takes the id, the short name or the full name.

NameTypeReqDescription
idstringyesThe indicator's id ('rsi', 'bb'), short name or name.

No output schema declared.

No examples provided.

list_drawing_tools ~83

Lists the built-in drawing tools: the `type` that chart.addDrawing and chart.setDrawingTool take, the number of points (anchors) each needs, how the pointer draws it, and the options it offers. Search by words of the type or name ("fib", "channel").

NameTypeReqDescription
querystring–Words to find in the type or name.

No output schema declared.

No examples provided.

list_indicators ~117

Lists the built-in indicators with their ids, names and where they draw (overlay: on the price pane; panel: in a pane of their own). Search by words of the id or name ("moving average", "bollinger"). Use the id with chart.addIndicator(id, params); get_indicator has the params and line keys.

NameTypeReqDescription
placementstring–Only those on the price pane, or only those in a pane of their own.
querystring–Words to find in the id, short name or name.

No output schema declared.

No examples provided.

list_options ~117

Lists the options that new ChartWidget(el, options), new Chart(el, options) or new ChartWidgetGrid(el, options) take: each name, its TypeScript type, its doc, and the values it allows where it allows only some. Search by words of the name or doc.

NameTypeReqDescription
querystring–Words to find in the option name or doc.
targetstringyesThe entry point: ChartWidget (the full trading UI), Chart (the headless chart) or ChartWidgetGrid (several charts).

No output schema declared.

No examples provided.

list_style_keys ~111

Lists the style keys of the chart's look and the kind of value each takes (color, boolean, lineStyle: 'solid' | 'dashed' | 'dotted', width: pixels up to 20). They go in Chart's `overrides` option or chart.applyOverrides({...}). Narrow by a prefix such as 'grid.' or 'series.candlestick.'.

NameTypeReqDescription
prefixstring–Only keys starting with this, e.g. 'grid.' or 'crosshair.'.

No output schema declared.

No examples provided.

list_widget_features ~90

Lists the names ChartWidget's `features` option takes (every switch is on unless set false). A name without a dot turns a whole capability off ('alerts', 'hotkeys'); a dotted name, one place ('toolbar.screenshot', 'menu.chart.settings'). Narrow by a prefix.

NameTypeReqDescription
prefixstring–Only names starting with this, e.g. 'toolbar.' or 'menu.'.

No output schema declared.

No examples provided.

validate_options ~135

Checks an options object before it goes to new ChartWidget, new Chart or new ChartWidgetGrid: unknown option names (with the one likely meant, and where an option of another entry point belongs), values outside the allowed ones, numbers given as strings, intervals, feature switch names, style override keys and values, and languages, nested options included. Write functions and adapters as strings; they pass.

NameTypeReqDescription
optionsobjectyesThe options object, as JSON.
targetstringyesThe entry point: ChartWidget (the full trading UI), Chart (the headless chart) or ChartWidgetGrid (several charts).

No output schema declared.

No examples provided.

Install

How do I install the TradeCanvas MCP server?

TradeCanvas runs locally as an npm package, launched with npx -y @tradecanvas/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @tradecanvas/mcp

# add to Claude Code
claude mcp add bonguynvan-tradecanvas -- npx -y @tradecanvas/mcp
Common questions

What is the TradeCanvas MCP server?

TradeCanvas is an MCP server listed in the public MCP registry as io.github.bonguynvan/tradecanvas. Look up TradeCanvas chart indicators, options and drawing tools, and check options before use. This page covers its npm package (@tradecanvas/mcp).

Is the TradeCanvas MCP server safe to use?

TradeCanvas scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the TradeCanvas MCP server expose?

TradeCanvas exposes 7 tools: list_indicators, get_indicator, list_drawing_tools, list_options, list_widget_features, and 2 more. Their descriptions and schemas cost roughly 754 tokens of context every time the server is loaded.

Is the TradeCanvas MCP server still maintained?

TradeCanvas is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the TradeCanvas MCP server under?

TradeCanvas declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.