Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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/dingdawg/dingdawg-agent-1/playwright)<a href="https://agentmods.dev/mcp/dingdawg/dingdawg-agent-1/playwright"><img src="https://agentmods.dev/badge/mcp/dingdawg/dingdawg-agent-1/playwright.svg" alt="Measured on agentmods" 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 5d 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": "/home/joe-rangel/.npm-global/bin/playwright-mcp",
"args": []
}
}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.
- 5d ago First seen · 6 lines scan A f4560d074809
playwright is an MCP server published in the GitHub repository dingdawg/dingdawg-agent-1 (1 stars, last pushed 1mo 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-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.
playwright-browser
MCP server "playwright-browser" as configured in CSOAI-ORG/playwright-browser. Runs locally from the @meok-ai-labs/playwright-browser npm package.
dingdawg-governance
Governance receipts for AI agents — universal, MCP-native, fail-closed governance layer compliant with EU AI Act Art. 12, Colorado AI Act (SB 24-205), and NIST AI RMF. LNN interpretability, IPFS audit proofs, and rollback for any agent in any framework. Runs locally from the dingdawg-governance npm package. Needs 1…
gate
Deterministic runtime enforcement of step order for AI agents: ALLOW/DENY before a step runs. Remote server at mcp.agenticrail.nz.
dingdawg-compliance
EU AI Act + Colorado AI Act compliance scoring. 87/100 in 60 seconds. Free local scan. Runs locally from the dingdawg-compliance npm package. Needs 1 environment variable to run.
dingdawg-governance
Universal governance layer for AI agents. MCP-native, fail-closed, audit proofs and rollback. Runs locally from the dingdawg-governance npm package. Needs 1 environment variable to run.