Skills/PyPI/semgrep-mcp

semgrep-mcp@0.9.0

VERIFIED· not started

Publisher claims: "MCP Server for using Semgrep to scan code" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher semgrep · publishing for 592 daysInstalls 10,858Last detonated 58 min ago
$claude mcp add semgrep-mcp -- uvx semgrep-mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
SEMGREP_APP_TOKENConfiguration, not credentials: JS2P_DEBUG, SEMGREP_IS_HOSTED, SEMGREP_MCP, SEMGREP_MCP_DISABLE_TRACING, SEMGREP_OTEL_ENDPOINT, SEMGREP_PATH, SEMGREP_SETTINGS_FILE, SEMGREP_URL, SEMGREP_USER_AGENT_APPEND, USE_SEMGREP_RPC
Where it talks to
semgrep.dev, semgrep.ai (its own)Also claude.ai, githubusercontent.com, datadoghq.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names claude.ai, githubusercontent.com, datadoghq.com as well as its own vendor. The guard injects SEMGREP_APP_TOKEN only into requests to semgrep.dev (and its subdomains) and refuses the rest.

$vet-skills run --secrets SEMGREP_APP_TOKEN=semgrep.dev -- uvx semgrep-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedscripts/configure_semgrep_mcp.py:154 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedsrc/semgrep_mcp/utilities/utils.py:99 · Python subprocess execution detectedprocess = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/configure_semgrep_mcp.py:37 · Python subprocess execution detectedresult = subprocess.run(["claude", "--version"], capture_output=True, text=True, timeout=10)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Destructive file system command detectedDockerfile:35 · Destructive file system command detectedRUN rm -rf /home/app/.semgrepFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedscripts/configure_semgrep_mcp.py:304 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedsrc/semgrep_mcp/utilities/utils.py:113 · Python subprocess execution detectedprocess = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/configure_semgrep_mcp.py:227 · Python subprocess execution detectedresult = subprocess.run(claude_cmd, capture_output=True, text=True, timeout=30)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedsrc/semgrep_mcp/semgrep.py:184 · Python subprocess execution detectedprocess = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Access to sensitive file pathstests/unit/test_safe_join.py:44 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filessafe_join(base_dir, "/etc/passwd")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈46 tok
1 file · 64 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for semgrep-mcp@0.9.0 as of 23 min ago. This is the package itself, not its dependencies.