io.github.ofershap/real-browser

MCPcommunity
v1.2.1io.github.ofershapUnknownUpdated 6mo agonpmGitHub

MCP server + Chrome extension for AI browser control with real sessions.

The missing piece in AI coding: your agent can now see your REAL browser. You ship a fix. Your agent says "done, please verify." You alt-tab to Chrome, navigate to the page, log in, click around, find the bug. Your agent just wrote the code. It could also verify it. It already has your browser open right there. It just can't see it. MCP server - runs on your machine, talks to your AI agent Chrome…

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 →
50GitHub stars
6Forks
6mo agoLast update
Package
Authorio.github.ofershap
LicenseUnknown
Version1.2.1
Sourcemcp-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 surface18 tools · 1 privileged
Security scan✓ Cleanv1.2.1 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

18 tools · 1 privileged
Statically extracted from the published packagev1.2.1 · 3mo 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.

browser_click_textNo description published

This tool published no description. Forge does not invent one.

browser_clickNo description published

This tool published no description. Forge does not invent one.

browser_consoleNo description published

This tool published no description. Forge does not invent one.

browser_handle_dialogNo description published

This tool published no description. Forge does not invent one.

browser_evaluateprivilegedNo description published

This tool published no description. Forge does not invent one.

browser_findNo description published

This tool published no description. Forge does not invent one.

browser_hoverNo description published

This tool published no description. Forge does not invent one.

browser_navigateNo description published

This tool published no description. Forge does not invent one.

browser_networkNo description published

This tool published no description. Forge does not invent one.

browser_press_keyNo description published

This tool published no description. Forge does not invent one.

browser_screenshotNo description published

This tool published no description. Forge does not invent one.

browser_scrollNo description published

This tool published no description. Forge does not invent one.

browser_selectNo description published

This tool published no description. Forge does not invent one.

browser_snapshotNo description published

This tool published no description. Forge does not invent one.

browser_tabsNo description published

This tool published no description. Forge does not invent one.

browser_textNo description published

This tool published no description. Forge does not invent one.

browser_typeNo description published

This tool published no description. Forge does not invent one.

browser_waitNo description published

This tool published no description. Forge does not invent one.

0 of 18 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

The missing piece in AI coding: your agent can now see your REAL browser. You ship a fix. Your agent says "done, please verify." You alt-tab to Chrome, navigate to the page, log in, click around, find the bug. Your agent just wrote the code. It could also verify it. It already has your browser open right there. It just can't see it. MCP server - runs on your machine, talks to your AI agent Chrome extension - sits in your browser, executes the commands…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in browser automation & scraping