@qase/mcp-server
npm could not install it the way the runner installs: from the registry only, without install scripts. Run 2026-11-16.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @qase/mcp-server@3.1.0
Installing a package runs its code. Use a sandbox for anything you have not read.
What it said when it did not start
a dependency does not come from the npm registry: node_modules/npm/node_modules/@gar/promise-retry
Written by the package or by npm, not by this site.
Install facts
| License | not stated |
|---|---|
| Needs | not stated |
| Source | not stated |
| Install scripts | None declared by it or anything installed with it. |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 3.1.0 | 2026-11-16 | Did not install | 0 |
| 3.0.6 | 2026-11-12 | Did not install | 0 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40qase/mcp-server)
New version out? Ask for a fresh report.