Mcp Vibe Checker

io.github.webmoleaiPublished by GitHub account webmoleaiv0.1.1Updated Oct 24, 2026

Vibe-check your code — personality types, energy ratings, aesthetic suggestions.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A novelty MCP server that "vibe-checks" code, assigning personality types to functions, rating variable names and suggesting aesthetic alternatives.

What you can do
  • Assign personality types to functions, such as main character energy or NPC behavior
  • Rate the energy of variable names and give a short assessment of each
  • Suggest more aesthetic alternative names for variables
  • Produce an overall vibe score and a qualitative code aesthetic assessment with a recommendation
When to use it
For fun, demos or lighthearted team banter when you want a playful, deliberately unscientific take on a snippet or codebase. The README states it is not useful for code review and unlikely to improve code quality.
Requirements
Runs as a local process via npx from the npm package mcp-vibe-checker; Node.js is needed. No authentication, environment variables or headers are declared.
Before you install
Output is intentionally arbitrary and unscientific, so do not treat its ratings or name suggestions as real review feedback. It is a local stdio process with no declared credentials or write actions.

Installation

In SourceWeft

  1. Open Mcp Vibe Checker 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

mcp-vibe-check

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.

What It Does

  • Personality types for functions — Is handleSubmit a main character, or does it have NPC behavior? Find out.
  • Variable energy ratings — x gets "cryptic oracle energy (3/10)". MAXIMUM_RETRY_COUNT gets "dramatic monologue energy (9/10)". They earned it.
  • Aesthetic name suggestions — isValid → vibesPassing. error → chaosEvent. You're welcome.
  • Overall vibe score — A completely arbitrary number between 1 and 10 that means nothing and everything.
  • Code aesthetic assessment — Qualitative vibes. Unscientific. Occasionally accurate.

Example

Input:

javascript
function handleSubmit(userData, isValid) {  const result = userData.name;  return result;}

Output:

json
{  "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"}

Install

bash
npx mcp-vibe-check

Configure in Claude Code

Add to your .mcp.json:

json
{  "mcpServers": {    "vibe-check": {      "command": "npx",      "args": ["-y", "mcp-vibe-check"]    }  }}

Then ask Claude: "What vibes does this codebase give off?"

Personality Types

Your functions can be:

TypeMeaning
main character energyCarries the entire plot
side quest vibesImportant but easily forgotten
NPC behaviorDoes its job without complaint
protagonist arcStarted simple, evolved into something bigger
villain origin storyNobody asked for this complexity
comic reliefTechnically unnecessary, yet essential
mentor energyOlder, wiser, called at critical moments
chosen one potentialUntested but destined for greatness

FAQ

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."

Source: README.md at commit 6872bb2

Tools

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

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% 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

    Declare a license in the repository or the registry entry.