Is Astravue MCP safe to use?

Astravue MCP has an HVTrust score of 44.3/100 (Grade D), ranked #925 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Astravue MCP?

Astravue MCP scores 44.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

Astravue MCP

AstravueOrg/astravue-mcp-server

Official MCP server for Astravue — manage projects, tasks, time tracking, and teams through AI

MCP Servers Grade D Listed Apache-2.0

44.3/100

Rank #925 of 1320

Compare Astravue MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-25 · 10d ago

Recent change

Rank +7

Is Astravue MCP safe? Astravue MCP scores 44.3/100 (Grade D), ranked #925 of 1320 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 3.6/10; 5% of recent commits are signed; last pushed 2026-08-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#504 Anilist MCP — 44.5 (D) → #505 Propresenter MCP — 44.4 (D) → #507 1password MCP — 44.3 (D) → #508 Excel MCP Server — 44.1 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 16 spots (#909 → #925)

2026-09-03

Rank Moved

Rank dropped 53 spots (#856 → #909)

2026-09-02

Rank Moved

Rank dropped 16 spots (#840 → #856)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

37.7

Activity sub-score · out of 100

#506

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 D 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-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-08-25

10 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼16

was #909

Analysis

HVTrust Dimensions vs MCP Servers

44.3 / 100 · 100.0% confidence

Astravue MCP MCP Servers average (778 agents)

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

4.8 / 25

4.7 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

13.2 / 20

1.0 above avg 12.2

AdoptionLog-scaled stars · package downloads

2.7 / 20

3.5 below avg 6.2

Activity Inputs

37.7 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

23.6 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

1.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.6 / 10

OpenSSF Scorecard · scanned Sep 1, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 3

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Is Astravue MCP safe?

Public trust evidence for Astravue MCP 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 Astravue MCP publish package provenance?

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

Does Astravue MCP have an OpenSSF Scorecard?

Astravue MCP has an OpenSSF Scorecard score of 3.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 Astravue MCP actively maintained?

Maintained. Last push was 10 days ago.

What license does Astravue MCP use?

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

Are Astravue MCP's commits signed?

5% of the last 100 commits to Astravue MCP 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

medium confidence

Implemented

Astravue MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 Astravue MCP'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: marketplace → declared

Maintain Astravue MCP?

For maintainers

HVTrust scores Astravue MCP 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-04

Rank Moved

Rank dropped 16 spots (#909 → #925)

2026-09-03

Rank Moved

Rank dropped 53 spots (#856 → #909)

2026-09-02

Rank Moved

Rank dropped 16 spots (#840 → #856)

2026-09-01

Rank Moved

Rank dropped 31 spots (#809 → #840)

2026-08-31

Rank Moved

Rank dropped 36 spots (#773 → #809)

2026-08-30

Rank Moved

Rank dropped 27 spots (#746 → #773)

2026-08-29

Rank Moved

Rank dropped 49 spots (#697 → #746)

2026-08-28

Rank Moved

Rank dropped 24 spots (#673 → #697)

2026-08-27

Scorecard Added

OSSF Scorecard: 3.6/10

2026-08-27

Rank Moved

Rank rose 512 spots (#1185 → #673)

2026-08-27

HVTrust Changed

HVTrust up 25.1pts (18.8 → 43.9)

2026-08-26

Rank Moved

Rank dropped 48 spots (#1137 → #1185)

2026-08-24

Rank Moved

Rank rose 110 spots (#1245 → #1135)

2026-08-24

HVTrust Changed

HVTrust up 3.0pts (15.9 → 18.9)

2026-08-24

Activity Score Changed

Activity score up 16pts (23 → 39)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1215 → #1241)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-12

Rank Moved

Rank rose 17 spots (#1227 → #1210)

2026-08-10

Rank Moved

Rank dropped 76 spots (#1152 → #1228)

2026-08-08

Newly Listed

First tracked at rank #1131

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/astravue-mcp.svg)](https://hvtracker.net/agents/astravue-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/astravue-mcp"><img src="https://hvtracker.net/badge/astravue-mcp.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.3 · Raw JSON