Isolated browsers with a persistent identity for AI agents, on your own Windows machine.
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.
lease_profileReserve a free profile.Reserve a free profile.
No input schema was published for this tool.
open_pageNavigate to a public http or https address, and get the full page map back.Navigate to a public http or https address, and get the full page map back.
No input schema was published for this tool.
read_inboxThe profile's confirmation codes, by mail or by text.The profile's confirmation codes, by mail or by text.
No input schema was published for this tool.
3 of 3 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.
Isolated browsers with a persistent identity for AI agents, on your own Windows machine.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.