prospector-mcp
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prospector_runC | Run Prospector static analysis on a file or directory. |
| prospector_check_readyA | Check whether Prospector is installed and report its version. |
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 have clearly distinct purposes: one runs the analysis, the other checks installation. No overlap.
Both tools follow a consistent 'prospector_' prefix with a verb (run, check_ready). Clear and predictable pattern.
Only 2 tools for a static analysis server feels minimal but not unreasonable if the scope is limited to running checks.
Missing common operations like listing rules, retrieving results, or configuring the analysis. Gaps are significant for a typical analysis workflow.