provekit-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROVEKIT_MCP_ROOT | Yes | The absolute path to the workspace root that the scanner is allowed to read from. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_codeA | Scan a snippet of code for leaked secrets and insecure patterns
(OWASP Top 10). Returns findings sorted by severity. No filesystem
access. |
| scan_pathA | Scan a single source file for leaked secrets and insecure patterns.
|
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 are clearly distinguished by their input type: scan_code takes a code snippet, while scan_path takes a file path. Though both perform similar security scanning, the descriptions make the boundary unambiguous, so an agent should rarely misselect.
Both tools follow a consistent 'scan_<target>' pattern with snake_case, making the naming predictable and intuitive. The verb-noun structure is uniform and there are no stylistic deviations.
With only two tools, the server feels thin for a security scanning purpose. The count is borderline—not egregiously small, but it offers only the most basic scanning operations and lacks the breadth one might expect.
The server only supports scanning a snippet or a single file, with no ability to scan directories, repositories, or multiple files at once. This is a significant gap for a security scanner, as users would likely need batch or recursive scanning to be practical.