Odoo Sh MCP Server
odoo-sh-mcp
PyPI
v0.4.3
Published by nicoruiz — 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 6
high Reads a sensitive credential path or dumps the environment (src/odoo_sh_mcp/server.py)MTC-SRC-006
In the server's implementation (`src/odoo_sh_mcp/server.py:564`): 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: OO_SH_SSH_KEY", "~/.ssh/id_ed25519") if not ssh_host or not ssh_user: raise ValueError("ODOO_SH_SSH_
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/odoo_sh_mcp/server.py
high Tool "ssh_exec" exposes command/code executionMTC-CAP-001
Tool "ssh_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool ssh_exec
medium Unconstrained command parameter "command" on "ssh_exec"MTC-CAP-006
Tool "ssh_exec" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool ssh_exec · inputSchema.properties.command
low Reads a sensitive credential path or dumps the environment in packaging/dev tooling (tests/test_ssh.py)MTC-SRC-006
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_ssh.py:16`): 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: = "12345" KEY = "~/.ssh/id_ed25519" def make_proc(returncode=0, stdout="", stderr=""): proc = MagicMock() proc
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_ssh.py
low Mutating tool "ssh_exec" declares no destructiveHintMTC-CAP-005
Tool "ssh_exec" 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 ssh_exec
low Shell/command execution in packaging/dev tooling (src/odoo_sh_mcp/tools/ssh.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`src/odoo_sh_mcp/tools/ssh.py:23`): 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: try: result = subprocess.run(args, capture_output=True, text=True, timeout=120) except subprocess.TimeoutE
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/odoo_sh_mcp/tools/ssh.py
Tools 19
Each tool and what it can reach — statically extracted from the published source.
ssh_execruns code / shellcreate_model_fileno sensitive capabilitycreate_recordno sensitive capabilitycreate_view_inheritanceno sensitive capabilitydelete_recordno sensitive capabilityfind_field_in_viewno sensitive capabilityget_model_fieldsno sensitive capabilityget_model_infono sensitive capabilityget_server_logsno sensitive capabilityget_view_by_xmlidno sensitive capability
Show 9 more tools ↓
get_viewsno sensitive capabilityinstall_moduleno sensitive capabilitylist_modulesno sensitive capabilityscaffold_moduleno sensitive capabilitysearch_modelsno sensitive capabilitysearch_recordsno sensitive capabilityssh_read_logno sensitive capabilityupdate_recordno sensitive capabilityupgrade_moduleno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (19 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.4.3 latest |
A 93/100 | 6 | 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 odoo-sh-mcp --online --registry pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.