Tvcontrol (seandonahoe) MCP Server

@seandonahoe/tvcontrol npm v2.0.0

Published by @seandonahoe — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
B
87/100
Last scanned
Trust
B · 87/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.
B Why this grade threat 98 − adoption risk = 87/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 − 2.1 = 98. What the published surface and source actually contain:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain

2. Client adoption risk — 98 − 11 = 87. 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
−5 publisher verification (unlocatable) — no provenance and no public repository to inspect
inspection depth (source) — how much of the target the scan could see

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 8

high Shell/command execution in server code (src/core/health.js)MTC-SRC-002

In the server's implementation (`src/core/health.js:6`): 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: child_process

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 src/core/health.js

medium Hardcoded egress to an external endpoint (src/connection.js)MTC-SRC-003

In the server's implementation (`src/connection.js:127`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`http://${CDP_HOST}:${CDP_PORT}/json/list`

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 src/connection.js

medium Hardcoded egress to an external endpoint (src/core/alerts.js)MTC-SRC-003

In the server's implementation (`src/core/alerts.js:103`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://pricealerts.tradingview.com/list_alerts'

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 src/core/alerts.js

medium Hardcoded egress to an external endpoint (src/core/chart.js)MTC-SRC-003

In the server's implementation (`src/core/chart.js:232`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`https://symbol-search.tradingview.com/symbol_search/v3/?${params}`

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 src/core/chart.js

medium Hardcoded egress to an external endpoint (src/core/pine.js)MTC-SRC-003

In the server's implementation (`src/core/pine.js:341`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch( 'https://pine-facade.tradingview.com/pine-facade/translate_light?user_name=Guest&pine_id=00000000-0000-0000-0000-000000000000'

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 src/core/pine.js

medium Hardcoded egress to an external endpoint (src/core/sweep_parallel.js)MTC-SRC-003

In the server's implementation (`src/core/sweep_parallel.js:36`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`http://${CDP_HOST}:${CDP_PORT}/json/new?${url}`

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 src/core/sweep_parallel.js

medium Hardcoded egress to an external endpoint (src/core/tab.js)MTC-SRC-003

In the server's implementation (`src/core/tab.js:15`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`http://${CDP_HOST}:${CDP_PORT}/json/list`

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 src/core/tab.js

low Package has no source repositoryMTC-SUP-011

"@seandonahoe/tvcontrol" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package @seandonahoe/tvcontrol

Tools 88

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

  • alert_createno sensitive capability
  • alert_deleteno sensitive capability
  • alert_delete_by_idno sensitive capability
  • alert_listno sensitive capability
  • batch_runno sensitive capability
  • capture_screenshotno sensitive capability
  • chart_get_stateno sensitive capability
  • chart_get_visible_rangeno sensitive capability
  • chart_manage_indicatorno sensitive capability
  • chart_scroll_to_dateno sensitive capability
  • chart_set_symbolno sensitive capability
  • chart_set_timeframeno sensitive capability
  • chart_set_typeno sensitive capability
  • chart_set_visible_rangeno sensitive capability
  • chart_vision_readno sensitive capability
  • data_get_equityno sensitive capability
  • data_get_indicatorno sensitive capability
  • data_get_ohlcvno sensitive capability
  • data_get_pine_boxesno sensitive capability
  • data_get_pine_labelsno sensitive capability
  • data_get_pine_linesno sensitive capability
  • data_get_pine_tablesno sensitive capability
  • data_get_strategy_resultsno sensitive capability
  • data_get_study_valuesno sensitive capability
  • data_get_tradesno sensitive capability
  • depth_getno sensitive capability
  • draw_clearno sensitive capability
  • draw_get_propertiesno sensitive capability
  • draw_listno sensitive capability
  • draw_remove_oneno sensitive capability
  • draw_shapeno sensitive capability
  • indicator_set_inputsno sensitive capability
  • indicator_toggle_visibilityno sensitive capability
  • layout_listno sensitive capability
  • layout_switchno sensitive capability
  • pane_focusno sensitive capability
  • pane_listno sensitive capability
  • pane_set_layoutno sensitive capability
  • pane_set_symbolno sensitive capability
  • pine_analyzeno sensitive capability
  • pine_checkno sensitive capability
  • pine_compileno sensitive capability
  • pine_get_consoleno sensitive capability
  • pine_get_errorsno sensitive capability
  • pine_get_sourceno sensitive capability
  • pine_list_scriptsno sensitive capability
  • pine_newno sensitive capability
  • pine_openno sensitive capability
  • pine_saveno sensitive capability
  • pine_set_sourceno sensitive capability
  • pine_smart_compileno sensitive capability
  • quote_getno sensitive capability
  • replay_autoplayno sensitive capability
  • replay_startno sensitive capability
  • replay_statusno sensitive capability
  • replay_stepno sensitive capability
  • replay_stopno sensitive capability
  • replay_tradeno sensitive capability
  • state_deleteno sensitive capability
  • state_listno sensitive capability
  • state_restoreno sensitive capability
  • state_snapshotno sensitive capability
  • strategy_sweepno sensitive capability
  • symbol_infono sensitive capability
  • symbol_searchno sensitive capability
  • tab_closeno sensitive capability
  • tab_listno sensitive capability
  • tab_newno sensitive capability
  • tab_switchno sensitive capability
  • tv_discoverno sensitive capability
  • tv_health_checkno sensitive capability
  • tv_launchno sensitive capability
  • tv_ui_stateno sensitive capability
  • ui_clickno sensitive capability
  • ui_evaluateno sensitive capability
  • ui_find_elementno sensitive capability
  • ui_fullscreenno sensitive capability
  • ui_hoverno sensitive capability
  • ui_keyboardno sensitive capability
  • ui_mouse_clickno sensitive capability
  • ui_open_panelno sensitive capability
  • ui_scrollno sensitive capability
  • ui_type_textno sensitive capability
  • watchlist_addno sensitive capability
  • watchlist_exportno sensitive capability
  • watchlist_getno sensitive capability
  • watchlist_importno sensitive capability
  • watchlist_removeno sensitive capability

What this scan could not see

Versions

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
v2.0.0 latest B 87/100 8 1.8.0 2026-07-23

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: B · 87/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/seandonahoe-tvcontrol/badge.svg)](https://mcptrustchecker.com/registry/seandonahoe-tvcontrol)
HTML
<a href="https://mcptrustchecker.com/registry/seandonahoe-tvcontrol"><img src="https://mcptrustchecker.com/registry/seandonahoe-tvcontrol/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/seandonahoe-tvcontrol/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 @seandonahoe/tvcontrol --online

Use the free API → How scoring works

Other implementations of Tvcontrol 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Gaming & Entertainment