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/susomejias/rembricWrote 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/susomejias/rembric/playwright)<a href="https://agentmods.dev/mcp/susomejias/rembric/playwright"><img src="https://agentmods.dev/badge/mcp/susomejias/rembric/playwright/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/susomejias/rembric/playwright"><img src="https://agentmods.dev/badge/mcp/susomejias/rembric/playwright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
playwright 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 9d 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
{
"playwright": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@playwright/[email protected]",
"--headless",
"--isolated",
"--browser",
"chromium"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 9d ago First seen · 14 lines scan A 2c4423763e97
playwright is an MCP server published in the GitHub repository susomejias/rembric (12 stars, last pushed 6d ago), licensed MIT. 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-30.
Other mcp servers, from other repositories
web-fetch
MCP server for fetching web content using Playwright browser. Runs locally from the fetcher-mcp npm package.
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.
weapp-agent-mcp
Agent-first MCP server for WeChat Mini Program debugging & automation via WeChat DevTools. Runs locally from the @chaixueyuan/weapp-agent-mcp npm package. Needs 15 environment variables to run.
lan-direct
Browser MCP: the app under test egresses via the real ISP while the agent stays on the VPN. Runs locally from the lan-direct npm package.
agent-browser-mcp
MCP server "agent-browser-mcp" as configured in linsipeng/hermes-chrome-bridge. Runs locally from the agent-browser-mcp Python package.
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.