Is Openzim MCP safe to use?

Openzim MCP has an HVTrust score of 87.3/100 (Grade A), ranked #34 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Openzim MCP?

Openzim MCP scores 87.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 127 GitHub stars and is categorized under MCP Servers.

Openzim MCP

cameronrye/openzim-mcp

OpenZIM MCP is a modern, secure, and high-performance MCP (Model Context Protocol) server that enables AI models to acce

MCP Servers Python Grade A Listed MIT

87.3/100

Rank #34 of 1320

Compare Openzim MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-09-04 · 0d ago

Recent change

No recent signal change

Is Openzim MCP safe? Openzim MCP scores 87.3/100 (Grade A), ranked #34 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.5/10; 100% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#4 Apify MCP Server — 88.7 (A) → #5 MCP Hangar — 87.5 (A) → #7 Ha MCP — 87.3 (A) → #8 LinkedIn MCP Server — 87.3 (A) →

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-08-25

Rank Moved

Rank rose 28 spots (#58 → #30)

2026-08-25

HVTrust Changed

HVTrust up 3.4pts (83.6 → 87.0)

2026-08-22

Scorecard Added

OSSF Scorecard: 5.4/10

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with Codebase Memory MCP Get email alerts for Openzim MCP View MCP Servers Report missing data

66.0

Activity sub-score · out of 100

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 A 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 →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

127

Forks

Last Push

2026-09-04

today

Commits (4 wk)

Downloads (7d)

1,065

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲4

was #38

Analysis

HVTrust Dimensions vs MCP Servers

87.3 / 100 · 100.0% confidence

Openzim MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

21.9 / 25

12.3 above avg 9.6

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.9 / 17

3.1 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

19.4 / 20

7.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

9.1 / 20

2.8 above avg 6.3

Activity Inputs

66.0 / 100

StarsRepository reach

12.6 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

23.1 / 25

CommunityFork signal

5.3 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

7.5 / 10

OpenSSF Scorecard · scanned Sep 4, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 10

Is Openzim MCP safe?

Public supply-chain signals for Openzim MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Openzim MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Openzim MCP publish package provenance?

Yes. Openzim MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Openzim MCP have an OpenSSF Scorecard?

Openzim MCP has an OpenSSF Scorecard score of 7.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 Openzim MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Openzim MCP use?

Openzim MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Openzim MCP's commits signed?

100% of the last 100 commits to Openzim MCP 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.

Compare Openzim MCP head-to-head

Openzim MCP vs Codebase Memory MCP → Openzim MCP vs SearXNG Search → Openzim MCP vs Supabase MCP Server →

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

Openzim MCP 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 Openzim MCP'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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

Maintain Openzim MCP?

For maintainers

HVTrust scores Openzim MCP 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

2026-08-25

Rank Moved

Rank rose 28 spots (#58 → #30)

2026-08-25

HVTrust Changed

HVTrust up 3.4pts (83.6 → 87.0)

2026-08-22

Scorecard Added

OSSF Scorecard: 5.4/10

2026-08-22

Grade Changed

Trust grade B → A

2026-08-22

Rank Moved

Rank rose 78 spots (#134 → #56)

2026-08-22

HVTrust Changed

HVTrust up 11.6pts (71.2 → 82.8)

2026-08-19

Rank Moved

Rank dropped 10 spots (#131 → #141)

2026-08-13

Rank Moved

Rank dropped 10 spots (#125 → #135)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-08

Newly Listed

First tracked at rank #128

GitHub → PyPI: openzim-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/openzim-mcp.svg)](https://hvtracker.net/agents/openzim-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/openzim-mcp"><img src="https://hvtracker.net/badge/openzim-mcp.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