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/bartstc/vite-ts-react-templateWrote 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/bartstc/vite-ts-react-template/playwright)<a href="https://agentmods.dev/mcp/bartstc/vite-ts-react-template/playwright"><img src="https://agentmods.dev/badge/mcp/bartstc/vite-ts-react-template/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/bartstc/vite-ts-react-template/playwright"><img src="https://agentmods.dev/badge/mcp/bartstc/vite-ts-react-template/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": {
"type": "stdio",
"command": "pnpm",
"args": [
"dlx",
"@playwright/[email protected]",
"--browser=chromium"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 5. 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 · 11 lines scan A de2d5ca1cc62
playwright is an MCP server published in the GitHub repository bartstc/vite-ts-react-template (122 stars, last pushed 8d 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
stdlib
Standard library for Webiny — platform-agnostic, Node.js, and browser utilities. Runs locally from the @webiny/stdlib npm package.
codegraph
MCP server "codegraph" as configured in JNTMTMTM/eIsland. Launched with codegraph serve --mcp --path C:\Users\Administrator\Desktop\pyisland_project\eIs.
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.
storybook-mcp
MCP server "storybook-mcp", hosted remotely at localhost, as configured in yannbf/mealdrop.
nx-mcp
Nx's MCP server: lets the agent read the Nx project graph, look up generators and run tasks in an Nx monorepo. Runs locally from the nx npm package.
flow
Build, validate, simulate, and deploy walkerOS event pipelines. Runs locally from the @walkeros/mcp npm package. Needs 3 environment variables to run.