NoVibeLeaks MCP server
Commit Oct 25, 2026Detects hardcoded secrets, API keys, and security anti-patterns within the AI agent development loop.
Also known as Procoder1234556/NoVibeLeaks
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 25, 2026
- License
- MIT
What is NoVibeLeaks MCP?
NoVibeLeaks detects hardcoded secrets, API keys, and security anti-patterns within the AI agent development loop.
Summary generated from the project's README
About NoVibeLeaks MCP server
Identifying hardcoded secrets and security anti-patterns during the AI agent development loop is the primary function of NoVibeLeaks. This Python-based MCP server operates via stdio to provide real-time security feedback to coding agents and IDEs. It helps developers catch sensitive data like API keys, tokens, and private keys before they are committed to a codebase.
Users interact with the server through five specific tools: check_secrets for finding hardcoded credentials, validate_api_key for optional masked provider checks, scan_vibe_bugs for identifying CORS or auth gaps, get_security_score for a numerical assessment, and list_available_rules to view the YAML rule catalog. The system uses a set of YAML rules to evaluate code quality and security posture.
Setting up the server is straightforward using uvx or by installing the package via PyPI. It is designed to integrate directly into an agent's workflow, allowing the LLM to proactively scan its own output for risky patterns, debug flags, and configuration errors.
What you can do with it
- 1Detecting hardcoded credentialsAsk the AI agent to scan the current file for any exposed API keys or private tokens.
- 2Evaluating overall code securityRequest a numerical security assessment of the recently written code to see where improvements are needed.
- 3Finding common configuration errorsHave the agent check for risky patterns such as improper CORS settings or authentication gaps.
- 4Reviewing active security rulesList the specific YAML rules currently being used to audit the codebase.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 16, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableprocoder1234556/novibeleaks is public and reachablegithub.com/procoder1234556/novibeleaks ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-25github.com/procoder1234556/novibeleaks ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubWhat it does
NoVibeLeaks is a Model Context Protocol server (Python, stdio). Your coding agent calls five tools while it writes code — same idea as a focused package in Ponytail’s ponytail-mcp, but for secrets, MCP config risk, and LLM anti-patterns.
| Tool | Purpose |
|---|---|
check_secrets |
Hardcoded API keys, tokens, private keys |
validate_api_key |
Optional live provider check (masked) |
scan_vibe_bugs |
Debug flags, CORS, auth gaps, risky patterns |
get_security_score |
0–100 score + category breakdown |
list_available_rules |
Loaded YAML rule catalog |
flowchart LR
H[IDE / Agent] <-->|stdio MCP| S[NoVibeLeaks]
S --> R[(YAML rules)]
S --> F[Findings + score]
Install
PyPI / uvx (recommended after publish):
{
"mcpServers": {
"novibeleaks": {
"command": "uvx",
"args": ["novibeleaks"]
}
}
}
From this repo (development):
cd secmcp
uv sync
uv run mcp dev server.py
Copy .cursor/mcp.json.example for local paths.
Repo layout (MCP only)
NoVibeLeaks/
├── README.md
├── server.json # MCP Registry manifest
├── secmcp/ # Python package + server.py + rules/
├── assets/ # README diagrams
└── .github/workflows/ # test + PyPI publish
Registry & marketplace
| Goal | Doc |
|---|---|
| Official MCP Registry | docs/MCP_REGISTRY.md |
| MCPmarket listing | docs/MCPMARKET.md |
Develop
cd secmcp && uv sync && pytest -q
License
MIT — LICENSE
NoVibeLeaks MCP questions
How is the security of the code measured?
The server provides a security score ranging from 0 to 100 along with a breakdown by category.