Odoo Pulse
An AI business analyst for your Odoo ERP. Ask one question, get one answer — numbers, highlights, risks, and a verdict (on-track / at-risk / off-track) — over the Model Context Protocol. CRUD bridges to Odoo already exist; this is the analytics layer that sits on top.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
minhhq-a1
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
ODOO_URLenv =https://acme.odoo.com \ODOO_DBenv =acme \ODOO_USERNAMEenv =you@example.com \ODOO_API_KEYenv =your-api-key \ODOO_READ_ONLYenv =true \ODOO_MAX_RECORDSODOO_VERIFY_SSLODOO_WRITABLE_MODELSODOO_ALLOW_DELETEODOO_SCHEMA_CACHE_TTLODOO_SCHEMA_CACHE_MAXODOO_MAX_ATTACHMENT_BYTESODOO_TIMEOUTODOO_TOOL_GROUPSapps — opt in via . Full catalogue and configuration:Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
84/84 tools missing one or more hints — find_partner (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_opportunities (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_sale_orders (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +81 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Destructive tools are labelled
1 tool perform destructive updates without destructiveHint — delete_records deletes at line 90 (return safe(lambda: {"deleted": get_client().unlink(model, ids), "ids": ids}))
Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.
Tool inputs are validated
83/84 tool handlers declare input schemas (99%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 3/84 tool handlers wrap calls in try/catch (4%)
Wrap each tool handler body in try/catch and return a structured error response.
Tests exist
No test files found
Add tests that exercise each declared tool.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/minhhq-a1/odoo-pulse)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check