updated 2026-11-10 04:07 UTC

Automox MCP Server

Repository

An MCP server implementation for Automox

MCP Servers Python Listed MIT

Is Automox MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.6 / 10
Provenance Attested
Signed commits 100%
Last push 27d ago
Advisories None known
Compare Automox MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Automox MCP Server scores 74.6/100 (Grade B), ranked #274 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.6/10; 100% of recent commits are signed; no published advisory affects its latest release (automox-mcp); last pushed 2026-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Automox MCP Server 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 Automox MCP Server 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 Signed

    github.com/AutomoxCommunity/automox-mcp, MIT, last pushed 2026-10-14. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review2
    • Branch Protection4
    • Signed Releases8
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies7
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 4
    Packaging 10
    Pinned-Dependencies 7
    SAST 8
    Security-Policy 10
    Signed-Releases 8
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI automox-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: automox-mcp 2.2.9. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-27 OSSF Scorecard: 7.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Automox MCP Server’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 Automox MCP Server compares in MCP Servers

  1. #158 MCP Server Trello 74.8 +0.2
  2. #159 Search Console MCP 74.8 +0.2
  3. #160 Automox MCP Server 74.6 this agent
  4. #161 YouTube Research MCP 74.6 ±0
  5. #162 Figma Ui MCP 74.4 −0.2

Bars show each HVTrust score; the tick marks Automox MCP Server’s 74.6.

Where the 74.6 comes from

HVTrust dimensions vs the MCP Servers average

74.6 / 100 · 100.0% confidence

Automox MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.7 / 25
9.9 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.1 / 17
1.8 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.4 / 20
0.8 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.4 / 20
2.2 below avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-10-26
Rank Moved
Rank dropped 14 spots (#226 → #240)
2026-10-15
Rank Moved
Rank rose 15 spots (#239 → #224)
2026-10-13
Rank Moved
Rank dropped 11 spots (#220 → #231)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.6/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent
View MCP Servers Report missing data
36.0
Activity sub-score · out of 100
#160
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 B 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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 27 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
15
Forks
5
Last Push
2026-10-14
27 days ago
Commits (4 wk)
1
Downloads (7d)
81
pypi
HN mentions (30d)
—
Open Issues
4
Rank Change
▼2
was #272

Analysis

Activity Inputs

36.0 / 100
StarsRepository reach
7.2 / 30
FreshnessLast push recency
21.2 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
3.6 / 20

Common questions about Automox MCP Server

Automox MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Automox MCP Server publish package provenance?
Yes. Automox MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Automox MCP Server have an OpenSSF Scorecard?
Automox MCP Server has an OpenSSF Scorecard score of 6.6/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 Automox MCP Server actively maintained?
Maintained. Last push was 27 days ago.
What license does Automox MCP Server use?
Automox MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Automox MCP Server's commits signed?
100% of the last 100 commits to Automox MCP Server 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
Automox MCP Server 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
high confidence
Match
Published package metadata matches the tracked repo
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 Automox MCP Server'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
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Automox MCP Server?

For maintainers

HVTrust scores Automox MCP Server 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 20HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-10-26
Rank Moved
Rank dropped 14 spots (#226 → #240)
2026-10-15
Rank Moved
Rank rose 15 spots (#239 → #224)
2026-10-13
Rank Moved
Rank dropped 11 spots (#220 → #231)
2026-10-09
Rank Moved
Rank rose 13 spots (#225 → #212)
2026-10-04
Rank Moved
Rank dropped 23 spots (#194 → #217)
2026-09-26
Rank Moved
Rank dropped 10 spots (#175 → #185)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 623 spots (#790 → #167)
2026-09-23
HVTrust Changed
HVTrust up 49.4pts (28.9 → 78.3)
2026-09-22
Newly Listed
First tracked at rank #790
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 18 spots (#147 → #165)
2026-09-10
Rank Moved
Rank rose 23 spots (#155 → #132)
2026-09-05
Rank Moved
Rank dropped 31 spots (#102 → #133)
2026-09-02
Rank Moved
Rank rose 11 spots (#105 → #94)
2026-08-27
Scorecard Added
OSSF Scorecard: 7.7/10
2026-08-27
Grade Changed
Trust grade C → B
2026-08-27
Rank Moved
Rank rose 212 spots (#297 → #85)
2026-08-27
HVTrust Changed
HVTrust up 16.3pts (63.4 → 79.7)
2026-08-26
Rank Moved
Rank dropped 24 spots (#273 → #297)
2026-08-25
Rank Moved
Rank rose 15 spots (#288 → #273)
2026-08-24
Rank Moved
Rank dropped 16 spots (#272 → #288)
2026-08-22
Rank Moved
Rank rose 11 spots (#283 → #272)
2026-08-20
Rank Moved
Rank dropped 11 spots (#265 → #276)
2026-08-19
Rank Moved
Rank dropped 19 spots (#246 → #265)
2026-08-17
Rank Moved
Rank rose 12 spots (#256 → #244)
2026-08-13
Rank Moved
Rank rose 20 spots (#262 → #242)
GitHub → PyPI: automox-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.6 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/automox-mcp-server.svg)](https://hvtracker.net/agents/automox-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/automox-mcp-server"><img src="https://hvtracker.net/badge/automox-mcp-server.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