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/praveenjuge/teakWrote 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/praveenjuge/teak/playwright)<a href="https://agentmods.dev/mcp/praveenjuge/teak/playwright"><img src="https://agentmods.dev/badge/mcp/praveenjuge/teak/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/praveenjuge/teak/playwright"><img src="https://agentmods.dev/badge/mcp/praveenjuge/teak/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 11d 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": {
"command": "bunx",
"args": [
"@playwright/[email protected]",
"--headless"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 11d ago First seen · 9 lines scan A d536bdc8d0c3
playwright is an MCP server published in the GitHub repository praveenjuge/teak (24 stars, last pushed today), 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-09-30.
Other mcp servers, from other repositories
playwright-electron
MCP server "playwright-electron", hosted remotely at 127.0.0.1, as configured in 777genius/agent-teams-ai.
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.
browser-control
MCP server "browser-control" as configured in Jamailar/Beav. Runs ./mcp-server.mjs with node.
uivision-mcp
MCP server for browser and desktop automation: OCR, image recognition, real mouse and keyboard input. Runs locally from the uivision-mcp-bridge npm package. Needs 1 environment variable to run.
electromcp
Drive any Electron app from your AI. MCP server with 93 tools, 4 recipe packages (Slack/Discord/Notion/Linear), security primitives, and a CLI mirror. The testing surface area Tauri structurally cannot match. Runs locally from the electromcp npm package.
browser-mcp
MCP server "browser-mcp" as configured in EndymionLee/PilotBrowseMCP. Runs BrowserPlugin\server\dist\index.js with node.