lizard-studio (lizard-build/lizard-studio) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 29 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
74/100

lizard-studio

Claude Code Chrome extension — runs the real Claude Code CLI locally, with the chat in your browser's side panel. Claude gets browser tools over MCP (DOM, console, network, screenshot, click, type) plus an on-page design toolkit. Local only, no telemetry.

→ lizard-build/lizard-studio· listed on github_repo_search

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

lizard-build

Source: github_repo_search

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 →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 1 credential: RK_BRIDGE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configRK_BRIDGE_PORT
configRK_BRIDGE_SESSION
🔐 secretRK_BRIDGE_TOKEN
configRK_EXT_ID
configSHELL
// 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

29/29 tools missing one or more hints — browser_tabs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); browser_tab_activate (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); browser_tab_open (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +26 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 test coverage

12/29 tools referenced in tests (41%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

7 calls in production code run through a shell (src/host/claude-host.mjs:511, src/host/claude-host.mjs:552, src/host/claude-host.mjs:569)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

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 5 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/lizard-build/lizard-studio?variant=verified)](https://m8ven.ai/mcp/lizard-build/lizard-studio)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: d05ca270680f80dce3354217fe6f931df9dc5569
code hash: 3eb0fe0a9097770558feaaeea7299072020a389e8e35c8c290f3d55f9331cd74
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