deep-code-security (backspace-shmackspace/deep-code-security) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

deep-code-security

Multi-language SAST and AI-powered fuzzing MCP server for Claude Code integration, enabling static and dynamic security analysis of code.

→ backspace-shmackspace/deep-code-security· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

backspace-shmackspace

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: ANTHROPIC_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configDCS_BRIDGE_MAX_TARGETSMax fuzz targets produced by SAST-to-Fuzz bridge
configDCS_FUZZ_ALLOWED_PLUGINSpython,c and AI-powered harness generation with
🔐 secretANTHROPIC_API_KEYAPI key for Claude (required for fuzzing)
configGOOGLE_CLOUD_PROJECTGCP project ID for Vertex AI (optional)
configCLOUD_ML_PROJECT_NUMBERGCP project number for Vertex AI (optional)
configANTHROPIC_VERTEX_PROJECT_IDVertex AI project override (optional)
configDCS_SCANNER_BACKENDScanner backend: semgrep, treesitter, or auto (prefer semgrep if available)
configDCS_REGISTRY_PATH
configDCS_ALLOWED_PATHS
configDCS_SANDBOX_TIMEOUTPer-exploit timeout in seconds
configDCS_CONTAINER_RUNTIME
configDCS_MAX_CONCURRENT_SANDBOXESConcurrency limit for sandbox execution
configDCS_MAX_FILESMax files per scan
configDCS_MAX_RESULTSMax findings returned per hunt operation
configDCS_MAX_VERIFICATIONSMax findings to verify in auditor phase
configDCS_QUERY_TIMEOUTTree-sitter query timeout in seconds
configDCS_QUERY_MAX_RESULTSMax results per tree-sitter query
configDCS_SEMGREP_TIMEOUTMaximum seconds for Semgrep subprocess
configDCS_SEMGREP_RULES_PATHPath to DCS Semgrep rule files
configDCS_FUZZ_MODELClaude model for input generation
configDCS_FUZZ_MAX_ITERATIONSMax fuzzing iterations
configDCS_FUZZ_INPUTS_PER_ITERInputs generated per iteration
configDCS_FUZZ_TIMEOUT_MSPer-input execution timeout
configDCS_FUZZ_MAX_COST_USDAPI cost budget
configDCS_FUZZ_OUTPUT_DIRCorpus and report output directory
configDCS_FUZZ_GCP_REGIONGCP region for Vertex AI
configDCS_FUZZ_MCP_TIMEOUTHard wall-clock timeout for MCP fuzz invocations
configDCS_FUZZ_C_COMPILE_FLAGSComma-separated gcc flags (e.g., -O2,-march=native)
configDCS_FUZZ_C_INCLUDE_PATHSComma-separated include paths for C harness compilation
configDCS_OUTPUT_DIR
// quality suggestions

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 1 concrete improvement we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/backspace-shmackspace/deep-code-security)](https://m8ven.ai/mcp/backspace-shmackspace/deep-code-security)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 80e448e5edc123c8296bc2225f86dae9cfb918f1
code hash: 65398c124e90e08a4393cb51f1e363dc82bc052518e08bb6cb407e6356ec1ac5
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client