MCP servers · aguantar

VibeScan MCP Server: scan projects for leaked secrets and security issues

An MCP server that scans projects for leaked secrets, dangerous code patterns and git hygiene issues, used from Claude Code.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

This MCP server connects VibeScan to Claude Code. It exposes two tools: vibescan_scan, which scans a project for secrets, dangerous code patterns and git hygiene problems, and vibescan_rules, which lists the 17 detection rules. The secret checks cover 14 categories, including env files, cloud credentials, Docker and infrastructure files, CI/CD pipelines, SSH keys and mobile files. Code checks flag patterns such as eval(), exec(), shell injection, SQL injection, pickle and innerHTML. Git checks flag a missing .gitignore and unignored .env, .pem or .key files.

It suits a developer who wants to check a project for leaked credentials or common security issues from inside Claude Code. The README gives the example request "check for leaked secrets" as a way to start a scan in plain language.

The server is added to a project's .mcp.json file, after which Claude can run the scan on request. According to the README, all scanning runs locally, so the code is not sent off the machine. The project is released under the MIT license.

Limitations and requirements

Set up for use with Claude Code, with the connection configured in a .mcp.json file. No other requirements are stated.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.Aguantar/vibescan-mcp-server

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

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026