Automox MCP Server
An MCP server implementation for Automox
Compare Automox MCP Server
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →Strong public trust posture, backed by multiple independent signals.
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
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
Activity & Reach
Analysis
HVTrust Dimensions vs MCP Servers
79.3 / 100 · 100.0% confidenceAutomox MCP Server MCP Servers average (778 agents)
Activity Inputs
44.0 / 100Supply Chain Trust
Is Automox MCP Server safe?
Does Automox MCP Server publish package provenance?
Does Automox MCP Server have an OpenSSF Scorecard?
Is Automox MCP Server actively maintained?
What license does Automox MCP Server use?
Are Automox MCP Server's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/automox-mcp-server)
<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
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