updated 2026-11-10 04:07 UTC

Qase Test Management

Repository

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.2 / 10
Provenance Attested
Signed commits 39%
Last push 6d ago
Advisories None known
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.9/100 (Grade A), ranked #150 of 1374 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.2/10; 39% of recent commits are signed; no published advisory affects its latest release (@qase/mcp-server); last pushed 2026-11-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Qase Test Management 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

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

  1. Source Partly signed

    github.com/qase-tms/qase-mcp-server, MIT, last pushed 2026-11-04. 39% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.2/10 (scanned Nov 6, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 6
    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 6
    SAST 6
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 7

  3. Published packages Linked and attested

    • npm @qase/mcp-server Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: @qase/mcp-server 3.0.6. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-05 OSSF Scorecard: 7.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

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

  1. #66 Roslyn CodeLens 82.0 +0.1
  2. #67 ClickHouse 81.9 ±0
  3. #68 Qase Test Management 81.9 this agent
  4. #69 Filesystem MCP 81.9 ±0
  5. #70 Intervals Icu MCP 81.9 ±0

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

Where the 81.9 comes from

HVTrust dimensions vs the MCP Servers average

81.9 / 100 · 100.0% confidence

Qase Test Management MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
18.4 / 25
7.6 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.6 / 17
2.3 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
16.8 / 20
4.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.1 / 20
1.5 above avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-06
Rank Moved
Rank rose 17 spots (#151 → #134)
2026-11-01
Rank Moved
Rank rose 15 spots (#162 → #147)
2026-10-30
Rank Moved
Rank rose 14 spots (#171 → #157)
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
View MCP Servers Report missing data
55.0
Activity sub-score · out of 100
#68
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 6 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
37
Forks
11
Last Push
2026-11-04
6 days ago
Commits (4 wk)
19
Downloads (7d)
10,097
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼5
was #145

Analysis

Activity Inputs

55.0 / 100
StarsRepository reach
9.5 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
16.2 / 25
CommunityFork signal
5.0 / 20

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.2/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 6 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
Rank 19HVTrust 3Grade 3Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-06
Rank Moved
Rank rose 17 spots (#151 → #134)
2026-11-01
Rank Moved
Rank rose 15 spots (#162 → #147)
2026-10-30
Rank Moved
Rank rose 14 spots (#171 → #157)
2026-10-29
Rank Moved
Rank dropped 17 spots (#154 → #171)
2026-10-15
Rank Moved
Rank rose 24 spots (#151 → #127)
2026-10-12
Rank Moved
Rank rose 11 spots (#159 → #148)
2026-10-02
Rank Moved
Rank dropped 11 spots (#126 → #137)
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)
GitHub → npm: @qase/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 81.9 Grade A
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.4 · Raw JSON