odoo-mcp-beta@0.1.2
VERIFIED· not startedPublisher claims: "MCP Server for Odoo Integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
OAUTH_ALLOWED_DOMAINSOAUTH_ALLOWED_EMAILSOAUTH_AUDIENCEOAUTH_AUTH0_DOMAINOAUTH_AUTHORIZATION_ENDPOINTOAUTH_CLIENT_IDOAUTH_CLIENT_SECRETOAUTH_DISCOVERY_ENDPOINTOAUTH_ENABLEDOAUTH_ISSUEROAUTH_JWKS_URIOAUTH_OKTA_DOMAINOAUTH_PROVIDEROAUTH_REDIRECT_URIOAUTH_REFRESH_TOKENOAUTH_REQUIRE_EMAIL_VERIFICATIONOAUTH_REQUIRE_PKCEOAUTH_REQUIRE_STATEOAUTH_SCOPESOAUTH_SESSION_TIMEOUTOAUTH_TOKEN_ENDPOINTOAUTH_USERINFO_ENDPOINTOAUTH_VALIDATE_TOKENODOO_PASSWORDConfiguration, not credentials: ODOO_CONFIG_FILE, ODOO_DB, ODOO_MCP_PREFIX, ODOO_TIMEOUT, ODOO_URL, ODOO_USERNAME, ODOO_VERIFY_SSL- Where it talks to
- no vendor host named in the codeAlso google.com, microsoftonline.com — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names google.com, microsoftonline.com as well as its own vendor. The guard injects OAUTH_ALLOWED_DOMAINS, OAUTH_ALLOWED_EMAILS, OAUTH_AUDIENCE, OAUTH_AUTH0_DOMAIN, OAUTH_AUTHORIZATION_ENDPOINT, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, OAUTH_DISCOVERY_ENDPOINT, OAUTH_ENABLED, OAUTH_ISSUER, OAUTH_JWKS_URI, OAUTH_OKTA_DOMAIN, OAUTH_PROVIDER, OAUTH_REDIRECT_URI, OAUTH_REFRESH_TOKEN, OAUTH_REQUIRE_EMAIL_VERIFICATION, OAUTH_REQUIRE_PKCE, OAUTH_REQUIRE_STATE, OAUTH_SCOPES, OAUTH_SESSION_TIMEOUT, OAUTH_TOKEN_ENDPOINT, OAUTH_USERINFO_ENDPOINT, OAUTH_VALIDATE_TOKEN, ODOO_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.
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 88/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 deviationsStatic findings
# Note: This is a simplified version. Real sudo would requireFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# For now, we just execute with current user and note it was requested as sudoFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
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-beta@0.1.2 as of 23 h ago. This is the package itself, not its dependencies.