Is Qase Test Management safe to use?

Qase Test Management has an HVTrust score of 81.7/100 (Grade A), ranked #126 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Qase Test Management?

Qase Test Management scores 81.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 32 GitHub stars and is categorized under MCP Servers.

Qase Test Management

qase-tms/qase-mcp-server

An official Qase MCP server

MCP Servers TypeScript Listed MIT

Is Qase Test Management safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.1 / 10

Provenance Attested

Signed commits 39%

Last push yesterday

Compare Qase Test Management

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Qase Test Management scores 81.7/100 (Grade A), ranked #126 of 1325 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.1/10; 39% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Qase Test Management compares in MCP Servers

#58 Delimit — API Governance for AI Coding Assistants 81.8 +0.1
#59 Auth0 MCP Server 81.7 ±0
#60 Qase Test Management 81.7 this agent
#61 Discord MCP 81.7 ±0
#62 Talkthrough MCP 81.3 −0.4

Bars show each HVTrust score; the tick marks Qase Test Management’s 81.7.

Where the 81.7 comes from

HVTrust dimensions vs the MCP Servers average

81.7 / 100 · 100.0% confidence

Qase Test Management MCP Servers average (775 agents)

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

18.3 / 25

8.0 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

14.5 / 17

2.3 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.3 / 20

5.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

8.6 / 20

1.4 above avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

Maintainer Checklist

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 Qase Test Management View MCP Servers Report missing data

55.6

Activity sub-score · out of 100

#60

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

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

4,848

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #128

Analysis

Activity Inputs

55.6 / 100

StarsRepository reach

9.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

16.7 / 25

CommunityFork signal

4.8 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.1 / 10

OpenSSF Scorecard · scanned Sep 6, 2026 (refresh pending)

Signed Commits

39%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 9

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10

Common questions about Qase Test Management

Public supply-chain signals for Qase Test Management are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Qase Test Management carries less obvious unverified-evidence risk than projects with thin signals.

Does Qase Test Management publish package provenance?

Yes. Qase Test Management's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Qase Test Management have an OpenSSF Scorecard?

Qase Test Management has an OpenSSF Scorecard score of 7.1/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 Qase Test Management actively maintained?

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

What license does Qase Test Management use?

Qase Test Management ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Qase Test Management's commits signed?

39% of the last 100 commits to Qase Test Management 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

Qase Test Management 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 Qase Test Management'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

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Qase Test Management?

For maintainers

HVTrust scores Qase Test Management 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 573 spots (#705 → #132)

2026-09-23

HVTrust Changed

HVTrust up 50.5pts (30.7 → 81.2)

2026-09-22

Newly Listed

First tracked at rank #705

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Scorecard Added

OSSF Scorecard: 7.1/10

2026-09-05

Grade Changed

Trust grade B → A

2026-09-05

Rank Moved

Rank rose 176 spots (#281 → #105)

2026-09-05

HVTrust Changed

HVTrust up 14.8pts (66.7 → 81.5)

2026-09-03

Grade Changed

Trust grade D → B

2026-09-03

Rank Moved

Rank rose 684 spots (#958 → #274)

2026-09-03

HVTrust Changed

HVTrust up 25.9pts (40.8 → 66.7)

2026-09-02

Rank Moved

Rank dropped 50 spots (#908 → #958)

2026-09-01

Rank Moved

Rank dropped 28 spots (#880 → #908)

2026-08-31

Rank Moved

Rank dropped 31 spots (#849 → #880)

2026-08-30

Rank Moved

Rank dropped 35 spots (#814 → #849)

2026-08-29

Rank Moved

Rank dropped 46 spots (#768 → #814)

2026-08-28

Rank Moved

Rank dropped 30 spots (#738 → #768)

2026-08-27

Rank Moved

Rank dropped 22 spots (#716 → #738)

2026-08-26

Rank Moved

Rank dropped 97 spots (#619 → #716)

2026-08-16

Rank Moved

Rank dropped 13 spots (#613 → #626)

2026-08-10

Rank Moved

Rank dropped 10 spots (#600 → #610)

2026-08-08

Newly Listed

First tracked at rank #600

GitHub → npm: @qase/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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