Odoo AI Telegram MCP (prashantk8ursrvc-ux/odoo-ai-telegram-mcp) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
13 days ago

Odoo AI Telegram MCP

Exposes 104 Odoo tools across CRM, Sales, Inventory, Accounting, and Helpdesk, enabling natural-language control of an Odoo instance via a Telegram assistant with user-level authentication and multi-step orchestration.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

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

prashantk8ursrvc-ux

Source: Glama

Is this your MCP?

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

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: OPENROUTER_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 8 credentials: ODOO_PASSWORD, BOT_TOKEN, ADMIN_BOT_TOKEN, OPENROUTER_API_KEY, GROQ_API_KEY, GEMINI_API_KEY, ANTHROPIC_API_KEY, CLAUDE_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configODOO_VERSIONODOO_URL, ODOO_DB, Target instance
configODOO_URL, ODOO_DB, ODOO_VERSION Target instance
configODOO_DBODOO_URL, , ODOO_VERSION Target instance
configODOO_USERNAME
🔐 secretODOO_PASSWORD
configSKIP_AUTH_FOR_SCHEMA
🔐 secretBOT_TOKEN, ADMIN_BOT_TOKEN The two Telegram bots
🔐 secretADMIN_BOT_TOKENBOT_TOKEN, The two Telegram bots
configBRAND_COMPANY_NAME
configBRAND_COMPANY_SUBTITLE
configBRAND_COMPANY_TAGLINE
configBRAND_SIGNATURE_NAME
configBRAND_SIGNATURE_COMPANY
configBRAND_SIGNATURE_ADDRESS
configBRAND_SIGNATURE_EMAIL
configBRAND_SIGNATURE_PHONE
configBRAND_COLOR_PRIMARY_NAVY
configBRAND_COLOR_ACCENT_BLUE
configBRAND_COLOR_BRAND_GOLD
configBRAND_COLOR_ALERT_RED
configBRAND_COLOR_ALERT_RED_BG
configBRAND_COLOR_SUCCESS_GREEN
configBRAND_COLOR_BACKGROUND
configBRAND_COLOR_TEXT_BODY
configBRAND_COLOR_TEXT_MUTED
configBRAND_COLOR_LINE_BORDER
configBRAND_COLOR_TABLE_HEADER
configLLM_PROVIDER+ provider key Model backend
🔐 secretOPENROUTER_API_KEY
configOPENROUTER_MODEL
🔐 secretGROQ_API_KEY
configGROQ_MODEL
🔐 secretGEMINI_API_KEY
configGEMINI_MODEL
configOLLAMA_HOST
configOLLAMA_PORT
configOLLAMA_BASE_URL
configOLLAMA_MODEL
🔐 secretANTHROPIC_API_KEY
🔐 secretCLAUDE_API_KEY
configCLAUDE_MODEL
configANTHROPIC_MODEL
// quality suggestions

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

105/105 tools missing one or more hints — call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); crm_get_leads (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); crm_get_lead_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +102 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/prashantk8ursrvc-ux-odoo-ai-telegram-mcp-1kx8me)](https://m8ven.ai/mcp/prashantk8ursrvc-ux-odoo-ai-telegram-mcp-1kx8me)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b3059454700380db9ec1c6049a619a376b653587
code hash: 07be2490dfc8050446141748362c9d0ae9580dc037c1a4102c34d16b5ffbd788
verified: 8/15/2026, 9:28:52 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client