$ loading_
Use MCP tools to inspect web pages, capture screenshots, and list screens.
The materials indicate this MCP tool mainly provides local web development helper functions (screenshots and screen listing), with no declared secrets or remote endpoints, and no clear high-risk red flags. Caution is still warranted because it can execute locally and access screen contents, while community adoption is low and maintenance status is unknown.
The materials explicitly state that no keys or environment variables are required. No API keys, OAuth tokens, or other sensitive credentials are requested, so credential leakage and abuse exposure appears low.
It declares no remote endpoint hosts, and the description only mentions screenshots and listing screens. There is no evidence in the provided materials of sending user data to external services, so network egress risk appears low based on available facts.
The objective checks indicate that this tool executes code. This is a common MCP capability, but it means the tool can run local logic and use system capabilities related to screenshots and screen enumeration, so its runtime environment and permissions should be constrained.
Based on the functional description, the tool can at least access screen listings and capture screen contents. This does not by itself imply broad filesystem read/write access, but it may collect sensitive information visible on screen. The materials do not describe broader data access, so this is rated as caution rather than high risk.
Positive factors include that it is open source under the MIT License, making the code in principle auditable. However, it comes from a third-party registry, the GitHub repository shows 0 stars, and maintenance status is unknown, so confidence and evidence of ongoing maintenance are limited, leaving some supply-chain and dependency review risk.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "webdev-mcp" yet — see the docs or source repo.
Use webdev-mcp to open https://example.com, capture a full-page screenshot of the homepage, and return the screenshot result with notes on key visible sections.
A page screenshot plus a brief description of the main homepage sections.
Use webdev-mcp to analyze the currently accessible screens or page views in this web app, and list each view with its purpose.
A list of accessible pages or screens, with a short explanation of each one.
Use webdev-mcp to capture a screenshot of the target page and list its main interface regions to help me verify recent UI changes.
An updated screenshot and a structured list of interface regions for verification.
Capture app or webpage screenshots and analyze them with a local vision model.
Automate browser tasks, capture console logs, and take screenshots for web workflows.
Capture screen frames on demand for multimodal Q&A and interface understanding.
Control a browser with AI for automation, extraction, interception, and screenshots.
Let AI capture Windows screenshots for troubleshooting, review, and visual context.
Capture, compare, audit, and map web pages for review workflows.