updated 2026-09-26 06:32 UTC

MCP Odoo

erpipe-org/mcp-odoo

Odoo MCP for AI agents — gated writes, multi-instance. Hosted product: https://erpipe.com

MCP Servers Python Listed MIT

Is MCP Odoo safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.5 / 10
Provenance None
Signed commits 15%
Last push 32d ago
Compare MCP Odoo

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Odoo scores 52.4/100 (Grade C), ranked #869 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.5/10; 15% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Odoo compares in MCP Servers

  1. #490 SunoMCP 52.5 +0.1
  2. #491 Longbridge MCP 52.5 +0.1
  3. #492 MCP Odoo 52.4 this agent
  4. #493 Apideck Libraries MCP 52.2 −0.2
  5. #494 Nutrition MCP 52.2 −0.2

Bars show each HVTrust score; the tick marks MCP Odoo’s 52.4.

Where the 52.4 comes from

HVTrust dimensions vs the MCP Servers average

52.4 / 100 · 100.0% confidence

MCP Odoo MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.1 / 25
5.2 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
0.7 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
9.9 / 20
2.2 below avg 12.1
AdoptionLog-scaled stars · package downloads
10.1 / 20
2.9 above avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-24
Rank Moved
Rank dropped 39 spots (#823 → #862)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 32 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for MCP Odoo View MCP Servers Report missing data
46.9
Activity sub-score · out of 100
#492
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 32 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
415
Forks
190
Last Push
2026-08-25
32 days ago
Commits (4 wk)
0
Downloads (7d)
776
pypi
HN mentions (30d)
—
Open Issues
2
Rank Change
▲2
was #871

Analysis

Activity Inputs

46.9 / 100
StarsRepository reach
15.7 / 30
FreshnessLast push recency
20.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.5 / 10
OpenSSF Scorecard · scanned Sep 23, 2026
Signed Commits
15%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 1
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 4
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Common questions about MCP Odoo

Public trust evidence for MCP Odoo is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does MCP Odoo publish package provenance?
No published build provenance is currently detected for MCP Odoo. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Odoo have an OpenSSF Scorecard?
MCP Odoo has an OpenSSF Scorecard score of 3.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP Odoo actively maintained?
Slowing down. Last push was 32 days ago — keep an eye on whether activity resumes.
What license does MCP Odoo use?
MCP Odoo ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Odoo's commits signed?
15% of the last 100 commits to MCP Odoo are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP Odoo appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to MCP Odoo's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Odoo?

For maintainers

HVTrust scores MCP Odoo from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 24Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1
2026-09-24
Rank Moved
Rank dropped 39 spots (#823 → #862)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 222 spots (#1045 → #823)
2026-09-23
HVTrust Changed
HVTrust up 29.8pts (23.9 → 53.7)
2026-09-22
Newly Listed
First tracked at rank #1045
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 52 spots (#762 → #814)
2026-09-13
Rank Moved
Rank dropped 24 spots (#727 → #751)
2026-09-12
Rank Moved
Rank dropped 10 spots (#717 → #727)
2026-09-09
Rank Moved
Rank dropped 11 spots (#693 → #704)
2026-09-07
Rank Moved
Rank dropped 41 spots (#650 → #691)
2026-09-06
Rank Moved
Rank dropped 19 spots (#631 → #650)
2026-09-05
Rank Moved
Rank dropped 73 spots (#558 → #631)
2026-09-04
Rank Moved
Rank dropped 23 spots (#535 → #558)
2026-09-03
Rank Moved
Rank dropped 31 spots (#504 → #535)
2026-09-02
Rank Moved
Rank dropped 24 spots (#480 → #504)
2026-09-01
Rank Moved
Rank dropped 16 spots (#464 → #480)
2026-08-31
Rank Moved
Rank dropped 33 spots (#431 → #464)
2026-08-30
Rank Moved
Rank rose 11 spots (#442 → #431)
2026-08-29
Rank Moved
Rank dropped 14 spots (#428 → #442)
2026-08-28
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-28
Grade Changed
Trust grade D → C
2026-08-28
Rank Moved
Rank rose 410 spots (#838 → #428)
2026-08-28
HVTrust Changed
HVTrust up 22.1pts (35.5 → 57.6)
2026-08-27
Rank Moved
Rank dropped 24 spots (#814 → #838)
2026-08-26
Rank Moved
Rank dropped 108 spots (#706 → #814)
2026-08-21
Rank Moved
Rank dropped 13 spots (#698 → #711)
2026-08-16
Rank Moved
Rank dropped 11 spots (#677 → #688)
2026-08-14
Rank Moved
Rank rose 10 spots (#689 → #679)
2026-08-13
Rank Moved
Rank dropped 12 spots (#677 → #689)
2026-08-10
Rank Moved
Rank dropped 31 spots (#648 → #679)
2026-08-08
Newly Listed
First tracked at rank #648
GitHub → PyPI: odoo-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 52.4 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-odoo.svg)](https://hvtracker.net/agents/mcp-odoo)
HTML:
<a href="https://hvtracker.net/agents/mcp-odoo"><img src="https://hvtracker.net/badge/mcp-odoo.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON