sdlc-integrity-mcp
This MCP server provides AI coding agents with tools to audit and enforce code integrity, safety, and quality across an SDLC workspace. It supports scanning multiple languages and catching issues like lifecycle gaps, insecure patterns, and style violations.
AuditCodeIntegrity: Detects lifecycle teardown gaps, mock-theater tests, naming invariant violations, swallowed exceptions, and DRY violations. Returns structured JSON findings.
ShellSafetyChecker: Scans shell scripts for missing
set -euo pipefail, shebang issues, hardcoded credentials, background-job silent-failure risks, and optionally integratesshellcheck.JsSafetyChecker: AST-based analysis of JavaScript/HTML files for syntax errors, duplicate function definitions, and duplicate HTML element IDs.
PythonSafetyChecker: Runs
bandit(High/Critical security issues),ruff(lint/style), and AST checks foreval/exec, unsafepickleloads, hardcoded credentials, and mutable default arguments.
All tools accept a target (file or directory) and optional timeout up to 600 seconds; relative paths resolve against the SDLC_WORKSPACE environment variable. Findings are returned as MCP results with isError: true if issues are found. The server can be extended via custom rules placed in <workspace>/.sdlc-rules/.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@sdlc-integrity-mcp audit my project for lifecycle gaps and safety issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SDLC Code Integrity
MCP server for enterprise SDLC code integrity. AI coding agents call its tools over the Model Context Protocol to scan a workspace for lifecycle teardown gaps, mock-theater tests, DRY violations, and language-specific safety issues in shell, JavaScript/HTML, and Python.
Quick start
Set SDLC_WORKSPACE to the absolute path of the repo to audit. If omitted, the server uses its process working directory. The server speaks MCP over stdio (no HTTP port).
Cursor
Add to ~/.cursor/mcp.json or the project .cursor/mcp.json:
{
"mcpServers": {
"sdlc-integrity": {
"command": "npx",
"args": ["-y", "@asobacloud/sdlc-integrity-mcp"],
"env": {
"SDLC_WORKSPACE": "/absolute/path/to/your/repo"
}
}
}
}Restart Cursor (or reload MCP servers), then ask the agent to run the integrity tools.
Claude Code
CLI (user scope):
claude mcp add --transport stdio --scope user \
--env SDLC_WORKSPACE=/absolute/path/to/your/repo \
sdlc-integrity -- npx -y @asobacloud/sdlc-integrity-mcpOr put the same JSON under mcpServers in project .mcp.json (team-shared) or ~/.claude.json (user-wide):
{
"mcpServers": {
"sdlc-integrity": {
"command": "npx",
"args": ["-y", "@asobacloud/sdlc-integrity-mcp"],
"env": {
"SDLC_WORKSPACE": "/absolute/path/to/your/repo"
}
}
}
}Verify with claude mcp list. Project .mcp.json servers need approval the first time you open the repo in Claude Code.
Codex
CLI:
codex mcp add sdlc-integrity --env SDLC_WORKSPACE=/absolute/path/to/your/repo -- npx -y @asobacloud/sdlc-integrity-mcpOr edit ~/.codex/config.toml (or project .codex/config.toml in a trusted project):
[mcp_servers.sdlc-integrity]
command = "npx"
args = ["-y", "@asobacloud/sdlc-integrity-mcp"]
[mcp_servers.sdlc-integrity.env]
SDLC_WORKSPACE = "/absolute/path/to/your/repo"Codex CLI, the IDE extension, and the ChatGPT desktop Codex host share this config.
Run directly
npx -y @asobacloud/sdlc-integrity-mcpRelated MCP server: aegis
Tools
Tool | Runtime | What it checks |
|
| Lifecycle teardown parity, mock-theater test detection, naming invariants, swallowed exceptions, DRY / duplicative functions. Returns structured JSON. |
|
| Missing |
|
| JS/HTML syntax errors, duplicate function definitions, duplicate HTML element IDs (AST-based via esprima). |
|
| bandit (High/Critical), ruff, AST checks for |
Each tool accepts:
target— file or directory to scan (relative paths resolve againstSDLC_WORKSPACE)timeout— optional timeout in ms (default120000, max600000)
Checker exit code 1 (findings) becomes isError: true on the MCP result. Unexpected crashes are reported as errors.
Requirements
Runtime | Required for |
Node.js ≥ 22 | MCP server + |
Python 3 |
|
bash |
|
Optional (skipped with a warning if missing):
Tool | Improves |
| |
| |
|
Custom rules
Drop JSON tool configs into <workspace>/.sdlc-rules/. Local rules override bundled tools with the same name, or add new ones. Script paths resolve relative to .sdlc-rules/.
{
"name": "MyCustomAudit",
"description": "Project-specific integrity check",
"input_schema": {
"type": "object",
"properties": {
"target": { "type": "string", "description": "File or directory to scan" },
"timeout": { "type": "integer", "description": "Timeout in ms (max 600000)" }
}
},
"execution": {
"runtime": "python3",
"script": "./my-audit.py",
"args": ["--target", "{{target}}"],
"default_timeout": 120000,
"max_timeout": 600000
}
}{{placeholder}} values are filled from the tool call. If a value is omitted, that flag and its placeholder are skipped.
Architecture
rules/*.json → tool schemas + execution specs
scripts/* → checker subprocesses
src/loader.ts → bundled rules + .sdlc-rules/ overlay
src/runner.ts → spawn, timeouts, exit-code → isError
src/index.ts → MCP stdio server
bin/cli.js → npx / bin entrypointDevelopment
git clone https://github.com/AsobaCloud/sdlc-integrity-mcp.git
cd sdlc-integrity-mcp
npm install
npm run build
npm testScript | Purpose |
| Compile TypeScript → |
| E2E via real MCP |
| Run the server on stdio |
|
|
Local MCP config (instead of npx):
{
"mcpServers": {
"sdlc-integrity": {
"command": "node",
"args": ["/absolute/path/to/sdlc-integrity-mcp/dist/index.js"],
"env": {
"SDLC_WORKSPACE": "/absolute/path/to/your/repo"
}
}
}
}Releasing
CI runs build + E2E on every push/PR. To publish a new version:
Bump
versioninpackage.jsonCommit, push, and create a GitHub Release (
gh release create vX.Y.Z --generate-notes).github/workflows/publish.ymlpublishes to npm (Trusted Publisher / OIDC, orNPM_TOKENif configured)
License
MIT © Asoba
Available Tools
4 toolsAuditCodeIntegrityA
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.
Inputs: target, timeout.
JsSafetyCheckerA
Run the JavaScript safety checker (AST-based duplicate function, duplicate HTML ID, syntax errors) against a file or directory. Returns findings.
Inputs: target, timeout.
PythonSafetyCheckerA
Run the Python safety checker (bandit security issues, ruff style/lint issues, AST mutable default arg checks) against Python files. Returns findings.
Inputs: target, timeout.
ShellSafetyCheckerA
Run the shell safety checker (missing set -euo pipefail, background job silent failure risk, hardcoded credentials) against shell scripts. Returns findings.
Inputs: target, timeout.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Audit your MCP servers for poisoned tools and leaked secrets, and check AI-generated code for flaws.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
Scan AI agent skills, MCP server packages and MCP configs before you install them. Static analysis.
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP security server for AI coding agents. 12 tools: pre-install guardian, vulnerability audit, supply-chain attack detection via static code analysis, and CycloneDX 1.6 SBOM generation. Zero runtime dependencies.15111 npm15Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server for auditing AI agent permissions and access by scanning for the trifecta of credentials, injection, and reach without heavy infrastructure.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enforces repository governance rules for AI coding agents, providing tools to validate plans, diffs, and scan for architectural and safety violations.2MIT
- AlicenseAqualityBmaintenanceMCP server that enables AI coding assistants to audit repositories against engineering rules, generating self-contained HTML reports with citations and optional GitHub issue filing.102Apache 2.0