Is GitMCP safe?
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, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
git-mcp 1.0.0
- Node.js shell/command execution
- Node.js network egress
- npm prepare hook
No malicious indicators found by static analysis.
Findings (3)
The component can run operating-system commands or spawn processes.
const match = /language-(\w+)/.exec(className || "");
exec(input?: (string | URLPatternInit), baseURL?: string): URLPatternResult | null;
exec(query: string): Promise<D1ExecResult>;
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.
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.
The component makes outbound network requests.
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.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentOr get notified if this component's risk changes:
How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →