Is GitKraken MCP server safe?
What GitKraken MCP server does
@gitkraken/gk is GitKraken's command-line tool; its npm README documents the GitKraken MCP Server it provides (gk mcp), with Git operations such as add, commit, checkout, stash and push, plus issues and pull requests across GitHub, GitLab, Bitbucket, Azure DevOps, Jira and other integrations. The npm author field lists Gitkraken. It runs Git commands on local repositories, calls connected services through your GitKraken integrations, and the package runs a postinstall script (node install.js). Before installing, review that postinstall step and which integrations are connected, since the tools include git_push and pull request creation.
- Node.js shell/command execution
- npm install-time lifecycle hook
- Node.js filesystem read
What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.
GitKraken MCP server is an MCP server analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: filesystem read, filesystem write, install time execution, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
@gitkraken/ gk 3.1.77
Get notified when this component changes
Change alerts aren't live yet. Leave your email and we'll let you know when they launch. We use it only for this and delete it on request.
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of GitKraken MCP server's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (5)
package.json runs scripts automatically when the package is installed.
"postinstall": "node install.js",
Why it matters: Install scripts are a favorite supply-chain foothold — they execute on every machine that installs the package.
Fix: Inspect the hook command. Install-time scripts are a common supply chain execution vector; ensure they do nothing beyond a documented build step.
The component can run operating-system commands or spawn processes.
import { spawnSync } from "child_process";let result = spawnSync(path.join(binDir, bin), args, {Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.
Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; prefer execFile with an argument array.
The component reads files from disk.
fs.readFileSync(new URL("./package.json", import.meta.url), "utf8"),const zipData = fs.readFileSync(zipPath);
.update(fs.readFileSync(filename))
Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.
Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.
The component writes or deletes files on disk.
fs.rmSync(wrappedDir, { recursive: true, force: true });fs.writeFileSync(file, content);
const writer = fs.createWriteStream(filename);
Why it matters: Usually legitimate, but worth confirming the paths can't be controlled by untrusted input.
Fix: Confirm which files are written/deleted and that paths cannot be influenced by untrusted input.
The component makes outbound network requests.
Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.
Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.
How attackers abuse these capabilities
Interactive labs on the attack class behind the rules above. They show the technique, not anything found in GitKraken MCP server.
Maintain GitKraken MCP server?
The free Claude Code plugin scans each npm, PyPI or MCP package with this report's open-source engine before the install command runs. It runs on your machine and needs no account.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →