Is Automox MCP Server safe to use?

Automox MCP Server has an HVTrust score of 77.7/100 (Grade B), ranked #178 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Automox MCP Server?

Automox MCP Server scores 77.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 14 GitHub stars and is categorized under MCP Servers.

Automox MCP Server

AutomoxCommunity/automox-mcp

An MCP server implementation for Automox

MCP Servers Python Listed MIT

Is Automox MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.6 / 10

Provenance Attested

Signed commits 100%

Last push 7d ago

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 77.7/100 (Grade B), ranked #178 of 1325 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 7.6/10; 100% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How Automox MCP Server compares in MCP Servers

#96 MCP Adr Analysis Server 77.8 +0.1
#97 Native DevTools 77.8 +0.1
#98 Automox MCP Server 77.7 this agent
#99 The MCP server for GoReleaser 77.7 ±0
#100 MCP Youtube 77.7 ±0

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

Where the 77.7 comes from

HVTrust dimensions vs the MCP Servers average

77.7 / 100 · 100.0% confidence

Automox MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

22.0 / 25

11.7 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

15.0 / 17

2.8 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

12.1 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

5.6 / 20

1.6 below avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

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

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with another agent Get email alerts for Automox MCP Server View MCP Servers Report missing data

38.8

Activity sub-score · out of 100

#98

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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-19

7 days ago

Commits (4 wk)

Downloads (7d)

115

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼3

was #175

Analysis

Activity Inputs

38.8 / 100

StarsRepository reach

7.1 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

3.9 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

7.6 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

100%

of last 100 commits verified

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 10

Packaging 10

Pinned-Dependencies 7

SAST 8

Security-Policy 10

Signed-Releases 8

Token-Permissions 10

Vulnerabilities 8

Common questions about Automox MCP Server

Public supply-chain signals for Automox MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Automox MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

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 7.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?

Actively maintained. The repository was pushed to within the last 7 day(s).

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

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

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

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)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → none

2026-08-12

Rank Moved

Rank rose 17 spots (#279 → #262)

2026-08-10

Rank Moved

Rank dropped 12 spots (#264 → #276)

2026-08-08

Newly Listed

First tracked at rank #249

GitHub → PyPI: automox-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON