Argus runs on your own machine — the client starts it, so there is no endpoint to ping. 263 installs a week from npm. Last commit 3 Aug 2026.
Automated web QA via Chrome DevTools MCP — a11y, security, visual, env diff, CI; Aegis redaction.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const found = execFileSync(cmd, [name], {
const filePath = path.join(resolved, name);
for (const [k, v] of Object.entries(process.env)) {
<p>This page calls <code>document.write()</code> and <code>document.writeln()</code> to trigger D6.2 detection.</p>
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add argus -e 'TARGET_DEV_URL=<TARGET_DEV_URL>' -- npx -y argusqa-os{
"mcpServers": {
"argus": {
"command": "npx",
"args": [
"-y",
"argusqa-os"
],
"env": {
"TARGET_DEV_URL": "<TARGET_DEV_URL>"
}
}
}
}[mcp_servers.argus]
command = "npx"
args = ["-y", "argusqa-os"]
env = { TARGET_DEV_URL = "<TARGET_DEV_URL>" }{
"mcpServers": {
"argus": {
"command": "npx",
"args": [
"-y",
"argusqa-os"
],
"env": {
"TARGET_DEV_URL": "<TARGET_DEV_URL>"
}
}
}
}{
"servers": {
"argus": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"argusqa-os"
],
"env": {
"TARGET_DEV_URL": "<TARGET_DEV_URL>"
}
}
}
}Put your own value in place of
<TARGET_DEV_URL> (Base URL of the dev environment to audit (e.g. http://localhost:3000)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
TARGET_STAGING_URL (Base URL of the staging environment — used by argus_compare for dev vs staging diff. Omit to use CSS analysis mode), SLACK_BOT_TOKEN (Slack bot token (xoxb-...) for posting reports. Omit to generate a local report.html instead), FIGMA_API_TOKEN (Figma personal access token — enables argus_design_audit to fetch design specs from a Figma frame and compare them against the live DOM (13 fidelity finding types). Omit to skip design fidelity audits), ARGUS_REDACT_SENSITIVE (Aegis confidentiality egress boundary. Default ON: every tool response is redacted so secrets, PII, and exploit detail never cross into the calling agent's context (the local on-disk report keeps full fidelity). Set to 0 for byte-identical pre-Aegis output).
Alternatives to Argus
same job, measured the same wayMCP server for loading authenticated web pages using Chrome DevTools Protocol
MCP server for Chrome DevTools
MCP server for Chrome DevTools
MCP server for Chrome DevTools
MCP server for Chrome DevTools
AI-powered browser automation MCP — 6 tools for web interaction, extraction, and validation.
Browser automation MCP server with 84 tools. Pure CDP, DOM diffing, vision hybrid.
Browser automation MCP server with 84 tools. Pure CDP, DOM diffing, vision hybrid.
Argus — questions
Answers built from our own checks of this server.