SkillTotal

Is GitMCP safe?

No malicious indicators - review capabilities before installing
Notable — review in context (capabilities are not malware):
  • Node.js network egress
  • npm prepare hook
  • MCP tool surface detected

git-mcp is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 3 risky constructs are reported for review. It can: install time execution, mcp tools detected and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

git-mcp 1.0.0

npm_package · https://github.com/idosal/git-mcp
LOW
0
/ 100 risk score
Snapshot · scanned Sep 24, 2026 · git-mcp@1.0.0 · engine 0.53.0 / ruleset 60

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of GitMCP's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
install time executionmcp tools detectednetwork egress

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Tool surface
Tool Usage
Network egress
Interaction & Communication / Direct Communication
Supply-chain provenance risk
General Protections / Supply Chain

Findings (3)

MEDIUMnpm prepare hookST-INSTALL-NPM-PREPARE

package.json has a 'prepare' script (runs on git/local installs and before publishing).

"prepare": "husky"

Why it matters: Usually a build step, but confirm it doesn't fetch or run remote code.

Fix: Usually a legitimate build step; confirm it only builds and does not fetch or execute remote code.

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

const response = await fetch(url);
const response = await fetch(searchUrl, {
const response = await fetch(url, {
const response = await fetch(url, {
const response = await fetch(url);
const response = await fetch(robotsTxtUrl);
async fetch(request: Request, env: any, ctx: any) {
return await MyMCP.serve("/*").fetch(request, env, ctx);
const res = await env.ASSETS.fetch(`${origin}/README.md`);
fetch(input: RequestInfo | URL, init?: RequestInit<RequestInitCfProperties>): Promise<Response>;
declare function fetch(input: RequestInfo | URL, init?: RequestInit<RequestInitCfProperties>): Promise<Response>;
fetch(request: Request): Response | Promise<Response>;
fetch(input: RequestInfo | URL, init?: RequestInit): Promise<Response>;

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.

LOWMCP tool surface detectedST-MCP-DETECTED

An MCP tool surface (manifest or tool definitions) was found.

const mcp = new McpServer({
mcp.tool("fetch_documentation", "Fetch documentation for a repository (URL will be provided when called).", {
mcp.tool("search_documentation", "Search documentation for a repository (URL will be provided when called).", {
server = new McpServer({

Why it matters: Just context — review which tools it offers and their permissions.

Fix: Review the declared MCP tools and their permissions.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →