Root (MohamedElashri) MCP Server

root-mcp PyPI v0.1.7

Published by mohamedelashri — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
B
83/100
Last scanned
Trust
B · 83/100
How safe the published surface and source look. 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 100 − 17.5 = 83/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−15.4 Dynamic evaluation of a non-literal value MTC-SRC-010 injection
−2.1 Package has no source repository MTC-SUP-011 supply-chain

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 the deduction.

Findings 9

high Dynamic evaluation of a non-literal value (src/root_mcp/core/operations/basic_stats.py)MTC-SRC-010

In the server's implementation (`src/root_mcp/core/operations/basic_stats.py:289`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: eval(

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/root_mcp/core/operations/basic_stats.py

high Dynamic code execution in server code (src/root_mcp/core/operations/basic_stats.py)MTC-SRC-001

In the server's implementation (`src/root_mcp/core/operations/basic_stats.py:289`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: eval(

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/root_mcp/core/operations/basic_stats.py

high Dynamic code execution in server code (src/root_mcp/extended/analysis/expression.py)MTC-SRC-001

In the server's implementation (`src/root_mcp/extended/analysis/expression.py:45`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: eval(

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/root_mcp/extended/analysis/expression.py

high Dynamic code execution in server code (tests/test_root_executor.py)MTC-SRC-001

In the server's implementation (`tests/test_root_executor.py:151`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: eval(

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 tests/test_root_executor.py

high Shell/command execution in server code (src/root_mcp/common/root_availability.py)MTC-SRC-002

In the server's implementation (`src/root_mcp/common/root_availability.py: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: subprocess.run(

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/root_mcp/common/root_availability.py

high Shell/command execution in server code (src/root_mcp/extended/root_native/executor.py)MTC-SRC-002

In the server's implementation (`src/root_mcp/extended/root_native/executor.py:201`): 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: subprocess.run(

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/root_mcp/extended/root_native/executor.py

high Shell/command execution in server code (tests/test_root_executor.py)MTC-SRC-002

In the server's implementation (`tests/test_root_executor.py:147`): 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: exec(

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 tests/test_root_executor.py

medium Dynamic module load from a non-literal (tests/test_root_executor.py)MTC-SRC-005

In the server's implementation (`tests/test_root_executor.py:158`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: __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 tests/test_root_executor.py

low Package has no source repositoryMTC-SUP-011

"root-mcp" 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 root-mcp

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
v0.1.7 latest B 83/100 9 1.5.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 · 83/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/root-mcp/badge.svg)](https://mcptrustchecker.com/registry/root-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/root-mcp"><img src="https://mcptrustchecker.com/registry/root-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/root-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 root-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Root 1

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

More in Learning & Documentation