Skip to main content
Glama
Aguantar

vibescan-mcp-server

by Aguantar

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
vibescan_scanA

Scan a project directory for leaked secrets and security issues.

Detects:

  • Leaked secrets: API keys, passwords, tokens in code/config/docs

  • Dangerous patterns: eval(), shell injection, SQL injection, pickle

  • Git hygiene: missing .gitignore, unignored sensitive files

  • 14 secret categories: env files, cloud credentials, Docker, CI/CD, SSH keys, etc.

Returns issues with severity, file location, description, and fix suggestion. All scanning runs locally — your code never leaves your machine.

Args: path: Project directory to scan (default: current directory) min_severity: Minimum severity to report — critical, high, medium, low, info (default: info)

vibescan_rulesA

List all available VibeScan detection rules.

Returns the full list of 17 detection rules with their IDs, names, and descriptions. Useful for understanding what VibeScan checks for.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one lists detection rules, the other performs scans. There is no overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent 'vibescan_' prefix with a verb_noun pattern ('rules' for list, 'scan' for execute), making it predictable.

Tool Count4/5

With only 2 tools, the set is slightly below the typical 3-15 range, but it is still reasonable for a focused security scanner. Each tool serves a distinct and necessary function.

Completeness4/5

The set covers the core workflow of learning about rules and running scans. A minor gap is the absence of a tool to view a single rule in detail, but the overall surface is adequate for the domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive