Vibescan Mcp Server

io.github.AguantarPublished by GitHub account Aguantarv0.1.0Updated Oct 24, 2026

MCP server for VibeScan — scan projects for leaked secrets and security issues

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

An MCP server for VibeScan that lets an assistant scan projects for leaked secrets and security issues.

What you can do
Scan a project for secrets, dangerous code patterns and Git hygiene issues across categories such as env files, cloud credentials, CI/CD and SSH keys. List all 17 detection rules. All scanning runs locally, so code stays on the machine.
When to use it
Use it when you want a quick local check in Claude Code for leaked secrets, dangerous code patterns, or poor Git ignore hygiene in a project, for example before committing or sharing code.
Requirements
A local Python install of the vibescan-mcp-server package (pip install), configured in .mcp.json to start over stdio. No account or API key is needed.
Before you install
Scan output can reveal information about secrets and credentials, so handle results carefully and avoid pasting them into external services. The tool only detects issues; it does not fix or delete files.

Installation

In SourceWeft

  1. Open Vibescan Mcp Server 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

vibescan-mcp-server

mcp-name: io.github.Aguantar/vibescan-mcp-server

MCP server for VibeScan — scan projects for leaked secrets and security issues directly from Claude Code.

Features

  • vibescan_scan — Scan a project for secrets, dangerous patterns, and git hygiene issues
  • vibescan_rules — List all 17 detection rules

What VibeScan detects

  • 14 secret categories: env files, config hardcodes, cloud credentials, Docker/infra, CI/CD pipelines, IDE settings, SSH keys, hardcoded patterns, frontend env vars, data files, doc secrets, mobile files, system configs, editor remnants
  • Dangerous code patterns: eval(), exec(), shell injection, SQL injection, pickle, innerHTML
  • Git hygiene: missing .gitignore, unignored .env/.pem/.key files

All scanning runs locally — your code never leaves your machine.

Installation

bash
pip install vibescan-mcp-server

Usage with Claude Code

Add to your .mcp.json:

json
{  "mcpServers": {    "vibescan": {      "command": "vibescan-mcp-server"    }  }}

Then ask Claude: "scan this project for security issues" or "check for leaked secrets".

License

MIT

Source: README.md at commit 5dd1851

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% 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
  • License10 pts