Skills/PyPI/odoo-mcp-uvx

odoo-mcp-uvx@1.0.1

VERIFIED· not started

Publisher claims: "Read-only MCP server for standard Odoo (SaaS/Cloud) via XML-RPC — no custom module required" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher niduran-orion · publishing for 227 daysInstalls 294Last detonated 24 h ago
$claude mcp add odoo-mcp-uvx -- uvx odoo-mcp-uvx
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
ODOO_API_KEYODOO_PASSWORDConfiguration, not credentials: ODOO_DB, ODOO_LOCALE, ODOO_MCP_HOST, ODOO_MCP_LOG_FILE, ODOO_MCP_LOG_FORMAT, ODOO_MCP_LOG_JSON, ODOO_MCP_LOG_LEVEL, ODOO_MCP_LOG_REQUEST_BODY, ODOO_MCP_LOG_RESPONSE_BODY, ODOO_MCP_PORT, ODOO_MCP_SLOW_OPERATION_THRESHOLD_MS, ODOO_MCP_TRANSPORT, ODOO_PORT, ODOO_PROTOCOL, ODOO_URL, ODOO_USER
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for ODOO_API_KEY, ODOO_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx odoo-mcp-uvx

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsmcp_server_odoo/config.py:124 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file: Optional path to .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp_server_odoo/__main__.py:119 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint("\nPlease check your environment variables or .env file", file=sys.stderr)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp_server_odoo/config.py:137 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslooks for .env in current directory.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp_server_odoo/config.py:145 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Check if we have a .env file or environment variablesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp_server_odoo/config.py:133 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Load configuration from environment variables and .env file.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsmcp_server_odoo/config.py:136 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file: Optional path to .env file. If not provided,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈59 tok
1 file · 22 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for odoo-mcp-uvx@1.0.1 as of 24 h ago. This is the package itself, not its dependencies.