Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/sa2web/sa2web-mcpInstalling this writes the configuration, not the program: `sa2-mcp` has to be on your PATH already, or the server will not start.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/sa2web/sa2web-mcp/sa2-remote-browser)<a href="https://agentmods.dev/mcp/sa2web/sa2web-mcp/sa2-remote-browser"><img src="https://agentmods.dev/badge/mcp/sa2web/sa2web-mcp/sa2-remote-browser/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/sa2web/sa2web-mcp/sa2-remote-browser"><img src="https://agentmods.dev/badge/mcp/sa2web/sa2web-mcp/sa2-remote-browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sa2-remote-browser scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"sa2-remote-browser": {
"command": "sa2-mcp",
"args": [],
"env": {
"SA2_LOGIN_URL": "https://www.test7878.com/agent/login?clientId=954d7b53e19344cebfc92a86b3dacb33&clientSecret=b381b99ad85249799add250cf829468fcba03ce0ece648efa803964b94eff63f",
"SA2_LOGIN_REDIRECT_PATH": "/app/login",
"SA2_LOGIN_REDIRECT_WAIT_MS": "8000",
"SA2_RBI_FRAME_SELECTOR": "#rbi-frame",
"SA2_RBI_FRAME_WAIT_MS": "5000",
"SA2_RBI_FRAME_CONTENT_WAIT_MS": "15000",
"SA2_AUTO_LOGIN_BEFORE_NAVIGATE": "true",
"SA2_LOGIN_SETTLE_MS": "1500",
"SA2_HEADLESS": "false",
"SA2_BROWSER": "chromium",
"SA2_VIEWPORT_WIDTH": "1440",
"SA2_VIEWPORT_HEIGHT": "1000",
"SA2_NAVIGATION_TIMEOUT_MS": "45000",
"SA2_ACTION_TIMEOUT_MS": "15000",
"SA2_IGNORE_HTTPS_ERRORS": "true"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 23 lines scan A 3838487cc537
sa2-remote-browser is an MCP server published in the GitHub repository sa2web/sa2web-mcp (14 stars, last pushed 2mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 2 environment variables to run.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
fetch
Lets the agent fetch a URL and read its content as markdown. Runs locally from the mcp-server-fetch Python package.
chrome-tabs
MCP server "chrome-tabs" as configured in pokutuna/mcp-chrome-tabs. Runs src/cli.ts with node.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.