Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Odoo

NPM · @HELIOSONE/ODOO-MCP

Odoo orders, late lines, supplier promise dates, manufacturing and stock. Read-only by default.

Available components

0 this week 69 Trust /100

Last scanned (7 hours ago)

Scores higher than 36% of npm servers

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 8 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1455 tokens (~111/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 76% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 54

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@heliosone/odoo-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~1,455 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_inventory_on_hand ~98

Product quantities from Odoo (product.product): on hand (qty_available), forecasted (virtual_available), incoming and outgoing, across all warehouses.

NameTypeReqDescription
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
productIdinteger––
querystring–Match product name or internal reference (SKU).

No output schema declared.

No examples provided.

get_order_status ~97

One sales or purchase order with its lines (ordered, delivered/received and invoiced quantities) and its transfers (receipts or deliveries). Find it by Odoo id or by order number / customer or vendor reference.

NameTypeReqDescription
namestring–Order number such as S00012 or P00007, or the customer/vendor reference.
orderIdinteger–Odoo record id.
orderTypestring––

No output schema declared.

No examples provided.

list_late_purchase_lines ~109

Lines on confirmed POs whose expected arrival (date_planned) is before asOf and that are not fully received. Adds qty_open and days_late.

NameTypeReqDescription
asOfstring–Cut-off date YYYY-MM-DD (default: today, UTC).
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
supplierstring–Match vendor name.

No output schema declared.

No examples provided.

list_late_sales_lines ~136

Lines on confirmed sales orders that are not fully delivered and whose promised date is before asOf. Promised date = the order's commitment_date if set, otherwise order date + the line's customer lead time (as Odoo computes it). Adds promised_date, qty_open and days_late.

NameTypeReqDescription
asOfstring–Cut-off date YYYY-MM-DD (default: today, UTC).
customerstring–Match customer name.
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).

No output schema declared.

No examples provided.

list_manufacturing_orders ~105

Odoo manufacturing orders (mrp.production) with state, quantity, planned start/finish and component availability. By default excludes done and cancelled orders. Needs the Manufacturing app.

NameTypeReqDescription
includeDoneboolean––
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
querystring–Match MO number, product or source document.

No output schema declared.

No examples provided.

list_open_purchase_orders ~123

Confirmed Odoo purchase orders (state "purchase" or locked "done") that are not fully received (receipt_status is not "full", where the field exists). includeRfqs adds draft, sent and to-approve RFQs. Newest first.

NameTypeReqDescription
includeRfqsboolean––
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
querystring–Match PO number, vendor name or vendor reference.

No output schema declared.

No examples provided.

list_open_sales_orders ~115

Confirmed Odoo sales orders (state "sale") that are not fully delivered (delivery_status is not "full", where the field exists). includeQuotations adds draft and sent quotations. Newest first.

NameTypeReqDescription
includeQuotationsboolean––
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
querystring–Match order number, customer name or customer reference.

No output schema declared.

No examples provided.

list_shipments ~149

Odoo transfers (stock.picking): receipts (incoming), deliveries (outgoing) or internal moves, with scheduled and done dates. By default only transfers not done or cancelled. lateOnly keeps those scheduled before asOf.

NameTypeReqDescription
asOfstring–Cut-off date YYYY-MM-DD (default: today, UTC).
directionstring––
includeDoneboolean––
lateOnlyboolean––
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
querystring–Match transfer number, source document or partner name.

No output schema declared.

No examples provided.

list_supplier_promise_dates ~98

Purchase order lines on confirmed POs with the vendor's expected arrival date (date_planned), soonest first. By default only lines with quantity still to receive.

NameTypeReqDescription
includeReceivedboolean––
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
supplierstring–Match vendor name.

No output schema declared.

No examples provided.

list_work_orders ~106

Odoo work orders (mrp.workorder): operation, work center, state, expected and actual duration. Optionally for one manufacturing order. By default excludes done and cancelled. Needs the Manufacturing app with work orders.

NameTypeReqDescription
includeDoneboolean––
limitinteger–Maximum rows to return (1-500, default 50).
manufacturingOrderIdinteger––
offsetinteger–Rows to skip, for paging (default 0).

No output schema declared.

No examples provided.

lookup_customer ~90

Find contacts (res.partner) by name, email, reference or VAT number. Contacts with more sales (customer_rank) come first.

NameTypeReqDescription
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
querystringyesName, email, internal reference or VAT number (partial match).

No output schema declared.

No examples provided.

lookup_supplier ~90

Find contacts (res.partner) by name, email, reference or VAT number. Contacts with more purchases (supplier_rank) come first.

NameTypeReqDescription
limitinteger–Maximum rows to return (1-500, default 50).
offsetinteger–Rows to skip, for paging (default 0).
querystringyesName, email, internal reference or VAT number (partial match).

No output schema declared.

No examples provided.

update_po_line_promise_date ~139

WRITE. Sets the expected arrival date (date_planned) of one purchase order line, e.g. after a vendor confirms a new date. Refused unless the server was started with ODOO_MCP_ENABLE_WRITES=true AND confirmation is exactly "CONFIRM update_po_line_promise_date". A date without a time is stored as 12:00 UTC. Returns the value before and after.

NameTypeReqDescription
confirmationstring–Must be exactly "CONFIRM update_po_line_promise_date".
lineIdintegeryespurchase.order.line id (see list_supplier_promise_dates).
promiseDatestringyes–

No output schema declared.

No examples provided.

Install

How do I install the Odoo MCP server?

Odoo runs locally as an npm package, launched with npx -y @heliosone/odoo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @heliosone/odoo-mcp

# add to Claude Code
claude mcp add helios-one-oy-odoo-mcp -- npx -y @heliosone/odoo-mcp
Common questions

What is the Odoo MCP server?

Odoo is an MCP server listed in the public MCP registry as io.github.Helios-One-Oy/odoo-mcp. Odoo orders, late lines, supplier promise dates, manufacturing and stock. Read-only by default. This page covers its npm package (@heliosone/odoo-mcp).

Is the Odoo MCP server safe to use?

Odoo scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Odoo MCP server expose?

Odoo exposes 13 tools: list_open_sales_orders, list_open_purchase_orders, get_order_status, list_supplier_promise_dates, list_late_purchase_lines, and 8 more. Their descriptions and schemas cost roughly 1,455 tokens of context every time the server is loaded.

Is the Odoo MCP server still maintained?

Odoo is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Odoo MCP server under?

Odoo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.