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.

io.github.AynOps/AynOps

PYPI · AYNOPS

AynOps is a reconnaissance focused MCP Server which gives reconnaissance capabilities to AI Clients

Available components

0 this week 37 Trust /100

Last scanned (20 hours ago)

Scores higher than 29% of PyPI servers

Category Security

Recent critical change

GHSA-6q48-6c7w-9gw2 affects this package (21 Oct 2026). See the changelog before you install this server.

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 Security99
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 33 of 34 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 33 of 34 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 26 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →

What we tested

Checks we ran (8)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Security disclosure

Checks we could not complete (6)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +5
    • Install scripts: unverified → pass ▲ security
    • The code this package runs automatically changed: its declared build backend security
  • 18 Nov 26 −5
    • Install scripts: pass → unverified ▼ security
    • The code this package runs automatically changed: its declared build backend security
  • 26 Oct 26 0
    • Stability: Stability not yet verified: our sandbox could not run this package, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess. functional
  • 25 Oct 26 +2
    • Install scripts: partial → pass ▲ security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • The code this package runs automatically changed: build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module) → its declared build backend security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 1.1.2 → 1.2.1 functional
  • 22 Oct 26 0
    • GHSA-6q48-6c7w-9gw2 no longer affects this package ▲ security
    • Known CVEs: fail → partial ▲ security
    • Score status: failed → scored ▲ functional
  • 21 Oct 26 0
    • GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
    • Known CVEs: partial → fail ▼ critical
    • Score status: scored → failed ▼ critical
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 0
    • License: fail → unverified ▼ functional
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 21 Nov 2026 · Analysed pypi/AynOps@1.2.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

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

Dependencies 33 packages
Packages resolved 33
Stale 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

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 io.github.AynOps/AynOps MCP server?

io.github.AynOps/AynOps runs locally as a PyPI package, launched with uvx AynOps. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · AynOps

# add to Claude Code
claude mcp add aynops-aynops -- uvx AynOps
Common questions

What is the io.github.AynOps/AynOps MCP server?

io.github.AynOps/AynOps is an MCP server listed in the public MCP registry as io.github.AynOps/AynOps. AynOps is a reconnaissance focused MCP Server which gives reconnaissance capabilities to AI Clients. This page covers its PyPI package (AynOps).

Is the io.github.AynOps/AynOps MCP server safe to use?

io.github.AynOps/AynOps scores 37 out of 100 on VerifyMCP. 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 io.github.AynOps/AynOps MCP server still maintained?

io.github.AynOps/AynOps is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.AynOps/AynOps MCP server?

VerifyMCP ran 8 checks on io.github.AynOps/AynOps, covering Malware scan, Known CVEs, Install scripts, Dependency health and 4 more. 6 items could not be completed, a gap on our side rather than a finding about io.github.AynOps/AynOps: License, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.