_ registry / mcp streamable-http · checked 13h ago

tradecanvas

https://tradecanvas.dev

Registry code: 186325f99050e0f5

api record

TradeCanvas (@tradecanvas/chart) draws trading charts: ChartWidget is the full trading UI, Chart the headless chart, ChartWidgetGrid several charts. Look names up instead of guessing them: list_indicators and get_indicator for indicator ids, params and line keys; list_drawing_tools for drawing types and their anchors; list_options for the options of each entry point; list_widget_features and list_style_keys for feature switches and style keys. For a chart that is not a trading chart (bars, a donut, an order book's depth, an equity curve, a market map, a gauge), list_finance_charts names the…

endpoint
https://tradecanvas.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tradecanvas live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is tradecanvas free to use?
Yes — the hub reached it with no key and no payment.
What tools does tradecanvas have?
11 tools: get_indicator, migration_plan, migration_lookup, list_options, list_widget_features, list_style_keys, validate_options, convert_widget_options, ….
Is tradecanvas safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
109ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
3 open 8 never probed 3 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_finance_charts open 13h ago

    Lists the charts of @tradecanvas/chart that are not the trading chart: bars, donut, scatter, histogram, calendar, correlation matrix, heatmap and sector map, depth, equity curve, waterfall, gauge, sparkline, and a backtest dashboard. Each with its class name and what it is for; list_options with that name gives its options. Search by words of the name or the purpose.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Words to find in the name or the purpose, e.g. \"order book\" or \"returns\"."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • list_drawing_tools open 13h ago

    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").

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Words to find in the type or name."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • list_indicators open 13h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Words to find in the id, short name or name."
        },
        "placement": {
          "enum": [
            "overlay",
            "panel"
          ],
          "type": "string",
          "description": "Only those on the price pane, or only those in a pane of their own."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_indicator unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The indicator's id ('rsi', 'bb'), short name or name."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • migration_plan unknown never probed

    How to move an app from TradingView's Advanced Charts / Trading Platform (the charting library) or from Lightweight Charts to TradeCanvas: the steps in order, what to search the app's code for and which tool maps what each search finds, and what to check at the end. Call it first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "source": {
          "enum": [
            "tradingview",
            "lightweight-charts"
          ],
          "type": "string",
          "description": "The library the app uses now: 'tradingview' (Advanced Charts, Trading Platform; the default) or 'lightweight-charts'."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • migration_lookup unknown never probed

    What a name of TradingView's charting library (Advanced Charts, Trading Platform) or Lightweight Charts becomes in TradeCanvas: a widget option, featureset, override key, study, drawing shape, widget or chart method, datafeed or broker member, or a resolution. Gives the TradeCanvas option, feature switch, style key, indicator id (with its defaults and line keys), drawing type (with its anchors) or call, and says plainly when there is no equivalent and what to do instead. Look up one name with 'name', or search the table with 'query'.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kind": {
          "enum": [
            "option",
            "featureset",
            "override",
            "study",
            "drawing",
            "method",
            "datafeed",
            "broker",
            "resolution"
          ],
          "type": "string",
          "description": "What the name is: a widget 'option', a 'featureset', an 'override' key, a 'study' (indicator), a 'drawing' (shape name), a 'method' of the widget or a chart, a 'datafeed' or 'broker' member, or a 'resolution' ('60', '1D')."
        },
        "name": {
          "type": "string",
          "description": "The name as the old library spells it: 'header_widget', 'paneProperties.background', 'Relative Strength Index', 'trend_line', 'createStudy', 'getBars', '60'."
        },
        "query": {
          "type": "string",
          "description": "Words to find in the table's names, targets and notes, when there is no exact name: 'volume', 'legend'."
        },
        "source": {
          "enum": [
            "tradingview",
            "lightweight-charts"
          ],
          "type": "string",
          "description": "The library the app uses now: 'tradingview' (Advanced Charts, Trading Platform; the default) or 'lightweight-charts'."
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • list_options unknown never probed

    Lists the options that new ChartWidget(el, options), new Chart(el, options), new ChartWidgetGrid(el, options) or a finance chart (new BarChart(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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "target"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Words to find in the option name or doc."
        },
        "target": {
          "enum": [
            "ChartWidget",
            "Chart",
            "ChartWidgetGrid",
            "BarChart",
            "DonutChart",
            "ScatterChart",
            "HistogramChart",
            "CalendarChart",
            "MatrixChart",
            "HeatmapChart",
            "CounterClockChart",
            "DepthChart",
            "EquityCurveChart",
            "WaterfallChart",
            "GaugeChart",
            "SparklineChart",
            "PerformanceDashboard"
          ],
          "type": "string",
          "description": "The entry point: ChartWidget (the full trading UI), Chart (the headless chart), ChartWidgetGrid (several charts), or a finance chart by its class name (list_finance_charts names them)."
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
  • list_widget_features unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "prefix": {
          "type": "string",
          "description": "Only names starting with this, e.g. 'toolbar.' or 'menu.'."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • list_style_keys unknown never probed

    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.'.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "prefix": {
          "type": "string",
          "description": "Only keys starting with this, e.g. 'grid.' or 'crosshair.'."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • validate_options unknown never probed

    Checks an options object before it goes to new ChartWidget, new Chart, new ChartWidgetGrid or a finance chart (by its class name): 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "target",
        "options"
      ],
      "properties": {
        "target": {
          "enum": [
            "ChartWidget",
            "Chart",
            "ChartWidgetGrid",
            "BarChart",
            "DonutChart",
            "ScatterChart",
            "HistogramChart",
            "CalendarChart",
            "MatrixChart",
            "HeatmapChart",
            "CounterClockChart",
            "DepthChart",
            "EquityCurveChart",
            "WaterfallChart",
            "GaugeChart",
            "SparklineChart",
            "PerformanceDashboard"
          ],
          "type": "string",
          "description": "The entry point: ChartWidget (the full trading UI), Chart (the headless chart), ChartWidgetGrid (several charts), or a finance chart by its class name (list_finance_charts names them)."
        },
        "options": {
          "type": "object",
          "properties": {},
          "description": "The options object, as JSON.",
          "additionalProperties": true
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • convert_widget_options unknown never probed

    Turns the options object of TradingView's widget (new TradingView.widget({...}): its options, disabled_features / enabled_features and overrides) into ChartWidget options, or Lightweight Charts' createChart options into Chart options. Returns the options, the calls to make once the chart exists, what has no place (each with what to do), and what validate_options finds in the result. Write functions and other code as strings; they are carried as they are.

    mcp-tool

    {
      "type": "object",
      "required": [
        "options"
      ],
      "properties": {
        "source": {
          "enum": [
            "tradingview",
            "lightweight-charts"
          ],
          "type": "string",
          "description": "The library the app uses now: 'tradingview' (Advanced Charts, Trading Platform; the default) or 'lightweight-charts'."
        },
        "options": {
          "type": "object",
          "properties": {},
          "description": "The old options object, as JSON.",
          "additionalProperties": true
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 186325f99050e0f5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/186325f99050e0f5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/186325f99050e0f5/badge.svg)](https://brick.blue/agent/186325f99050e0f5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.