SkillTotal

Is Context7 MCP server safe?

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

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

@upstash/context7-mcp 4.1.1

npm_package · npm:@upstash/context7-mcp
LOW
0
/ 100 risk score
Snapshot · scanned Sep 24, 2026 · @upstash/context7-mcp@4.1.1 · 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 Context7 MCP server's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
mcp 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

Findings (2)

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

dist/index.js:442-442 
const upstream = await observeUpstreamRequest("oauth_metadata", () => fetch(`${authServerUrl}/.well-known/oauth-authorization-server`, {
dist/lib/api.js:111-111 
return await observeUpstreamRequest("search_libraries", () => fetch(url, { headers, signal: abortSignal }), async (response) => {
dist/lib/api.js:141-141 
return await observeUpstreamRequest("fetch_context", () => fetch(url, { headers, signal: abortSignal }), async (response) => {
dist/lib/jwt.js:24-24 
const res = await fetch(`${CONTEXT7_API_BASE_URL}/v2/entra/config/${encodeURIComponent(audience)}`);
dist/lib/mcp-subscription-telemetry.js:403-403 
return handler.fetch(request, options);
dist/lib/mcp-subscription-telemetry.js:417-417 
const response = await operation.run(() => handler.fetch(request, options));

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.

dist/index.js:154-154 
: new McpServer(serverInfo, serverOptions);
dist/index.js:155-155 
server.registerTool(RESOLVE_LIBRARY_ID_TOOL, {
dist/index.js:233-233 
server.registerTool(QUERY_DOCS_TOOL, {

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 →