Is Autotask safe to use?

Autotask has an HVTrust score of 54.7/100 (Grade C), ranked #865 of 1387 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Autotask?

Autotask scores 54.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 62 GitHub stars and is categorized under MCP Servers.

Autotask

Repository Website by WYRE-AI

MCP server for Kaseya Autotask PSA — 39 tools for companies, tickets, projects, time entries, and more

MCP Servers TypeScript Listed Apache-2.0

Is Autotask safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.6 / 10

Provenance None

Signed commits 94%

Last push 2d ago

Compare Autotask

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Autotask scores 54.7/100 (Grade C), ranked #865 of 1387 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 5.6/10; 94% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Autotask 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.

Raise the OSSF Scorecard from 5.6 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +7.1 → 61.8 C · #359 of 779

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Autotask and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/WYRE-AI/autotask-mcp, Apache-2.0, last pushed 2026-11-09. 94% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 5.6/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:
- Code Review8
- Branch Protection8
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies8
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 9

CII-Best-Practices 0

Code-Review 8

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 8

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages None

Distributed as the container image ghcr.io/wyre-technology/autotask-mcp:v2.31.1; HVTracker doesn't check that registry's source link yet.

Changes to this chain

2026-09-08 OSSF Scorecard: 5.8/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

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

Bars show each HVTrust score; the tick marks Autotask’s 54.7.

Where the 54.7 comes from

HVTrust dimensions vs the MCP Servers average

54.7 / 100 · 100.0% confidence

Autotask MCP Servers average (779 agents)

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

11.7 / 25

0.9 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.0 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

13.6 / 20

1.3 above avg 12.3

AdoptionLog-scaled stars · package downloads

4.3 / 20

3.3 below avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-05

Rank Moved

Rank dropped 53 spots (#797 → #850)

2026-11-04

Rank Moved

Rank dropped 46 spots (#751 → #797)

2026-10-16

Rank Moved

Rank dropped 10 spots (#719 → #729)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.6/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent View MCP Servers Report missing data

54.8

Activity sub-score · out of 100

#479

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

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-09

2 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #865

Analysis

Activity Inputs

54.8 / 100

StarsRepository reach

10.8 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

8.6 / 20

Common questions about Autotask

Public trust evidence for Autotask is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Autotask publish package provenance?

No published build provenance is currently detected for Autotask. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Autotask have an OpenSSF Scorecard?

Autotask has an OpenSSF Scorecard score of 5.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 Autotask actively maintained?

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

What license does Autotask use?

Autotask ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Autotask's commits signed?

94% of the last 100 commits to Autotask 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

Autotask 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

N/A

No package source configured

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

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-11-05

Rank Moved

Rank dropped 53 spots (#797 → #850)

2026-11-04

Rank Moved

Rank dropped 46 spots (#751 → #797)

2026-10-16

Rank Moved

Rank dropped 10 spots (#719 → #729)

2026-10-07

Rank Moved

Rank rose 10 spots (#705 → #695)

2026-10-05

Rank Moved

Rank rose 23 spots (#732 → #709)

2026-10-01

Rank Moved

Rank dropped 40 spots (#682 → #722)

2026-09-27

Rank Moved

Rank dropped 19 spots (#652 → #671)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 94 spots (#740 → #646)

2026-09-23

HVTrust Changed

HVTrust up 29.2pts (30.1 → 59.3)

2026-09-22

Newly Listed

First tracked at rank #740

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Grade Changed

Trust grade D → C

2026-09-17

Rank Moved

Rank rose 524 spots (#1161 → #637)

2026-09-17

HVTrust Changed

HVTrust up 19.4pts (39.9 → 59.3)

2026-09-16

Grade Changed

Trust grade C → D

2026-09-16

Rank Moved

Rank dropped 517 spots (#644 → #1161)

2026-09-16

HVTrust Changed

HVTrust down 18.9pts (58.8 → 39.9)

2026-09-12

Rank Moved

Rank dropped 18 spots (#621 → #639)

2026-09-11

Grade Changed

Trust grade D → C

2026-09-11

Rank Moved

Rank rose 528 spots (#1149 → #621)

2026-09-11

HVTrust Changed

HVTrust up 19.5pts (40.1 → 59.6)

2026-09-10

Grade Changed

Trust grade C → D

2026-09-10

Rank Moved

Rank dropped 549 spots (#600 → #1149)

2026-09-10

HVTrust Changed

HVTrust down 19.6pts (59.7 → 40.1)

2026-09-08

Scorecard Added

OSSF Scorecard: 5.8/10

2026-09-08

Grade Changed

Trust grade D → C

2026-09-08

Rank Moved

Rank rose 712 spots (#1310 → #598)

2026-09-08

HVTrust Changed

HVTrust up 40.1pts (19.5 → 59.6)

2026-09-07

Rank Moved

Rank dropped 21 spots (#1289 → #1310)

2026-09-07

HVTrust Changed

HVTrust down 4.6pts (24.1 → 19.5)

2026-09-05

Rank Moved

Rank dropped 14 spots (#1266 → #1280)

2026-09-04

Rank Moved

Rank dropped 12 spots (#1254 → #1266)

2026-09-03

Rank Moved

Rank dropped 30 spots (#1224 → #1254)

2026-09-02

Rank Moved

Rank dropped 36 spots (#1188 → #1224)

2026-09-01

Rank Moved

Rank dropped 40 spots (#1148 → #1188)

2026-08-31

Rank Moved

Rank dropped 27 spots (#1121 → #1148)

2026-08-30

Rank Moved

Rank dropped 44 spots (#1077 → #1121)

2026-08-29

Rank Moved

Rank dropped 46 spots (#1031 → #1077)

2026-08-28

Rank Moved

Rank dropped 32 spots (#999 → #1031)

2026-08-27

Rank Moved

Rank dropped 16 spots (#983 → #999)

2026-08-26

Rank Moved

Rank dropped 99 spots (#884 → #983)

2026-08-17

Rank Moved

Rank rose 11 spots (#899 → #888)

2026-08-16

Rank Moved

Rank dropped 25 spots (#874 → #899)

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/autotask.svg)](https://hvtracker.net/agents/autotask)
            
HTML:
            <a href="https://hvtracker.net/agents/autotask"><img src="https://hvtracker.net/badge/autotask.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Autotask

How Autotask could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Autotask compares in MCP Servers

Where the 54.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Autotask

AI agent surface

Maintain Autotask?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers