-
Notifications
You must be signed in to change notification settings - Fork 22
[Target] Add Puppeteer MCP to the Safety Index #250
Copy link
Copy link
Open
Labels
area:integrationReal-server coverage and integration workflowsReal-server coverage and integration workflowsgood first issueGood for newcomersGood for newcomersmcp-serverMCP server compatibility contextMCP server compatibility contexttarget-registrySafety Index target registry contributionsSafety Index target registry contributions
Description
Metadata
Metadata
Assignees
Labels
area:integrationReal-server coverage and integration workflowsReal-server coverage and integration workflowsgood first issueGood for newcomersGood for newcomersmcp-serverMCP server compatibility contextMCP server compatibility contexttarget-registrySafety Index target registry contributionsSafety Index target registry contributions
Task
Run MCP Observatory against Puppeteer MCP (
@anthropic/mcp-server-puppeteer) and add a Safety Index target.Why this matters
Puppeteer MCP enables agents to control headless Chrome — navigate pages, click elements, take screenshots. The security surface includes arbitrary browser automation, potential SSRF via page navigation, and access to rendered DOM content.
Steps
npx @kryptosai/mcp-observatory test npx -y @anthropic/mcp-server-puppeteernpx @kryptosai/mcp-observatory report --run <artifact.json> --format markdowndocs/safety-index/artifacts/puppeteer-mcp-server.{json,md}docs/safety-index/targets.jsondocs/mcp-server-safety-index.mdnpm run safety-indexandnpm testSafe mode
The tool listing works without a running browser instance. The scan runs in metadata-only safe mode by default.
Reference
See PR #209 (UI5 MCP) for the expected output format. 15-20 minutes.