sdlc-integrity-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SDLC_WORKSPACE | No | The workspace directory to audit. Defaults to the process cwd. | process cwd |
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 |
|---|---|
| AuditCodeIntegrityA | Run the code integrity auditor (lifecycle teardown parity, mock-theater test detection, naming invariants, swallowed exceptions) against a file or directory. Returns structured JSON findings. |
| JsSafetyCheckerA | Run the JavaScript safety checker (AST-based duplicate function, duplicate HTML ID, syntax errors) against a file or directory. Returns findings. |
| PythonSafetyCheckerA | Run the Python safety checker (bandit security issues, ruff style/lint issues, AST mutable default arg checks) against Python files. Returns findings. |
| ShellSafetyCheckerA | Run the shell safety checker (missing set -euo pipefail, background job silent failure risk, hardcoded credentials) against shell scripts. Returns findings. |
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 4 tools
Each tool targets a distinct file type or aspect: general code integrity, JavaScript, Python, and shell. No overlap in purpose or input scope.
All four tool names follow a consistent CamelCase pattern with a clear suffix 'Checker' or 'Audit' indicating the tool's function. Consistent across the set.
Four tools is well-scoped for a code integrity/safety server: one general auditor and three language-specific checkers. No redundancy or bloat.
Covers the core languages likely targeted (JavaScript, Python, Shell) plus a general audit. Minor gaps like HTML/CSS checkers exist but the set is coherent for a focused integrity auditor.