CodeVitals
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 |
|---|---|
| health_checkA | Checks whether the CodeVitals MCP server is running. |
| analyze_repositoryB | Analyzes a repository and returns metadata, a health score, and a summary. |
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 2 tools
health_check and analyze_repository are clearly distinct: one checks server status, the other performs repository analysis. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern (health_check, analyze_repository), making the naming predictable and uniform.
With only 2 tools, the set feels thin. However, the scope is narrow and focused on repository analysis, so it is borderline rather than severely lacking.
The server covers its core purpose with a health check and a repository analysis tool. The analysis tool provides metadata, health score, and summary, leaving no obvious dead ends for basic usage, though deeper analysis features are absent.