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-lint

PYPI · ODOO-LINTER

Lint and fix Odoo addons: pylint-odoo and OCA checks, translation files and upgrades.

Available components

0 this week 66 Trust /100

Last scanned (14 hours ago)

Scores higher than 58% of PyPI servers

Category Developer Tools

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs maturin at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to GetFluvo/odoo-lint). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 13 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 532 tokens (~133/item across 4 items; 4 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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.

What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
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 21 Nov 2026 · Analysed pypi/odoo-linter@0.1.0a21

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo GetFluvo/odoo-lint
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/GetFluvo/odoo-lint/.github/workflows/release.yml@refs/tags/v0.1.0-alpha.21
Rekor log index 3741400231
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:59801bafcf3f0a090283b7d1384906c800118081caf8001d5e1d51ebc98c0f2a

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool maturin

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~444 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
check ~114

Lint Odoo addons (Python, manifests, .po/.pot translations) and list the violations, marking the ones `fix` can fix.

NameTypeReqDescription
ignorearray–Rules to skip
odoo_versionstring–Target Odoo version such as 18.0; default: from the project's configuration
pathsarray–Addon directories or files; default: the current directory
selectarray–Only these rules: codes, names or code prefixes such as PO or C81

No output schema declared.

No examples provided.

fix ~151

Apply odoo-lint's automatic fixes to Odoo addons and list what is left. Use dry_run to see a diff first.

NameTypeReqDescription
dry_runboolean–Return the changes as a diff instead of writing them (default false)
ignorearray–Rules to skip
odoo_versionstring–Target Odoo version such as 18.0; default: from the project's configuration
pathsarray–Addon directories or files; default: the current directory
selectarray–Only these rules: codes, names or code prefixes such as PO or C81
unsafeboolean–Also apply unsafe fixes, which can change behaviour (default false)

No output schema declared.

No examples provided.

rule ~58

Explain a rule by code or name (e.g. W8161 or prefer-env-translation): what it checks, why, and how to fix it. Without a rule, list all rules.

NameTypeReqDescription
rulestring–Rule code or name

No output schema declared.

No examples provided.

upgrade_check ~121

Report what Odoo addons need to run on a newer Odoo version, per version step and module: how many changes, how many `fix` makes automatically, how many need review or manual work.

NameTypeReqDescription
addons_patharray–Folders with the addons of the target version, Odoo's included: also check views, fields, XML ids and models against them
pathsarray–Addon directories; default: the current directory
targetstringyesOdoo version to upgrade to, e.g. 19.0

No output schema declared.

No examples provided.

Install

How do I install the odoo-lint MCP server?

odoo-lint runs locally as a PyPI package, launched with uvx odoo-linter mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · odoo-linter

# add to Claude Code
claude mcp add getfluvo-odoo-lint -- uvx odoo-linter mcp
Common questions

What is the odoo-lint MCP server?

odoo-lint is an MCP server listed in the public MCP registry as io.github.GetFluvo/odoo-lint. Lint and fix Odoo addons: pylint-odoo and OCA checks, translation files and upgrades. This page covers its PyPI package (odoo-linter).

Is the odoo-lint MCP server safe to use?

odoo-lint scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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-lint MCP server expose?

odoo-lint exposes 4 tools: check, fix, upgrade_check, rule. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.

Is the odoo-lint MCP server still maintained?

odoo-lint is still listed as active in the MCP registry. We last reached this channel on 21 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-lint MCP server under?

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

What did VerifyMCP test on the odoo-lint MCP server?

VerifyMCP ran 14 checks on odoo-lint, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about odoo-lint: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.