Automox MCP Server

An MCP server implementation for Automox

MCP Servers Python Grade B Listed MIT
79.3/100
Rank #102 of 1320
Compare Automox MCP Server

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-02 · 2d ago
Recent change
Rank

Is Automox MCP Server safe? Automox MCP Server scores 79.3/100 (Grade B), ranked #102 of 1320 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.7/10; 100% of recent commits are signed; last pushed 2026-09-02. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
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
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.
44.0
Activity sub-score · out of 100
#44

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-09-04 23:32 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
12
Forks
6
Last Push
2026-09-02
2 days ago
Commits (4 wk)
4?
Downloads (7d)
254
pypi
HN mentions (30d)
Open Issues
4
Rank Change
▼2
was #100

Analysis

HVTrust Dimensions vs MCP Servers

79.3 / 100 · 100.0% confidence

Automox MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
22.1 / 25
12.5 above avg 9.6
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
3.2 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.9 / 20
in line with avg 6.3

Activity Inputs

44.0 / 100
StarsRepository reach
6.7 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
3.9 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
7.7 / 10
OpenSSF Scorecard · scanned Sep 4, 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 10

Is Automox MCP Server safe?

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.7/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 2 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-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.

Reputation Timeline

Signal history
Rank 12Listed 1Surface 1HVTrust 1Grade 1Scorecard 1
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 79.3 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.3 · Raw JSON