MCP Zenml
MCP server to connect an MCP client (Cursor, Claude Desktop etc) with your ZenML MLOps and LLMOps pipelines
Is MCP Zenml safe? Promising trust profile, but some evidence still deserves review.
Compare MCP Zenml
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Zenml scores 57.5/100 (Grade C), ranked #705 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 4.2/10; 43% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Zenml compares in MCP Servers
- #386 Rust MCP Sdk 57.7 +0.2
- #387 RPG Maker MV Ultimate MCP 57.7 +0.2
- #388 MCP Zenml 57.5 this agent
- #389 Clio MCP 57.5 ±0
- #390 Icon Composer MCP 57.5 ±0
Bars show each HVTrust score; the tick marks MCP Zenml’s 57.5.
Where the 57.5 comes from
HVTrust dimensions vs the MCP Servers average
57.5 / 100 · 100.0% confidenceMCP Zenml MCP Servers average (775 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
56.8 / 100Supply Chain Trust
Common questions about MCP Zenml
Does MCP Zenml publish package provenance?
Does MCP Zenml have an OpenSSF Scorecard?
Is MCP Zenml actively maintained?
What license does MCP Zenml use?
Are MCP Zenml's commits signed?
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
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 →
- code
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP Zenml'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.
Maintain MCP Zenml?
For maintainers
HVTrust scores MCP Zenml 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-zenml)
<a href="https://hvtracker.net/agents/mcp-zenml"><img src="https://hvtracker.net/badge/mcp-zenml.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON