mcp-vibe-check
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vibe-checkA | Get a vibe check on your code. Assigns personality types to functions, rates variable name energy, and suggests more aesthetic alternatives. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap with other tools. The tool's purpose is clearly distinct by virtue of being the only tool in the server.
A single tool name cannot have inconsistencies. The name 'vibe-check' is descriptive and follows a clear, if not standard, convention appropriate for its function.
The server has a narrow, focused purpose—providing vibe checks on code. One tool is slightly below the typical 3-15 range, but it is perfectly reasonable for this specific, limited scope.
The tool covers the full stated purpose: assigning personality types, rating variable name energy, and suggesting aesthetic alternatives. There are no obvious missing operations within its defined domain.