@page-scanner/mcp

MCPcommunity
v0.4.2Byungdon YoonApache-2.0Updated 1d agonpmGitHub

Let a local AI agent capture a web page with the Page Scanner Chrome extension.

Works in
ClaudeCursorCopilotGemini

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
266Downloads/wk
1d agoLast update
Package
AuthorByungdon Yoon
LicenseApache-2.0
Version0.4.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface7 tools · 1 privileged
Security scan✓ Cleanv0.4.2 · todayHow well does this scan work?
EvalsNone
IndexedSep 25, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

7 tools · 1 privileged
Statically extracted from the published packagev0.4.2 · 5h ago

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 this

Sets 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 the

The 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 a

The 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 the

The 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 to

Captures 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.

About

Let a local AI agent capture a web page with the Page Scanner Chrome extension.

Keywords
mcpmodelcontextprotocolchromechrome-extensionscreenshotpdfpage-scanner
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-25 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

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)

Declared but not resolved

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.

Topics

Related in images, video & audio