Tabrix MCP Server
@tabrix/tabrix
npm
v2.7.0
Source verified
Published by guodaxia103 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Tabrix Native-Messaging host (Node)
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 6 = 93. 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 |
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 11
high Shell/command execution in server code (dist/cli.js)MTC-SRC-002
In the server's implementation (`dist/cli.js:40`): 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: require("path")); const child_process_1 = require("child_process"); const utils_1 = require("./scripts/utils"); const br
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/cli.js
high Shell/command execution in server code (dist/mcp/bridge-recovery.js)MTC-SRC-002
In the server's implementation (`dist/mcp/bridge-recovery.js:10`): 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: dgeRecovery; const node_child_process_1 = require("node:child_process"); const node_fs_1 = require("node:fs"); const nod
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/mcp/bridge-recovery.js
low Shell/command execution in packaging/dev tooling (dist/scripts/browser-config.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/browser-config.js:46`): 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: require("path")); const child_process_1 = require("child_process"); const constant_1 = require("./constant"); var Browse
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/scripts/browser-config.js
low Shell/command execution in packaging/dev tooling (dist/scripts/build.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/build.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: { value: true }); const child_process_1 = require("child_process"); const fs_1 = __importDefault(require("fs")); const p
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/scripts/build.js
low Shell/command execution in packaging/dev tooling (dist/scripts/daemon.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/daemon.js:15`): 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: require("path")); const child_process_1 = require("child_process"); const constant_1 = require("../constant"); const PID
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/scripts/daemon.js
low Shell/command execution in packaging/dev tooling (dist/scripts/doctor.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/doctor.js:19`): 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: require("path")); const child_process_1 = require("child_process"); const constant_1 = require("./constant"); const brow
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/scripts/doctor.js
low Shell/command execution in packaging/dev tooling (dist/scripts/postinstall.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/postinstall.js:10`): 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: require("path")); const child_process_1 = require("child_process"); const constant_1 = require("./constant"); const util
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/scripts/postinstall.js
low Shell/command execution in packaging/dev tooling (dist/scripts/report.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/report.js:17`): 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: require("path")); const child_process_1 = require("child_process"); const constant_1 = require("./constant"); const brow
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/scripts/report.js
low Shell/command execution in packaging/dev tooling (dist/scripts/smoke.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/smoke.js:13`): 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: re("path")); const node_child_process_1 = require("node:child_process"); const constant_1 = require("../constant"); cons
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/scripts/smoke.js
low Shell/command execution in packaging/dev tooling (dist/scripts/utils.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/scripts/utils.js:26`): 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: quire("crypto")); const child_process_1 = require("child_process"); const util_1 = require("util"); const constant_1 = r
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/scripts/utils.js
low Package runs install-time scripts (postinstall)MTC-SUP-010
"@tabrix/tabrix" executes 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 -e "const fs=require('fs');const path=require('path');const file=path.join(process.cwd(),'dist','scripts','postinstall.js');if(fs.existsSync(file)){require
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package @tabrix/tabrix
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 |
|---|---|---|---|---|
v2.7.0 latest |
A 93/100 | 11 | 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 @tabrix/tabrix --onlineMore in Browser Automation
Model Context Protocol (MCP) server that integrates AgentQL data extraction capabilities.
Screenshot any URL or HTML as PNG/JPEG/WebP from your AI agent. Full-page, clean, no install.
MCP server for aria51 accessibility scanner
Bridge any browser web app to Claude Code via MCP
Browserbase’s official MCP server: cloud headless browsers for agents, with sessions and screenshots.
MCP server for AI web browser automation using Browserbase and Stagehand