Qase (qase) MCP Server
@qase/mcp-server
npm
v1.1.8
Source verified
Published by qase-tms — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −6.7 | Possible combosquat of mcp ×4 MTC-SUP-006 | supply-chain |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind the deduction.
Findings 4
medium Possible combosquat of mcpMTC-SUP-006
"@qase/mcp-server" is "mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "mcp". Install packages only from their documented, official name.
Location: package @qase/mcp-server
medium Possible combosquat of @playwright/mcpMTC-SUP-006
"@qase/mcp-server" is "@playwright/mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "@playwright/mcp". Install packages only from their documented, official name.
Location: package @qase/mcp-server
medium Possible combosquat of @stripe/mcpMTC-SUP-006
"@qase/mcp-server" is "@stripe/mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "@stripe/mcp". Install packages only from their documented, official name.
Location: package @qase/mcp-server
medium Possible combosquat of @browsermcp/mcpMTC-SUP-006
"@qase/mcp-server" is "@browsermcp/mcp" with a decorative suffix — a common combosquat pattern.
Fix: Confirm you meant "@browsermcp/mcp". Install packages only from their documented, official name.
Location: package @qase/mcp-server
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.1.8 latest |
A 93/100 | 4 | 1.5.0 | 2026-07-22 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @qase/mcp-server --onlineOther implementations of Qase 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Security & Testing
Security scan results for the 1claw MCP server.
Security scan results for the 1password MCP server.
Security scan results for the 1password MCP server.
Security scan results for the A11y MCP server.
Security scan results for the A11y Tools MCP server.
Security scan results for the Abuseipdb MCP server.