MCP Project Guard
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_architectureB | Analyze project architecture, detect language, and return validation rules |
| find_similar_codeB | Find existing similar components, functions, or patterns in the project |
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
The two tools address distinct concerns: one analyzes project architecture and language, the other searches for similar code patterns. There is no overlap in purpose, making selection unambiguous.
Both tools follow a consistent verb_noun pattern (analyze_architecture, find_similar_code) with descriptive, clear names. The naming style is uniform and predictable.
With only two tools, the set feels thin for a 'Project Guard' server. According to the calibration, 1-2 tools is borderline; each tool is substantive, but the overall scope appears limited.
The server lacks core guard functionality such as validation, rule checking, or issue reporting. It only offers architecture analysis and code similarity search, which are helper operations rather than a complete project-guard surface.