io.github.VibeCheckAIOfficial/vibecheck-mcp
io.github.VibeCheckAIOfficial/vibecheck-mcp
Is the io.github.VibeCheckAIOfficial/vibecheck-mcp MCP server down? Yes. It has given no valid answer since 2026-10-18: install failed.
AI Code Firewall — MCP Server for hallucination prevention in AI development
install failed down since 2026-10-18 · probed 2026-11-15 · unchanged since 2026-11-08
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-15T08_35_29_770Z-debug-0.log
- Run it
- npx -y @vibecheckdev/vibecheck-mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/vibecheckai/vibecheck
- Registry
- active, updated 2026-02-24 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Engine DJ Library Assistant (unofficial) io.github.Venut-Technologies/engine-dj-mcp · alive
- Serato DJ library io.github.Venut-Technologies/serato-dj-mcp · alive
- io.github.Verifux/snapshot · alive
- ATS Engine io.github.VeriWorkly/ats-engine · alive
- io.github.VibeCodingInc/vibe-mcp · crashed on start
- io.github.Vigile-ai/vigile-mcp · alive
- io.github.VikrantSingh01/adaptive-cards-mcp · alive
- droppage io.github.Vilancer/droppage · alive
Servers that mention vibecheck or hallucination or development.
- SomaCheck Vibecheck io.github.Sensie-agents/vibecheck · needs auth
- agency.lona/trading · needs auth
- Projectory ae.projectory/mcp · alive
- BeatBandit MCP ai.beatbandit/beatbandit · needs auth
- OpenMandate ai.openmandate/mcp · alive
- Synthetic Data — Random User ai.saifs/synthetic-data-random-user · needs auth
- ai.smithery/devbrother2024-typescript-mcp-server-boilerplate · not found
- ai.smithery/exa-labs-exa-code-mcp · 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
- No valid answer since 2026-10-18, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.