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/mrkanitkar/playwright-pramanWrote 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/mrkanitkar/playwright-praman/playwright-test)<a href="https://agentmods.dev/mcp/mrkanitkar/playwright-praman/playwright-test"><img src="https://agentmods.dev/badge/mcp/mrkanitkar/playwright-praman/playwright-test.svg" alt="Measured on agentmods" height="20"></a>- Socket warn
Grade A, and why
playwright-test 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 today.
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-test": {
"type": "stdio",
"command": "npx",
"args": [
"playwright",
"run-test-mcp-server"
]
}
}What else mcp.json configures
This page is one entry in a file that holds 4. 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.
- today First seen · 10 lines scan A c634f79196b9
playwright-test is an MCP server published in the GitHub repository mrkanitkar/playwright-praman (11 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-08.
Other mcp servers, from other repositories
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
playwright
MCP server "playwright" as configured in evan043/claude-cli-advanced-starter-pack. Launched with cmd /c npx -y @anthropic/mcp-playwright.
sniff
Autonomous QA scanner: point it at your running app and it walks the real user flows in a headless browser and reports what's actually broken — broken pages/links, console & network errors, empty/placeholder data, broken forms, state-loss, bad loading/err. Runs locally from the sniff-qa npm package.
ai-web-tester
Autonomous browser testing engine & MCP toolset for AI coding agents. Runs locally from the ai-web-tester npm 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.
playwrightselectorguard-mcp
Playwright selector risk checks with healing suggestions and receipts. Remote server at playwrightselectorguard.clauxel.com.