updated 2026-11-11 00:08 UTC

AynOps

Repository

An Open Sourced Model Context Protocol (MCP) Local server that gives AI Clients real-time cybersecurity reconnaissance capabilities

MCP Servers Python Listed MIT

Is AynOps safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 6.5 / 10
Provenance None
Signed commits 76%
Last push 3d ago
Advisories None known
Compare AynOps

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: AynOps scores 39.1/100 (Grade D), ranked #1227 of 1387 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.5/10; 76% of recent commits are signed; no published advisory affects its latest release (AynOps); last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How AynOps could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships AynOps and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/AynOps/AynOps, MIT, last pushed 2026-11-08. 76% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.5/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:

    • Code Review7
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions8
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 7
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 4
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 8
    Vulnerabilities 0

  3. Published packages Not linked

    • PyPI AynOps Source link isn't a GitHub repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: AynOps 1.2.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 7.4/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues AynOps’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How AynOps compares in MCP Servers

  1. #705 Glean Remote MCP Server 39.2 +0.1
  2. #706 TalkToFigma MCP 39.2 +0.1
  3. #707 AynOps 39.1 this agent
  4. #708 Terminal MCP Server 39.0 −0.1
  5. #709 Nslookup MCP 38.9 −0.2

Bars show each HVTrust score; the tick marks AynOps’s 39.1.

Where the 39.1 comes from

HVTrust dimensions vs the MCP Servers average

39.1 / 100 · 67.0% confidence

AynOps MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
1.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
1.7 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
16.9 / 20
4.6 above avg 12.3
AdoptionLog-scaled stars · package downloads
3.5 / 20
4.1 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-28
Rank Moved
Rank dropped 11 spots (#1218 → #1229)
2026-10-25
Rank Moved
Rank rose 27 spots (#1251 → #1224)
2026-10-14
Rank Moved
Rank dropped 11 spots (#1223 → #1234)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View MCP Servers Report missing data
57.0
Activity sub-score · out of 100
#707
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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
29
Forks
40
Last Push
2026-11-08
3 days ago
Commits (4 wk)
18
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▲2
was #1229

Analysis

Activity Inputs

57.0 / 100
StarsRepository reach
8.9 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
15.9 / 25
CommunityFork signal
7.5 / 20

Common questions about AynOps

Public trust evidence for AynOps 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 AynOps publish package provenance?
No published build provenance is currently detected for AynOps. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does AynOps have an OpenSSF Scorecard?
AynOps has an OpenSSF Scorecard score of 6.5/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 AynOps actively maintained?
Actively maintained. The repository was pushed to within the last 3 day(s).
What license does AynOps use?
AynOps ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are AynOps's commits signed?
76% of the last 100 commits to AynOps 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
high confidence
Implemented
AynOps appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 AynOps'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
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain AynOps?

For maintainers

HVTrust scores AynOps 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
Rank 22HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1
2026-10-28
Rank Moved
Rank dropped 11 spots (#1218 → #1229)
2026-10-25
Rank Moved
Rank rose 27 spots (#1251 → #1224)
2026-10-14
Rank Moved
Rank dropped 11 spots (#1223 → #1234)
2026-10-09
Rank Moved
Rank dropped 11 spots (#1201 → #1212)
2026-09-30
Rank Moved
Rank dropped 28 spots (#1167 → #1195)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 487 spots (#670 → #1157)
2026-09-23
HVTrust Changed
HVTrust up 9.0pts (31.5 → 40.5)
2026-09-22
Newly Listed
First tracked at rank #670
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 14 spots (#1129 → #1143)
2026-09-07
Rank Moved
Rank dropped 22 spots (#1100 → #1122)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1084 → #1100)
2026-09-05
Rank Moved
Rank dropped 40 spots (#1044 → #1084)
2026-09-04
Rank Moved
Rank dropped 26 spots (#1018 → #1044)
2026-09-03
Rank Moved
Rank dropped 57 spots (#961 → #1018)
2026-09-02
Rank Moved
Rank dropped 49 spots (#912 → #961)
2026-09-01
Rank Moved
Rank dropped 39 spots (#873 → #912)
2026-08-31
Rank Moved
Rank dropped 27 spots (#846 → #873)
2026-08-30
Rank Moved
Rank dropped 37 spots (#809 → #846)
2026-08-29
Scorecard Added
OSSF Scorecard: 7.4/10
2026-08-29
Rank Moved
Rank rose 408 spots (#1217 → #809)
2026-08-29
HVTrust Changed
HVTrust up 22.2pts (18.6 → 40.8)
2026-08-28
Rank Moved
Rank dropped 14 spots (#1203 → #1217)
2026-08-27
Rank Moved
Rank dropped 10 spots (#1193 → #1203)
2026-08-26
Rank Moved
Rank dropped 44 spots (#1149 → #1193)
2026-08-18
Rank Moved
Rank dropped 12 spots (#1126 → #1138)
2026-08-16
Rank Moved
Rank dropped 24 spots (#1111 → #1135)
GitHub → PyPI: AynOps

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 39.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/aynops.svg)](https://hvtracker.net/agents/aynops)
HTML:
<a href="https://hvtracker.net/agents/aynops"><img src="https://hvtracker.net/badge/aynops.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.4 · Raw JSON