# @qase/mcp-server

Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 2.2.2
- **Author:** io.qase
- **License:** Unknown
- **npm:** @qase/mcp-server
- **Endpoints:** streamable-http https://mcp.qase.io/mcp
- **Source:** https://github.com/qase-tms/qase-mcp-server
- **Endpoint health:** reachable (last checked 2026-08-26T11:47:33.606Z, 1 sample) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 18 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-10T15:15:02.567Z
- **Version scanned:** 2.0.1
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `qase_api`
- `qase_attachment_upload`
- `qase_attachment_delete`
- `qase_case_bulk_create`
- `qase_case_upsert`
- `qase_case_delete`
- `qase_ci_report`
- `qase_defect_upsert`
- `qase_defect_delete`
- `qase_discover_tools`
- `qase_environment_upsert`
- `qase_environment_delete`
- `qase_external_issue_link`
- `qase_get`
- `qql_search`
- `qql_help`
- `triage_failed_run`
- `project`
- `run_id`
- `release_readiness`
- `milestone`
- `regression_workflow`
- `title`
- `source`
- `onboard_project`
- `ci_integration`
- `results_json`
- `qase_milestone_upsert`
- `qase_milestone_delete`
- `qase_plan_upsert`
- `qase_plan_delete`
- `qase_project_context`
- `qase_regression_run`
- `qase_result_record`
- `qase_result_delete`
- `qase_run_upsert`
- `qase_run_complete`
- `qase_run_delete`
- `qase_shared_step_upsert`
- `qase_shared_step_delete`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@qase/mcp-server\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs locally and hosted.
- Floor 46, ceiling 70 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40qase%2Fmcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40qase%2Fmcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40qase%2Fmcp-server
- HTML page: https://forgeregistry.com/registry/%40qase%2Fmcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.