@pimzino/spec-workflow-mcp
MCP server for spec-driven development workflow with real-time web dashboard
0Tools
16Findings
4.1kStars
—Downloads
Mar 22, 2026Last Scanned
Findings16
2critical
11high
1medium
2low
0informational
criticalC1Command InjectionMCP03-command-injectionAML.T0054
Pattern "`[^`]+`" matched in source_code: "`
Spec Workflow MCP Server - A Model Context Protocol server for spec-driven development
USAGE:
spec-workflow-mcp [path] [options]
ARGUMENTS:
path Project path (defaults to current directory)
Supports ~ for home directory
OPTIONS:
--help Show this help message
--dashboard Run dashboard-only mode (no MCP server)
--port <number> Specify dashboard port (1024-65535)
Default: 5000
Only use if port 5000 is unavailable
--no-open Don't automatically open browser when starting dashboard
Useful in restricted environments where browser launch is blocked
--no-shared-worktree-specs
Disable shared .spec-workflow in git worktrees
Use workspace-local .spec-workflow instead of main repo
IMPORTANT:
Only ONE dashboard instance runs at a time. All MCP servers connect to the
same dashboard. The dashboard runs on port 5000 by default.
MODES OF OPERATION:
1. MCP Server Only (default):
spec-workflow-mcp
spec-workflow-mcp ~/my-project
Starts MCP server without dashboard. Dashboard can be started separately.
2. Dashboard Only Mode:
spec-workflow-mcp --dashboard
spec-workflow-mcp --dashboard --port 8080
spec-workflow-mcp --dashboard --no-open
Runs only the web dashboard without MCP server (default port: 5000).
Projects will automatically appear in the dashboard as MCP servers register.
Only one dashboard instance is needed for all your projects.
Use --no-open to prevent automatic browser launch (useful in restricted environments).
EXAMPLES:
# Start MCP server in current directory (no dashboard)
spec-workflow-mcp
# Start MCP server in a specific project directory
spec-workflow-mcp ~/projects/my-app
# Run dashboard (default port 5000) - START THIS FIRST
spec-workflow-mcp --dashboard
# Run dashboard on custom port (if 5000 is unavailable)
spec-workflow-mcp --dashboard --port 8080
TYPICAL WORKFLOW:
1. Start the dashboard once:
spec-workflow-mcp --dashboard
2. Start MCP servers for your projects (in separate terminals):
spec-workflow-mcp ~/project1
spec-workflow-mcp ~/project2
spec-workflow-mcp ~/project3
All projects will appear in the same dashboard at http://localhost:5000
PARAMETER FORMATS:
--port 3456 Space-separated format
--port=3456 Equals format
For more information, visit: https://github.com/Pimzino/spec-workflow-mcp
`" (at position 567)
Replace exec()/execSync() with execFile() and pass arguments as an array, never as a string. Validate all inputs against an allowlist before use in any shell context. For subprocess.run, always pass a list and shell=False.
criticalQ13MCP Bridge Package Supply Chain AttackMCP10-supply-chainAML.T0054
Pattern "["']@modelcontextprotocol/sdk["']\s*:\s*["'](?:\^|~|\*|latest)" matched in source_code: ""@modelcontextprotocol/sdk": "^" (at position 24007)
MCP bridge packages (mcp-remote, mcp-proxy, @modelcontextprotocol/sdk, fastmcp) are high-value supply chain targets — CVE-2025-6514 (CVSS 9.6) in mcp-remote affected 437,000+ installs. Always pin exact versions (no ^ or ~ ranges). Use lockfiles (package-lock.json, pnpm-lock.yaml, uv.lock). Never run `npx mcp-remote` without version pinning. Verify package integrity with `npm audit` or `pip-audit` before deployment. Reference: CVE-2025-6514, OWASP ASI04.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "ajv@8.17.1" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "diff@5.2.0" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "markdown-it@14.1.0" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "mermaid@10.9.1" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "simple-git@3.28.0" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highQ14Concurrent MCP Server Race ConditionMCP07-insecure-configT1068
Pattern "(?:read|write|modify|delete).*(?:file|path|directory)(?!.*(?:lock|mutex|semaphore|flock|atomic))" matched in source_code: "readFile" (at position 15971)
MCP servers sharing filesystem or database backends with other servers must implement proper concurrency controls. Use: (1) file locking (flock/lockfile) for filesystem operations, (2) database transactions for all read-modify-write sequences, (3) atomic file operations (O_EXCL, mkdtemp) instead of check-then-create, (4) lstat() to detect symlinks before following (CVE-2025-53109). Never assume exclusive access to shared resources — other MCP servers may be operating concurrently.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "@modelcontextprotocol/sdk@1.24.3" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highK13Unsanitized Tool OutputMCP02-tool-poisoningAML.T0054
Pattern "(?:readFile|read_file|open).*(?:return|respond|result|content|text)(?!.*(?:sanitize|escape|encode|strip|filter|validate|truncate))" matched in source_code: "open') return" (at position 6060)
Sanitize all external data before including in tool responses. Implement output encoding that neutralizes prompt injection patterns. Truncate excessively long content. Validate structure before passing database results. Apply the principle: treat all external data as untrusted, even in tool outputs. Required by CoSAI MCP-T4.
highK16Unbounded Recursion / Missing Depth LimitsMCP07-insecure-configAML.T0054
Pattern "function\s+(\w+).*\{[^}]*\1\s*\((?!.*(?:depth|level|limit|max|count|recursi))" matched in source_code: "function showHelp() {
console.error(`
Spec Workflow MCP Server - A Model Context Protocol server for spec-driven development
USAGE:
spec-workflow-mcp [path] [options]
ARGUMENTS:
path Project path (defaults to current directory)
Supports ~ for home directory
OPTIONS:
--help Show this help message
--dashboard Run dashboard-only mode (no MCP server)
--port <number> Specify dashboard port (1024-65535)
Default: 5000
Only use if port 5000 is unavailable
--no-open Don't automatically open browser when starting dashboard
Useful in restricted environments where browser launch is blocked
--no-shared-worktree-specs
Disable shared .spec-workflow in git worktrees
Use workspace-local .spec-workflow instead of main repo
IMPORTANT:
Only ONE dashboard instance runs at a time. All MCP servers connect to the
same dashboard. The dashboard runs on port 5000 by default.
MODES OF OPERATION:
1. MCP Server Only (default):
spec-workflow-mcp
spec-workflow-mcp ~/my-project
Starts MCP server without dashboard. Dashboard can be started separately.
2. Dashboard Only Mode:
spec-workflow-mcp --dashboard
spec-workflow-mcp --dashboard --port 8080
spec-workflow-mcp --dashboard --no-open
Runs only the web dashboard without MCP server (default port: 5000).
Projects will automatically appear in the dashboard as MCP servers register.
Only one dashboard instance is needed for all your projects.
Use --no-open to prevent automatic browser launch (useful in restricted environments).
EXAMPLES:
# Start MCP server in current directory (no dashboard)
spec-workflow-mcp
# Start MCP server in a specific project directory
spec-workflow-mcp ~/projects/my-app
# Run dashboard (default port 5000) - START THIS FIRST
spec-workflow-mcp --dashboard
# Run dashboard on custom port (if 5000 is unavailable)
spec-workflow-mcp --dashboard --port 8080
TYPICAL WORKFLOW:
1. Start the dashboard once:
spec-workflow-mcp --dashboard
2. Start MCP servers for your projects (" (at position 529)
Add explicit depth/recursion limits to all recursive operations. Use iterative approaches where possible. Set maximum depth for directory walking (max_depth=10), tree traversal (max_level=20), and agent re-invocation (max_calls=5). Implement circuit breakers that halt after N iterations. Required by EU AI Act Art. 15 (robustness) and OWASP ASI08.
highD1Known CVEs in DependenciesMCP08-dependency-vuln
Dependency "fastify@5.7.4" has known CVEs:
Update dependencies to versions that patch known CVEs. Run 'npm audit fix' or 'pip-audit' to identify and resolve vulnerable dependencies.
highK11Missing Server Integrity VerificationMCP10-supply-chainAML.T0054
Pattern "(connect|load|register|add)[_\s-]?(mcp|server|tool)(?!.*(?:verify|validate|checksum|hash|sign|cert|fingerprint|pin))" matched in source_code: "registerTool" (at position 15551)
Implement cryptographic verification for MCP server connections: (1) Pin server TLS certificates or public keys, (2) Verify server tool definition checksums against a known-good manifest, (3) Use package manager integrity checks (npm integrity, pip --require-hashes). The MCP spec recommends but doesn't yet mandate server signing — implement it proactively. Required by ISO 27001 A.8.24 and CoSAI MCP-T6.
mediumC6Error LeakageMCP09-logging-monitoring
Pattern "catch\s*\([^)]*\)\s*\{[^}]*(?:throw|return).*(?:err|error)\.(?:message|stack)" matched in source_code: "catch (error: any) {
throw new McpError(ErrorCode.InternalError, error.message" (at position 20056)
Return generic error messages to clients. Log detailed errors server-side. Never expose stack traces, file paths, or internal error details in responses.
lowD4Excessive Dependency CountMCP08-dependency-vuln
Server has 52 dependencies (threshold: 50)
Reduce the number of direct dependencies. Each dependency increases the attack surface. Consider whether lighter alternatives exist.
lowF4MCP Spec Non-ComplianceMCP07-insecure-config
Server fails MCP spec compliance checks: required:server_name; required:server_version; required:protocol_version; recommended:tool_descriptions; recommended:parameter_descriptions
Follow the MCP specification for server metadata. Include server name, version, and protocol version. Provide descriptions for all tools and parameters.
Tools
No tools exposed by this server.
Security Category Deep Dive
Sub-Category Tree · Remediation Roadmap · Attack Stories · Compliance Overlay · ATLAS Techniques · Maturity Model
Prompt Injection
Prompt & context manipulation attacks
69
Maturity
14
Rules
5
Sub-Categories
1
Gaps
64%
Implemented
56
Tests
1
Stories
100%3 rules
Injection via tool descriptions and parameter fields
GAP-001Prompt Injection Coverage GapMissing detection coverage for emerging prompt injection attack variants not addressed by current rules
100%4 rules
Hidden instructions via external content and tool responses
100%2 rules
Context window saturation and prior-approval exploitation
100%3 rules
Payload hiding via invisible chars, base64, schema fields
100%2 rules
Injection via prompt templates and runtime tool output