npm analyzed 1.1.7

gemini-mcp-tool

v1.1.7
npm

MCP server for Gemini CLI integration

maintainer
filecrop
license
MIT
first seen
2026-05-22
last seen
2026-06-11
releases · 30d
7
short id
risk58/100 · heuristic grade
C elevated
  • vulnerabilitiesattested+35
  • capability exposureinferred+16
  • inherited (deps)attested+15
  • trust mitigatorsmixed−8

attestedinferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 12m ago · see ecosystem CVEs →

risk trajectory2 movements
  • D · 77C · 58
  • D · 62D · 77
capability exposuregrade factor +16
Inferred surface — each links to servers holding it:
vulnerabilities1 CVEs · grade factor +35
CRITICAL
OS command injection and @file exfiltration via prompt quoting (CVE-2026-0755) EPSS 1% CVE-2026-0755 affects [">= 1.1.2, < 1.1.6"]

inherited (deps) · grade factor +15

inherited via dependencies4
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @modelcontextprotocol/sdk · 1 hop CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @modelcontextprotocol/sdk · 1 hop CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @modelcontextprotocol/sdk · 1 hop CVE-2025-66414 fixed in 1.24.0
LOW
Vercel’s AI SDK's filetype whitelists can be bypassed when uploading files via ai · 1 hop CVE-2025-48985 fixed in 5.0.52
tool safetyall quiet

No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.

embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/github:jamubc/gemini-mcp-tool/badge.svg)](https://mcpobservatory.com/servers/github:jamubc/gemini-mcp-tool/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of filecrop.