Cli Site
mcpcli site — what's actually broken?
Runtime truth from a real check — not curl, not header grades. CLI + REST only (no MCP tool).
Related: Terminal CLI reference · Full command list · API key setup
npm install -g zephex && mcpcli setupmcpcli site localhost:3000mcpcli site zephex.devmcpcli site zephex.dev --why "what api errors"mcpcli site historyPaste a URL and get what broke, where, and what to fix first — in plain English plus developer detail. No browser download for localhost.
localhost — fast HTTP check on your machine
mcpcli site localhost:3000 hits your dev server over HTTP. Nothing to install — no download, no browser setup. Cloud agents cannot reach your loopback; this command can. You get page title, tech stack hints, load time, and API health probes with --deep.
Public URLs — full scan on Zephex cloud (AWS)
mcpcli site https://zephex.dev POSTs to /api/site/scan with your API key. The scan runs on Zephex infrastructure (real browser, JS console, screenshots). Run mcpcli setup first.
Core commands
mcpcli site <url>— full scan (alias:pulse,broken)mcpcli <url>— bare URL shorthand (e.g.mcpcli zephex.dev)mcpcli site last— re-print last sessionmcpcli site history— last 10 cloud scans (API key)mcpcli ask "is zephex.dev working"— natural language router
Useful flags
mcpcli site localhost:3000 --json --strict # CI: exit 1 if criticalmcpcli site localhost:3000 --deep --apis # API surface probemcpcli site zephex.dev --screenshot # PNG (cloud scans only)mcpcli site zephex.dev --why "why is checkout slow" # free 30m follow-upNot an MCP tool
Site Pulse (mcpcli site) is a fast runtime probe — page errors, API health, vitals. For security headers and TLS grades use /check-url or mcpcli check url https://… (same audit_headers MCP tool).