Mcp Vibe Checker — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Mcp Vibe Checker (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Your code has energy. Time to find out what kind.
An MCP server that gives your code a vibe check — assigning personality types to functions, rating variable name energy, and suggesting more aesthetic alternatives. Because userData was never the right name. It should be soulContainer.
handleSubmit a main character, or does it have NPC behavior? Find out.x gets "cryptic oracle energy (3/10)". MAXIMUM_RETRY_COUNT gets "dramatic monologue energy (9/10)". They earned it.isValid → vibesPassing. error → chaosEvent. You're welcome.Input:
function handleSubmit(userData, isValid) {
const result = userData.name;
return result;
}Output:
{
"overallVibe": "cozy cottage-core with hints of cyberpunk",
"vibeScore": 6.8,
"functions": [
{
"name": "handleSubmit",
"personality": "main character energy",
"assessment": "This function carries the entire plot"
}
],
"variables": [
{
"name": "userData",
"energy": 7,
"assessment": "classic protagonist (7/10) — reliable, not flashy",
"suggestion": "soulContainer"
},
{
"name": "isValid",
"energy": 7,
"assessment": "classic protagonist (7/10) — reliable, not flashy",
"suggestion": "vibesPassing"
},
{
"name": "result",
"energy": 5,
"assessment": "functional but uninspired (5/10) — exists, which is something",
"suggestion": "manifestation"
}
],
"codeAesthetic": "Your code reads like a mystery novel — lots of setup, unclear payoff",
"recommendation": "Consider adding more comments for dramatic tension"
}npx mcp-vibe-checkAdd to your .mcp.json:
{
"mcpServers": {
"vibe-check": {
"command": "npx",
"args": ["-y", "mcp-vibe-check"]
}
}
}Then ask Claude: "What vibes does this codebase give off?"
Your functions can be:
| Type | Meaning |
|---|---|
| main character energy | Carries the entire plot |
| side quest vibes | Important but easily forgotten |
| NPC behavior | Does its job without complaint |
| protagonist arc | Started simple, evolved into something bigger |
| villain origin story | Nobody asked for this complexity |
| comic relief | Technically unnecessary, yet essential |
| mentor energy | Older, wiser, called at critical moments |
| chosen one potential | Untested but destined for greatness |
Is this useful for code review? No. That's the point.
Will this improve my code quality? Statistically unlikely. Spiritually, possibly.
Why does `console.log` hurt my vibe score? Because it's not aesthetic. Use a proper logger. Your stdout deserves better.
My function got "NPC behavior". Should I be offended? Only if your function has feelings. Which, based on this tool, it might.
"Not all code reviews need to be actionable. Some just need to be vibes."
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.