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/tale-project/taleWrote 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/tale-project/tale/playwright)<a href="https://agentmods.dev/mcp/tale-project/tale/playwright"><img src="https://agentmods.dev/badge/mcp/tale-project/tale/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/tale-project/tale/playwright"><img src="https://agentmods.dev/badge/mcp/tale-project/tale/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 1mo 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": "npx",
"args": [
"@playwright/mcp@latest",
"--browser=chrome",
"--headless",
"--isolated",
"--viewport-size=1280x720",
"--output-dir=.playwright-mcp",
"--save-session",
"--caps=vision,pdf",
"--config=playwright-mcp.config.json"
]
}
}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.
- 1mo ago First seen · 16 lines scan A 25595de2951b
playwright is an MCP server published in the GitHub repository tale-project/tale (35 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-08-30.
Other mcp servers, from other repositories
web-fetcher
MCP server "web-fetcher" as configured in akanthed/SecureAI-Scan. Runs locally from the some-mcp-fetch-server npm package. Needs 1 environment variable to run.
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.
nexus-browser-mcp
A local browser-control MCP server built with Playwright and an accessibility tree. Playwright is software for controlling web browsers, while an accessibility tree describes page elements in a way automation tools can inspect.
skyvern
AI-powered browser automation — navigate, click, fill forms, and extract data from any website. Remote server at api.skyvern.com.
mcp-neo4j-knowledge-graph
Neo4j-based knowledge graph MCP server with temporal versioning and semantic search. Runs locally from the @henrychong-ai/mcp-neo4j-knowledge-graph npm package.
figjam-mcp
MCP server "figjam-mcp" as configured in ecestnrkl/figjam-mcp. Runs locally from the figjam-context-mcp npm package. Needs 4 environment variables to run.