DOM Inspector Plus MCP Server
Gives Claude the ability to inspect and extract UI components from any webpage through a Chrome extension, enabling element discovery, style extraction, and design token analysis.
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
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
Sreelal727
Source: Glama
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
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.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get_inspector_statusCheck if the DOM Inspector Plus Chrome extension is connected and get current page info
start_inspectorActivate the DOM Inspector on the current page. The user can then hover and click elements to extract them.
stop_inspectorDeactivate the DOM Inspector overlay on the current page.
extract_elementExtract a specific element from the current page by CSS selector. Returns the full component tree with styles, layout, Tailwind classes, and accessibility info.
get_extractionGet the latest element extraction from the DOM Inspector. Call this after the user clicks an element in inspection mode.
extract_design_tokensScan the current page and extract its design system: colors, typography, spacing scale, border radii, and shadows. Useful for understanding a site's visual language before recreating components.
get_page_structureGet a high-level overview of the current page's DOM structure — main landmarks, sections, and key components. Useful for understanding what's on the page before extracting specific elements.
capture_interaction_stateCapture how an element changes on hover, focus, or active state. Returns a diff showing what CSS properties change.
find_elementsFind elements on the page matching a CSS selector or semantic description. Returns a list of matching elements with their tag, classes, text content, and bounding box.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
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
9/9 tools missing one or more hints — get_inspector_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); start_inspector (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); stop_inspector (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 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
5/9 tool handlers declare input schemas (56%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
6/9 tool handlers wrap calls in try/catch (67%)
Wrap each tool handler body in try/catch and return a structured error response.
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.12.1 (high), @modelcontextprotocol/sdk@1.12.1 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
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.
[](https://m8ven.ai/mcp/sreelal727/dom-inspector-plus-mcp)?variant=verified from the URL.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