Mcp Vibe Checker

io.github.webmoleai由 GitHub 账号 webmoleai 发布v0.1.1更新于 Oct 24, 2026

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

已验证STDIO仅桌面开发者工具

概览

AI 生成的概览

一个娱乐性质的 MCP 服务器,为代码做“气质检查”:给函数分配人格类型、给变量名打能量分并建议更有美感的命名。

可以做什么
  • 为函数分配人格类型,例如主角光环或路人行为
  • 给变量名打能量分并给出简短评价
  • 为变量建议更有美感的替代名称
  • 生成整体气质分数、代码审美评估与一条建议
适用场景
适合娱乐、演示或团队轻松调侃时,对一段代码或代码库获得刻意不科学的趣味评价。README 明确说明它不适用于代码审查,也基本不会提升代码质量。
运行要求
通过 npx 从 npm 包 mcp-vibe-checker 作为本地进程运行,需要 Node.js。未声明任何认证、环境变量或请求头。
安装前请注意
输出刻意随意且不科学,不应把评分或改名建议当作真正的审查意见。它是本地 stdio 进程,未声明凭据,也没有写入类操作。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp Vibe Checker,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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

来源:README.md,提交 6872bb2

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。