Romaco MCP Server

@romaco/mcp npm v0.0.4 Source verified

Published by romaco-labs — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for romaco-charts — control your trading chart from Claude, Cursor, or any MCP-compatible AI agent

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (dist/tools/setup_chart.js)MTC-SRC-002

In the server's implementation (`dist/tools/setup_chart.js:110`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: cFile } = await import('child_process'); const opener = process.platform === 'darwin' ? 'open'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/tools/setup_chart.js

Tools 27

Each tool and what it can reach — statically extracted from the published source.

  • romaco_add_alertno sensitive capability
  • romaco_add_drawingno sensitive capability
  • romaco_add_indicatorno sensitive capability
  • romaco_analyze_marketno sensitive capability
  • romaco_annotateno sensitive capability
  • romaco_calculate_position_sizeno sensitive capability
  • romaco_capture_snapshotno sensitive capability
  • romaco_clear_alertsno sensitive capability
  • romaco_clear_drawingsno sensitive capability
  • romaco_detect_patternsno sensitive capability
Show 17 more tools ↓
  • romaco_draw_patternno sensitive capability
  • romaco_find_levelsno sensitive capability
  • romaco_get_chart_contextno sensitive capability
  • romaco_get_indicator_valuesno sensitive capability
  • romaco_get_visible_candlesno sensitive capability
  • romaco_go_to_timestampno sensitive capability
  • romaco_list_panesno sensitive capability
  • romaco_list_templatesno sensitive capability
  • romaco_load_candlesno sensitive capability
  • romaco_open_paper_positionno sensitive capability
  • romaco_remove_alertno sensitive capability
  • romaco_remove_indicatorno sensitive capability
  • romaco_reset_viewno sensitive capability
  • romaco_set_zoomno sensitive capability
  • romaco_setup_chartno sensitive capability
  • romaco_thesisno sensitive capability
  • romaco_thesis_batchno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.0.4 latest A 94/100 1 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/romaco-mcp/badge.svg)](https://mcptrustchecker.com/registry/romaco-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/romaco-mcp"><img src="https://mcptrustchecker.com/registry/romaco-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/romaco-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @romaco/mcp --online

Use the free API → How scoring works

More in Finance & Commerce