Computer Linker MCP Server
@easonwumac/computer-linker
npm
v0.1.12
Published by @easonwumac — 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.
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 − 7 = 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 |
| −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 12
high Reads a sensitive credential path or dumps the environment (dist/sensitive-files.js)MTC-SRC-006
In the server's implementation (`dist/sensitive-files.js:13`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: w Set([ ".env", ".netrc", ".npmrc", ".pypirc", "credentials", "credentials.json", "id_dsa",
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/sensitive-files.js
high Shell/command execution in server code (dist/capabilities.js)MTC-SRC-002
In the server's implementation (`dist/capabilities.js:1`): 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: ecFileSync } from "node:child_process"; import { arch, cpus, platform, release, totalmem, type } from "node:os"; import
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/capabilities.js
high Shell/command execution in server code (dist/cli.js)MTC-SRC-002
In the server's implementation (`dist/cli.js:2`): 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: ecFileSync } from "node:child_process"; import { existsSync, mkdirSync, mkdtempSync, readFileSync, rmSync, writeFileSync
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/processes.js)MTC-SRC-002
In the server's implementation (`dist/processes.js:2`): 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: spawnSync } from "node:child_process"; import { operationError } from "./operation-errors.js"; import { executableComma
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/processes.js
high Shell/command execution in server code (dist/screenshot.js)MTC-SRC-002
In the server's implementation (`dist/screenshot.js:1`): 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: { execFile } from "node:child_process"; import { existsSync, readdirSync, statSync } from "node:fs"; import { mkdir, rea
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/screenshot.js
high Shell/command execution in server code (dist/search.js)MTC-SRC-002
In the server's implementation (`dist/search.js:1`): 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: { execFile } from "node:child_process"; import { opendir, readFile } from "node:fs/promises"; import { join, relative }
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/search.js
high Shell/command execution in server code (dist/security.js)MTC-SRC-002
In the server's implementation (`dist/security.js:1`): 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: ecFileSync } from "node:child_process"; import { loadConfig } from "./config.js"; import { normalizeConfig } from "./per
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/security.js
high Shell/command execution in server code (dist/tunnels.js)MTC-SRC-002
In the server's implementation (`dist/tunnels.js:1`): 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: spawnSync } from "node:child_process"; import { once } from "node:events"; import { createHash, randomUUID } from "node
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/tunnels.js
high Shell/command execution in server code (dist/workspace-operations.js)MTC-SRC-002
In the server's implementation (`dist/workspace-operations.js:1`): 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: { execFile } from "node:child_process"; import { createHash } from "node:crypto"; import { opendir, readFile, stat } fro
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/workspace-operations.js
medium Tool "create_file" can modify the filesystemMTC-CAP-002
Tool "create_file" can write, overwrite or delete files (keyword "create_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool create_file
low Mutating tool "create_file" declares no destructiveHintMTC-CAP-005
Tool "create_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool create_file
low Unconstrained path parameter "path" on "create_file"MTC-CAP-008
Tool "create_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.
Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.
Location: tool create_file · inputSchema.properties.path
Tools 12
Each tool and what it can reach — statically extracted from the published source.
create_filewrites filescomputer_operationno sensitive capabilityget_capabilitiesno sensitive capabilityget_computer_infono sensitive capabilityget_operation_historyno sensitive capabilityglobno sensitive capabilitygrepno sensitive capabilitylist_workspacesno sensitive capabilitylsno sensitive capabilityopen_workspaceno sensitive capability
Show 2 more tools ↓
readno sensitive capabilityworkspace_operationno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, 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.12 latest |
A 93/100 | 12 | 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.
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 @easonwumac/computer-linker --onlineMore in Files & Storage
Security scan results for the Add MCP server.
Security scan results for the Atp Mcp Adapter MCP server.
Security scan results for the Duckpond MCP server.
Security scan results for the File Proxy MCP server.
Security scan results for the Fte MCP server.
Security scan results for the Google Drive MCP server.