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.

Agentic-Ops Control Plane

PYPI · AGENTIC-OPS · 2 COMPONENTS

Autonomous and governed SRE & MLOps control plane for AI agent platforms.

Available components

remote · agentic-ops-5ebv.onrender.com 33 pypi · agentic-ops 47
0 this week 47 Trust /100

Last scanned (5 hours ago)

Scores higher than 46% of PyPI servers

Category Monitoring and Observability

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 Security91
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects aiohttp 3.13.5, reached via instructor > aiohttp. A fixed version is available. View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 13 of 159 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to nolll77/agentic-ops). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

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.

  • 5 Nov 26 0
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • GHSA-2g87-pp6c-29x5 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112908 affects this package: high ▼ security
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-112911 affects this package: high ▼ security
    • CVE-2026-112912 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-112938 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
  • 4 Nov 26 0
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • GHSA-2g87-pp6c-29x5 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112908 affects this package: high ▼ security
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-112911 affects this package: high ▼ security
    • CVE-2026-112912 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-112938 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
  • 3 Nov 26 0
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • GHSA-2g87-pp6c-29x5 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112908 affects this package: high ▼ security
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-112911 affects this package: high ▼ security
    • CVE-2026-112912 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-112938 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
  • 2 Nov 26 0
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • GHSA-2g87-pp6c-29x5 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112908 affects this package: high ▼ security
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-112911 affects this package: high ▼ security
    • CVE-2026-112912 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-112938 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
  • 1 Nov 26 0
    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • GHSA-2g87-pp6c-29x5 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112908 affects this package: high ▼ security
    • CVE-2026-111750 affects this package: high ▼ security
    • CVE-2026-69243 affects this package: high ▼ security
    • CVE-2026-34993 affects this package: high ▼ security
    • CVE-2026-54274 affects this package: high ▼ security
    • CVE-2026-59881 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-54280 affects this package: high ▼ security
    • CVE-2026-112911 affects this package: high ▼ security
    • CVE-2026-112912 affects this package: high ▼ security
    • CVE-2026-54277 affects this package: high ▼ security
    • CVE-2026-112938 affects this package: high ▼ security
    • CVE-2026-54278 affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-54275 affects this package: high ▼ security
    • CVE-2026-69244 affects this package: high ▼ security
    • CVE-2026-25645 affects this package: high ▼ security
    • CVE-2026-111748 affects this package: high ▼ security
  • 31 Oct 26 0

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-47265 affects this package: high ▼ security
    • CVE-2026-54273 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • CVE-2026-111064 affects this package: high ▼ security
    • CVE-2026-111066 affects this package: high ▼ security
    • GHSA-2g87-pp6c-29x5 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-111063 affects this package: high ▼ security
    • CVE-2026-54276 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-50269 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54279 affects this package: high ▼ security
    • CVE-2026-111065 affects this package: high ▼ security
    • CVE-2026-111749 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112908 affects this package: high ▼ security
    • CVE-2026-111750 affects this package: high ▼ security
  • 20 Oct 26 47

    First indexed and scored.

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 5 Nov 2026 · Analysed pypi/agentic-ops@0.1.14

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 nolll77/agentic-ops
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/nolll77/agentic-ops/.github/workflows/publish.yml@refs/tags/v0.1.14
Rekor log index 3349233259
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:8bd42903ac435a7b11347a2cbb9c32892bd07f16666afcbf3a06e64c0ca8db37

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

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

Vulnerabilities 51 findings
ID CVE Severity Vector Fix available
GHSA-2fqr-mr3j-6wp8 CVE-2026-54279 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-2g87-pp6c-29x5 high yes
GHSA-494j-54xm-rwp3 CVE-2026-111063 medium yes
GHSA-4fvr-rgm6-gqmc CVE-2026-54273 medium yes
GHSA-4m7w-qmgq-4wj5 CVE-2026-54275 low yes
GHSA-5wr8-gcqf-gqf3 CVE-2026-111064 high yes
GHSA-63hw-fmq6-xxg2 CVE-2026-54277 medium yes
GHSA-6cjc-53gc-5rqm CVE-2026-111065 medium yes
GHSA-9x8q-7h8h-wcw9 CVE-2026-54280 low yes
GHSA-9xw5-w5jj-pvcg CVE-2026-111066 high yes
GHSA-cq5v-8q36-5273 CVE-2026-69244 high yes
GHSA-f9xw-jh8m-3mwq CVE-2026-111748 medium yes
GHSA-g3cq-j2xw-wf74 CVE-2026-54278 medium yes
GHSA-gx76-c99x-2c96 CVE-2026-111749 low yes
GHSA-hg6j-4rv6-33pg CVE-2026-47265 medium yes
GHSA-hpj7-wq8m-9hgp CVE-2026-54276 medium yes
GHSA-jg22-mg44-37j8 CVE-2026-34993 medium CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:L yes
GHSA-m6qw-4cw2-hm4m CVE-2026-50269 low yes
GHSA-mfx4-hv73-q22v CVE-2026-69243 medium yes
GHSA-mq44-7p77-q5h7 CVE-2026-59881 medium yes
GHSA-pqxq-w44r-73xw CVE-2026-111750 medium yes
GHSA-xcgm-r5h9-7989 CVE-2026-54274 medium yes
PYSEC-2026-2104 CVE-2026-34993 high CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2105 CVE-2026-47265 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-2106 CVE-2026-50269 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2107 CVE-2026-54273 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2108 CVE-2026-54274 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2109 CVE-2026-54276 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
PYSEC-2026-2110 CVE-2026-54277 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2111 CVE-2026-54278 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2112 CVE-2026-54279 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-2113 CVE-2026-54280 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-237 CVE-2026-54275 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3545 CVE-2026-69244 none yes
PYSEC-2026-3546 CVE-2026-69243 none yes
PYSEC-2026-3547 CVE-2026-59881 none yes
GHSA-567q-5qvw-pf92 CVE-2026-112907 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L yes
GHSA-6627-m3xw-93mp CVE-2026-112908 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L yes
GHSA-69hj-f68j-2879 CVE-2026-112909 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N yes
GHSA-8mx5-7m5m-r77g CVE-2026-112910 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L yes
GHSA-9c4x-gm8v-wgc4 CVE-2026-112911 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H yes
GHSA-9j6q-wvj5-jgjg CVE-2026-112912 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N yes
GHSA-9vhv-jxww-xfm5 CVE-2026-112913 low CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L yes
GHSA-cwqr-hh33-gh44 CVE-2026-112915 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-fq56-3cx3-fjxp CVE-2026-112935 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-j8f7-rjxc-mr56 CVE-2026-112936 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L yes
GHSA-m462-7rxw-wvpg CVE-2026-112938 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H yes
GHSA-rfpc-qcw5-3pc4 CVE-2026-112939 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-v4x8-3wr5-3wq8 CVE-2026-112940 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H yes
GHSA-gc5v-m9x4-r6x2 CVE-2026-25645 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N yes

Showing 50 of 51 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 159 packages
Packages resolved 159
Stale 11
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Agentic-Ops Control Plane MCP server?

Agentic-Ops Control Plane runs locally as a PyPI package, launched with uvx agentic-ops. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · agentic-ops

# add to Claude Code
claude mcp add nolll77-agentic-ops -- uvx agentic-ops
Common questions

What is the Agentic-Ops Control Plane MCP server?

Agentic-Ops Control Plane is an MCP server listed in the public MCP registry as io.github.nolll77/agentic-ops. Autonomous and governed SRE & MLOps control plane for AI agent platforms. This page covers its PyPI package (agentic-ops).

Is the Agentic-Ops Control Plane MCP server safe to use?

Agentic-Ops Control Plane scores 47 out of 100 on VerifyMCP. We recorded 51 known advisories against it as of 5 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.

Is the Agentic-Ops Control Plane MCP server still maintained?

Agentic-Ops Control Plane is still listed as active in the MCP registry. We last reached this channel on 5 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 Agentic-Ops Control Plane MCP server under?

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