D
Caution
46/100
7 days ago

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

qabyai

Source: modelscope

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical, 8 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
// known CVEs in dependencies1 critical8 high5 medium7 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalhappy-dom@17.4.4GHSA-37j7-fg3j-429f

Happy DOM: VM Context Escape can lead to Remote Code Execution

high@modelcontextprotocol/sdk@1.7.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.7.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highhappy-dom@17.4.4GHSA-6q6h-j7hj-3r64

Happy DOM ECMAScriptModuleCompiler: unsanitized export names are interpolated as executable code

highhappy-dom@17.4.4GHSA-w4gp-fjgq-3q4g

Happy DOM's fetch credentials include uses page-origin cookies instead of target-origin cookies

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

5/5 tools missing one or more hints — init-browser (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get-full-dom (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get-screenshot (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 2/5 tool handlers declare input schemas (40%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Production dependencies are patched

1 critical, 6 high severity in production deps — happy-dom@17.4.4 (critical), @modelcontextprotocol/sdk@1.7.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

4/24 production deps abandoned (no release in 2+ years): react-contenteditable@2023-02-28 (3.5y), tailwindcss-animate@2023-08-28 (3y), @skorotkiewicz/snowflake-id@2024-02-06 (2.5y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/qabyai-playwright-mcp-1elu85?variant=verified)](https://m8ven.ai/mcp/qabyai-playwright-mcp-1elu85)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 846281099d49ca5dff46dfe9f5c7c742b79db04d
code hash: 61605ff442c5d1e261e29d29c9b4ce31f21f5eaab66d5aeb3e3551587733865c
verified: 8/13/2026, 9:18:43 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client