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 分

    請在儲存庫或註冊中心條目中宣告授權條款。