Visidata (moeloubani) MCP Server
@moeloubani/visidata-mcp
npm
v0.1.7
Published by @moeloubani — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for VisiData - a terminal spreadsheet multitool for discovering and arranging tabular data
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 − 7.5 = 93. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −6.3 | Untrusted input concatenated into a command sink MTC-SRC-009 | injection |
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 93 − 7 = 86. 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:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 7
high Shell/command execution in server code (bin/visidata-mcp.js)MTC-SRC-002
In the server's implementation (`bin/visidata-mcp.js:3`): 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: st { spawn } = require('child_process'); const path = require('path'); const fs = require('fs'); // Try to find Python
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 bin/visidata-mcp.js
medium Untrusted input concatenated into a command sink (bin/visidata-mcp.js)MTC-SRC-009
In the server's implementation (`bin/visidata-mcp.js:13`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: equire('child_process').execSync(`${candidate} --version`, { encoding: 'utf8', stdio: 'pipe' })
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 bin/visidata-mcp.js
low Shell/command execution in packaging/dev tooling (scripts/check-python.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/check-python.js:3`): 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: { execSync } = require('child_process'); function checkPython() { console.log('🔍 Checking Python requirements...');
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 scripts/check-python.js
low Shell/command execution in packaging/dev tooling (scripts/install-python-package.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/install-python-package.js:3`): 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: { execSync } = require('child_process'); function findPython() { const candidates = ['python3', 'python']; for (
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 scripts/install-python-package.js
low Shell/command execution in packaging/dev tooling (scripts/test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/test.js:3`): 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: ync, spawn } = require('child_process'); function findPython() { const candidates = ['python3', 'python']; for (
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 scripts/test.js
low Shell/command execution in packaging/dev tooling (scripts/uninstall.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/uninstall.js:3`): 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: { execSync } = require('child_process'); function findPython() { const candidates = ['python3', 'python']; for (
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 scripts/uninstall.js
low Package runs install-time scripts (preinstall, postinstall)MTC-SUP-010
"@moeloubani/visidata-mcp" executes preinstall/postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/check-python.js ; node scripts/install-python-package.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @moeloubani/visidata-mcp
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.7 latest |
B 86/100 | 7 | 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.
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 @moeloubani/visidata-mcp --onlineOther implementations of Visidata 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Data Science & ML
MCP server for 2s.io — 575+ pay-per-call tools for AI agents — ground-truth data, AI gateway, and agent infra (storage, locks, queues, watchers). x402 USDC on Base/Solana, no API keys, upto usage billing, free trials.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Add MCP servers to your favorite coding agents with a single command.
Help agents automatically write and test stories for your UI components
Model Context Protocol server for AI-Archive platform - enables AI agents to discover, submit, and review research papers
MCP server for Semantic Scholar research workflows with stdio and Streamable HTTP transports.