Is Ocm MCP Server safe to use?

Ocm MCP Server has an HVTrust score of 44.3/100 (Grade D), ranked #1080 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Ocm MCP Server?

Ocm MCP Server scores 44.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 9 GitHub stars and is categorized under MCP Servers.

Ocm MCP Server

sandeepbazar/ocm-mcp-server

Moved to github.com/ocm-mcp-server/ocm-mcp-server — this repository is a signpost only.

MCP Servers Needs review Unlicensed

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

OSSF Scorecard 2.3 / 10

Provenance Attested

Signed commits 50%

Last push 28d ago

Compare Ocm MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Ocm MCP Server scores 44.3/100 (Grade D), ranked #1080 of 1325 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 2.3/10; 50% of recent commits are signed; last pushed 2026-08-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ocm MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Ocm MCP Server’s 44.3.

Where the 44.3 comes from

HVTrust dimensions vs the MCP Servers average

44.3 / 100 · 100.0% confidence

Ocm MCP Server MCP Servers average (775 agents)

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

12.9 / 25

2.6 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

2.0 / 17

10.2 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.0 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

4.4 / 20

2.8 below avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Warning Issued

Warning: eligibility issues detected

Maintainer Checklist

Declare an open license Publish a clear OSI-approved license so usage and maintenance terms are independently verifiable.

Raise Scorecard signals Current OSSF Scorecard is 2.3/10. Tighten the weakest checks to improve public safety evidence.

Review Flags

[4.1.1] no declared license (GitHub license field is null)

Compare with another agent Get email alerts for Ocm MCP Server View MCP Servers Report missing data

34.6

Activity sub-score · out of 100

#632

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 D 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-26

Activity & Reach

Stars

Forks

Last Push

2026-08-29

28 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #1081

Analysis

Activity Inputs

34.6 / 100

StarsRepository reach

6.0 / 30

FreshnessLast push recency

21.1 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

2.3 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

50%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 2

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 0

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 10

Common questions about Ocm MCP Server

Public trust evidence for Ocm MCP Server 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 Ocm MCP Server publish package provenance?

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

Does Ocm MCP Server have an OpenSSF Scorecard?

Ocm MCP Server has an OpenSSF Scorecard score of 2.3/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 Ocm MCP Server actively maintained?

Maintained. Last push was 28 days ago.

What license does Ocm MCP Server use?

Ocm MCP Server ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Ocm MCP Server's commits signed?

50% of the last 100 commits to Ocm MCP Server 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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

Warning

1 package source mismatch detected

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 Ocm MCP Server'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

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-03

Mcp Status Changed

Detected MCP server support changed: implemented → none

2026-09-03

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

Maintain Ocm MCP Server?

For maintainers

HVTrust scores Ocm MCP Server 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-09-23

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Warning Issued

Warning: eligibility issues detected

2026-09-23

Rank Moved

Rank rose 97 spots (#1170 → #1073)

2026-09-23

HVTrust Changed

HVTrust up 24.2pts (20.3 → 44.5)

2026-09-22

Newly Listed

First tracked at rank #1170

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 12 spots (#1056 → #1068)

2026-09-11

Rank Moved

Rank dropped 19 spots (#1021 → #1040)

2026-09-09

Rank Moved

Rank dropped 16 spots (#1005 → #1021)

2026-09-08

Rank Moved

Rank dropped 12 spots (#993 → #1005)

2026-09-07

Rank Moved

Rank dropped 57 spots (#936 → #993)

2026-09-06

Rank Moved

Rank rose 24 spots (#960 → #936)

2026-09-04

Rank Moved

Rank dropped 27 spots (#935 → #962)

2026-09-03

License Changed

License classification changed from open to unlicensed

2026-09-03

Mcp Status Changed

Detected MCP server support changed: implemented → none

2026-09-03

Drift Warning Raised

Package-provenance drift warning: package metadata no longer clearly points at this repo

2026-09-03

Scorecard Added

OSSF Scorecard: 2.3/10

2026-09-03

Warning Issued

Warning: eligibility issues detected

2026-09-03

Grade Changed

Trust grade C → D

2026-09-03

Rank Moved

Rank dropped 389 spots (#546 → #935)

2026-09-03

HVTrust Changed

HVTrust down 11.9pts (55.7 → 43.8)

2026-09-02

Rank Moved

Rank dropped 21 spots (#525 → #546)

2026-09-01

Rank Moved

Rank dropped 12 spots (#513 → #525)

2026-08-31

Rank Moved

Rank dropped 27 spots (#486 → #513)

2026-08-29

Rank Moved

Rank dropped 216 spots (#274 → #490)

2026-08-29

HVTrust Changed

HVTrust down 8.5pts (64.5 → 56.0)

2026-08-29

Activity Score Changed

Activity score down 29pts (60 → 31)

2026-08-28

Rank Moved

Rank dropped 14 spots (#260 → #274)

2026-08-27

Grade Changed

Trust grade B → C

2026-08-27

Rank Moved

Rank dropped 20 spots (#240 → #260)

2026-08-26

Rank Moved

Rank dropped 23 spots (#217 → #240)

2026-08-24

Rank Moved

Rank dropped 17 spots (#204 → #221)

2026-08-22

Rank Moved

Rank rose 25 spots (#228 → #203)

2026-08-19

Rank Moved

Rank dropped 14 spots (#205 → #219)

2026-08-17

Rank Moved

Rank rose 14 spots (#217 → #203)

2026-08-13

Rank Moved

Rank dropped 14 spots (#200 → #214)

2026-08-12

Rank Moved

Rank rose 11 spots (#211 → #200)

2026-08-10

Rank Moved

Rank dropped 18 spots (#191 → #209)

2026-08-08

Newly Listed

First tracked at rank #194

GitHub → PyPI: ocm-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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