Odoo Pulse MCP Server

odoo-pulse PyPI v1.9.1

Published by minhhq-a1 — 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.

AI business analyst for Odoo ERP (18+) — one-call reports with verdicts, over MCP

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

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 − 4 = 96. 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:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — 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

low Shell/command execution in packaging/dev tooling (tests/contract/test_mcp_surface.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/contract/test_mcp_surface.py:217`): 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: ] = groups result = subprocess.run( [sys.executable, "-c", PROBE], check=True, capture_outpu

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/contract/test_mcp_surface.py

low Shell/command execution in packaging/dev tooling (tests/contract/test_metadata.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/contract/test_metadata.py:54`): 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: check=True): return subprocess.run( [ sys.executable, str(ROOT / "scripts/release/sy

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/contract/test_metadata.py

low Shell/command execution in packaging/dev tooling (tests/contract/test_release_contract.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/contract/test_release_contract.py:69`): 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: h / "github-output" subprocess.run( [ sys.executable, str(SCRIPT), "iden

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/contract/test_release_contract.py

low Shell/command execution in packaging/dev tooling (tests/contract/test_repository_hygiene.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/contract/test_repository_hygiene.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: ive}" ignored = subprocess.run( ["git", "check-ignore", "-q", relative], cwd=ROOT )

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/contract/test_repository_hygiene.py

low Shell/command execution in packaging/dev tooling (tests/contract/test_smithery_publish.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/contract/test_smithery_publish.py:82`): 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: tomli_shim) return subprocess.run( ["bash", str(script)], cwd=repo, env=env, captur

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/contract/test_smithery_publish.py

low Shell/command execution in packaging/dev tooling (tests/integration/test_package_startup.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/integration/test_package_startup.py:24`): 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: "PYTHONPATH", None) subprocess.run( [sys.executable, "-c", STARTUP_PROBE], check=True, cwd=t

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/integration/test_package_startup.py

Tools 88

Each tool and what it can reach — statically extracted from the published source.

  • get_invoiceingests untrusted input
  • get_purchase_orderingests untrusted input
  • get_sale_orderingests untrusted input
  • read_recordsingests untrusted input
  • absence_overviewno sensitive capability
  • aggregate_recordsno sensitive capability
  • business_pulseno sensitive capability
  • check_stockno sensitive capability
  • confirm_sale_orderno sensitive capability
  • create_contactno sensitive capability
Show 78 more tools ↓
  • create_leadno sensitive capability
  • create_recordno sensitive capability
  • create_taskno sensitive capability
  • delete_recordsno sensitive capability
  • find_partnerno sensitive capability
  • find_productsno sensitive capability
  • get_model_fieldsno sensitive capability
  • inventory_riskno sensitive capability
  • list_activitiesno sensitive capability
  • list_applicantsno sensitive capability
  • list_appraisalsno sensitive capability
  • list_approval_requestsno sensitive capability
  • list_attendancesno sensitive capability
  • list_bomsno sensitive capability
  • list_calendar_eventsno sensitive capability
  • list_coursesno sensitive capability
  • list_departmentsno sensitive capability
  • list_documentsno sensitive capability
  • list_email_campaignsno sensitive capability
  • list_employeesno sensitive capability
  • list_engineering_changesno sensitive capability
  • list_equipmentno sensitive capability
  • list_event_registrationsno sensitive capability
  • list_eventsno sensitive capability
  • list_expensesno sensitive capability
  • list_helpdesk_ticketsno sensitive capability
  • list_invoicesno sensitive capability
  • list_iot_devicesno sensitive capability
  • list_job_positionsno sensitive capability
  • list_knowledge_articlesno sensitive capability
  • list_loyalty_cardsno sensitive capability
  • list_loyalty_programsno sensitive capability
  • list_lunch_ordersno sensitive capability
  • list_maintenance_requestsno sensitive capability
  • list_manufacturing_ordersno sensitive capability
  • list_membershipsno sensitive capability
  • list_modelsno sensitive capability
  • list_notesno sensitive capability
  • list_opportunitiesno sensitive capability
  • list_paymentsno sensitive capability
  • list_payslipsno sensitive capability
  • list_pickingsno sensitive capability
  • list_planning_slotsno sensitive capability
  • list_pos_ordersno sensitive capability
  • list_pos_sessionsno sensitive capability
  • list_projectsno sensitive capability
  • list_purchase_ordersno sensitive capability
  • list_quality_alertsno sensitive capability
  • list_quality_checksno sensitive capability
  • list_repair_ordersno sensitive capability
  • list_sale_ordersno sensitive capability
  • list_sign_requestsno sensitive capability
  • list_social_postsno sensitive capability
  • list_subscriptionsno sensitive capability
  • list_surveysno sensitive capability
  • list_tasksno sensitive capability
  • list_time_offno sensitive capability
  • list_timesheetsno sensitive capability
  • list_vehiclesno sensitive capability
  • list_website_visitorsno sensitive capability
  • odoo_versionno sensitive capability
  • pipeline_reviewno sensitive capability
  • portfolio_healthno sensitive capability
  • procurement_watchno sensitive capability
  • production_healthno sensitive capability
  • project_budgetno sensitive capability
  • project_dashboardno sensitive capability
  • project_profitabilityno sensitive capability
  • project_status_reportno sensitive capability
  • project_subtask_hoursno sensitive capability
  • read_attachmentno sensitive capability
  • receivables_healthno sensitive capability
  • sales_snapshotno sensitive capability
  • search_countno sensitive capability
  • search_readno sensitive capability
  • standup_digestno sensitive capability
  • team_workloadno sensitive capability
  • update_recordsno sensitive capability

What this scan could not see

Versions 3

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
v1.9.1 latest A 96/100 6 1.13.0 2026-08-25
v1.9.0 A 96/100 5 1.12.1 2026-07-31
v1.8.2 A 96/100 0 1.12.1 2026-07-27

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: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/odoo-pulse/badge.svg)](https://mcptrustchecker.com/registry/odoo-pulse)
HTML
<a href="https://mcptrustchecker.com/registry/odoo-pulse"><img src="https://mcptrustchecker.com/registry/odoo-pulse/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/odoo-pulse/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 odoo-pulse --online --registry pypi

Use the free API → How scoring works

More in Business & CRM