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/PremierStudio/BrowserEngineWrote 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/premierstudio/browserengine/browser-engine)<a href="https://agentmods.dev/mcp/premierstudio/browserengine/browser-engine"><img src="https://agentmods.dev/badge/mcp/premierstudio/browserengine/browser-engine/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/premierstudio/browserengine/browser-engine"><img src="https://agentmods.dev/badge/mcp/premierstudio/browserengine/browser-engine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
browser-engine 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 yesterday.
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
{ "browser-engine": { "command": "npx", "args": [ "-y", "@premierstudio/browser-engine" ] } }
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.
- yesterday First seen · 9 lines scan A 9b85129dd8f6
browser-engine is an MCP server published in the GitHub repository PremierStudio/BrowserEngine (0 stars, last pushed yesterday), 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-09-11.
Other mcp servers, from other repositories
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
playwright-original
Context-efficient Playwright tools for MCP. Runs locally from the @tontoko/fast-playwright-mcp npm package.
expect
Let agents test your code in a real browser. Runs locally from the expect-cli npm package.
klyk
OS-level macOS app testing via MCP — native apps, Electron apps, browsers, web pages, system dialogs. Runs locally from the klyk Python package.
cypress-mcp
MCP server "cypress-mcp" as configured in miroslavmyrha/cypress-mcp. Runs locally from the @miroslavmyrha/cypress-mcp npm package.
locatorlabs-mcp
MCP server for intelligent Playwright locator generation - Get locators, analyze pages, generate POMs, and run tests. Runs locally from the locatorlabs-mcp npm package.