Vibecheck Mcp

io.github.VibeCheckAIOfficialPublished by GitHub account VibeCheckAIOfficialv1.0.0Updated Oct 24, 2026

AI Code Firewall — MCP Server for hallucination prevention in AI development

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server described as an AI code firewall for preventing hallucinations in AI-assisted development.

What you can do
The listing describes it as an AI code firewall aimed at hallucination prevention in AI development. No tools, instructions or README are provided, so the specific actions an assistant can take through it are not documented here. It runs as a local process over stdio rather than a remote endpoint.
When to use it
Consider it only if you want a local, desktop-only guardrail against hallucinated code during AI-assisted development and are willing to evaluate its behavior yourself, since no tool list or documentation is supplied.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package @vibecheckdev/vibecheck-mcp, so a Node.js runtime is needed. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The listing gives no tool list, README or instructions, so what it reads, changes or sends cannot be verified before installing. Treat it as unaudited third-party code running locally with your user permissions, and review the package yourself before use.

Installation

In SourceWeft

  1. Open Vibecheck Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.