@securecode-ai/mcp
v0.6.0
Published
Standalone SecureCode MCP server — scan, map, fix, and attack tools for AI coding assistants. Works without the VS Code extension.
Downloads
5,315
Maintainers
Readme
SecureCode MCP
Standalone MCP (Model Context Protocol) server for SecureCode AI. Provides security scanning tools to AI coding assistants — Cursor, Claude Code, Codex, Windsurf, and other compatible MCP clients — without requiring the VS Code extension.
Install
npm install -g @securecode-ai/mcpOr use directly with npx (no install needed):
npx @securecode-ai/mcp scan src/app.tsQuick Start
securecode-mcp login # Authenticate (email + OTP)
securecode-mcp doctor # Verify your setup works
securecode-mcp scan src/app.ts # Scan a file from the CLI
securecode-mcp serve # Start the MCP server (for AI clients)CLI Commands
securecode-mcp serve [--workspace <path>] Start the MCP stdio server
securecode-mcp login [--api-url <url>] Authenticate via email + OTP
securecode-mcp status Show current auth status
securecode-mcp logout Remove stored credentials
securecode-mcp scan <filePath> [--json] Scan a single file
[--depth <fast|deep|agent>] [--workspace <path>]
securecode-mcp doctor Verify setup (credentials, API, scan)
securecode-mcp --help Show helpScan from CLI
# Agent scan (deep, AI-powered)
securecode-mcp scan src/app/api/users/route.ts
# Fast scan (no AI, free, <5s)
securecode-mcp scan src/lib/auth.ts --depth fast
# JSON output for CI
securecode-mcp scan src/app.ts --json
# Exit codes: 0 = no findings, 1 = findings found, 2 = errorCI/CD Example
# GitHub Action
- name: SecureCode scan
run: |
npm install -g @securecode-ai/mcp
securecode-mcp login # or set SECURECODE_API_TOKEN
securecode-mcp scan src/ --json > scan-results.json
# Exit 1 if findings foundMCP client configuration
Cursor / Windsurf
{
"mcpServers": {
"securecode": {
"command": "npx",
"args": ["-y", "@securecode-ai/mcp@latest", "serve", "--workspace", "/path/to/your/project"],
"env": {
"SECURECODE_API_TOKEN": "your-api-token-here"
}
}
}
}Or if installed globally:
{
"mcpServers": {
"securecode": {
"command": "securecode-mcp",
"args": ["serve", "--workspace", "/path/to/your/project"]
}
}
}Claude Code
claude mcp add securecode -s user -- securecode-mcp serve --workspace /path/to/your/projectTools (17)
Scanning
| Tool | Description | Approval |
|------|-------------|----------|
| securecode.scan | Scan code for vulnerabilities (AI pipeline) | No |
| securecode.agent-scan | Agent-mode deep scan with 20+ tools, structured proof, and sandbox verification | No |
| securecode.agent-scan-batch | Sequential batch scan: map + architecture scout + scan top N files one at a time | No |
| securecode.scan-batch | Scan multiple files in one call | No |
| securecode.scan-secrets | Scan for hardcoded secrets and PII (local, no AI) | No |
| securecode.scan-dependencies | Scan lockfiles for known vulnerabilities (OSV/NVD) | No |
Project Analysis
| Tool | Description | Approval |
|------|-------------|----------|
| securecode.map | Build project map: endpoints, middleware, auth, architecture context | No |
Fixes & Testing
| Tool | Description | Approval |
|------|-------------|----------|
| securecode.fix | Generate a patch for a specific finding | Yes |
| securecode.attack | Endpoint red-team testing (beta) | Yes |
| securecode.run-tests | Run tests in sandbox for verification | Yes |
Agent Memory (FP Learning)
| Tool | Description | Approval |
|------|-------------|----------|
| securecode.record-false-positive | Dismiss a finding as FP — agent learns not to report it | No |
| securecode.get-agent-memory | View learned false positives and known facts | No |
| securecode.clear-agent-memory | Clear all agent memory (or one FP by ID) | No |
| securecode.add-known-fact | Add a project fact for faster investigations | No |
Finding Review
| Tool | Description | Approval |
|------|-------------|----------|
| securecode.review-findings | Review the finding queue for a workspace | No |
| securecode.decide-finding | Accept or reject a finding in the review queue | No |
| securecode.clear-finding-reviews | Clear all finding reviews for a workspace | No |
How Agent Memory Works
When the agent reports a false positive, dismiss it with record-false-positive. The agent stores the pattern in .securecode/agent-memory.json and will not report similar patterns in future scans of that workspace.
Scan 1: Agent reports csp_bypass → You dismiss as "intentional design"
Scan 2: Agent sees the FP memory → skips similar patterns → fewer false positivesMemory is per-workspace, user-owned, and deletable. No cross-tenant leakage.
Agent Scan Architecture
The agent scan (securecode.agent-scan) is an AI security investigator that:
- Maps the project architecture (architecture scout with trust boundaries, security controls, risks)
- Reads the target file and related files across the codebase
- Traces data flows (taint tracking, cross-file flow with structured source→sink→hop chains)
- Checks guards, endpoint policies, and configuration
- Verifies threat model applicability and capability reachability
- Self-critiques before reporting (selfCritique field)
- Gets reviewed by an independent critique LLM
- Proves findings in a sandbox (PROVEN/UNPROVEN)
- Generates fixes for proven findings
Agent tools (20+): read_file, search_code, trace_flow, trace_flow_cross_file, check_guard, check_policy, get_endpoints, list_imports, list_files, call_graph, git_blame, git_history, git_diff, check_dependencies, read_config, find_definition, find_references, find_tests, run_tests, finish.
The deterministic control plane enforces proof quality:
- Every finding requires source, reachability, control, threat-model, and impact evidence
- Unproven concerns become investigation notes, not findings
- Architecture risks expand across related files (callers, implementations, sinks)
- The finish gate rejects finish while proof requirements remain unsatisfied
Languages: JavaScript, TypeScript, Python (partial).
Environment Variables
| Variable | Default | Description |
|----------|---------|-------------|
| SECURECODE_API_TOKEN | — | API token (alternative to login) |
| SECURECODE_API_URL | https://api.usesecurecode.tech | API base URL |
| SECURECODE_ATTACK_ENABLED | — | Set to 1 to enable the attack tool |
Security
- Credentials stored in OS keychain (Windows Credential Manager, macOS Keychain, Linux Secret Service) with file fallback (
~/.securecode/credentials.json, mode 0600). - File reads are confined to the
--workspaceroot. - Fixes are returned for review and never auto-applied.
- Agent memory is per-workspace (
.securecode/agent-memory.json), never sent to the API. - No telemetry.
Development
npm install
npm run build
npm testLicense
MIT
