Autotask
MCP server for Kaseya Autotask PSA — 39 tools for companies, tickets, projects, time entries, and more
Is Autotask safe? Promising trust profile, but some evidence still deserves review.
Compare Autotask
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Autotask scores 59.3/100 (Grade C), ranked #653 of 1325 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.0/10; 94% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →
How Autotask compares in MCP Servers
- #361 Laravel MCP Companion 59.4 +0.1
- #362 PostgreSQL MCP Server 59.3 ±0
- #363 Autotask 59.3 this agent
- #364 Drawio MCP 59.2 −0.1
- #365 Google Surf MCP 59.2 −0.1
Bars show each HVTrust score; the tick marks Autotask’s 59.3.
Where the 59.3 comes from
HVTrust dimensions vs the MCP Servers average
59.3 / 100 · 100.0% confidenceAutotask MCP Servers average (775 agents)
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 C 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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
61.2 / 100Supply Chain Trust
Common questions about Autotask
Does Autotask publish package provenance?
Does Autotask have an OpenSSF Scorecard?
Is Autotask actively maintained?
What license does Autotask use?
Are Autotask'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 Autotask'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 Autotask?
For maintainers
HVTrust scores Autotask 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/autotask)
<a href="https://hvtracker.net/agents/autotask"><img src="https://hvtracker.net/badge/autotask.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON