github not analyzable

zenml-io/mcp-zenml

github

MCP server to connect an MCP client (Cursor, Claude Desktop etc) with your ZenML MLOps and LLMOps pipelines

maintainer
zenml-io
license
MIT
first seen
2026-05-22
last seen
2026-06-17
releases · 30d
0
short id
risk 38/100 · heuristic grade
C elevated

Source not yet analyzed — this grade rests on attested signals (CVEs, supply-chain) only. It is a floor: reading the code could raise it, not lower it.

  • capability exposureinferred+24
  • tool safetyinferred+19
  • trust mitigatorsmixed−5

inferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 8m ago · see ecosystem CVEs →

risk trajectory 1 movements
  • C · 35C · 38
capability exposure grade factor +24
Inferred surface — each links to servers holding it:
vulnerabilities 0 CVEs

No known CVEs for this server.

tool safety 3 findings · grade factor +19
  1. hightool shadowinglist_secrets

    tool "list_secrets" shadows a verified server's tool

    shadows I4cTime/quantum_ring

  2. mediumpurpose mismatchlist_secrets

    benign-looking name carries secrets

  3. lowexfiltration combo

    sensitive read and network capabilities split across this server's tools

embed badge readme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/mcpso:zenml-io/mcp-zenml/badge.svg)](https://mcpobservatory.com/servers/mcpso:zenml-io/mcp-zenml/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of zenml-io.