io.github.avivgerz-hue/ghost-qa
ghost-qa
Is the ghost-qa MCP server down? It gave no valid answer in the probe of 2026-11-11: crashed on start. One failed probe is not an outage.
Autonomous headless browser QA & self-healing verification loop for AI coding agents.
crashed on start no valid answer since 2026-11-11 · probed 2026-11-15 · unchanged since 2026-11-11
MCP error -32000: Connection closed npx -y ghost-qa init npx -y ghost-qa mcp No npm? Every command also works straight from GitHub, e.g. npx -y github:avi
- Run it
- npx -y ghost-qa@2.1.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/avivgerz-hue/ghost-qa
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.avclabs/enhance-mcp · alive
- io.github.avclabs/media-mcp · alive
- io.github.avelsys/delphi-codecoverage · alive
- io.github.avisre/stockportfolio-mcp · needs network
- unslop — 7-Pillar Design Craft Engine io.github.avivgerz-hue/unslop · needs args
- vibe-shield — security scanner for AI-generated code io.github.avivgerz-hue/vibe-shield · alive
- io.github.avivkeller/umd-mcp · alive
- GitPeak io.github.awalhadi/gitpeak · alive
Servers that mention ghost.
- MyGhosts app.myghosts/myghosts · needs auth
- Gus Dantas · retail media measurement com.ghostavo/retail-media-measurement · alive
- GhostViral com.ghostviralai/ghostviral · needs auth
- SCRIPTMASTERLABS — GhostKey MCP com.scriptmasterlabs/ghostkey · alive
- ServGhost com.servghost/servghost · not found
- com.trycloudflare.electron-quality-edge-chapter/ghost · no DNS
- dev.workers.ghost-agent-os.ghost-identity/ghost-x402-market-intel-vet-schema · alive
- GhostBlock io.github.Evozim/ghostblock · not found
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-11. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.