Let a local AI agent capture a web page with the Page Scanner Chrome extension.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
installprivilegedSets up Page Scanner's helper, which Chrome starts to connect the extension to thisSets up Page Scanner's helper, which Chrome starts to connect the extension to this
No input schema was published for this tool.
pairThe older way to connect, for a machine where the install tool cannot set up theThe older way to connect, for a machine where the install tool cannot set up the
No input schema was published for this tool.
list_browsersThe Chrome profiles that have Page Scanner paired and connected right now. Each is aThe Chrome profiles that have Page Scanner paired and connected right now. Each is a
No input schema was published for this tool.
list_tabsThe windows and open tabs of one browser, so you can pick what to scan. Tabs carry theThe windows and open tabs of one browser, so you can pick what to scan. Tabs carry the
No input schema was published for this tool.
scan_pageCaptures a whole web page and writes it to disk. Name a tabId from list_tabs toCaptures a whole web page and writes it to disk. Name a tabId from list_tabs to
No input schema was published for this tool.
extract_designReads a page's design as it is drawn: the colors, type, spacing,Reads a page's design as it is drawn: the colors, type, spacing,
No input schema was published for this tool.
diff_capturesCompares two captures of the same page that scan_page wrote, with no browser needed.Compares two captures of the same page that scan_page wrote, with no browser needed.
No input schema was published for this tool.
7 of 7 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Let a local AI agent capture a web page with the Page Scanner Chrome extension.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+43 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.