Compare two AI tools side by side
Put any two skills or MCP servers next to each other: risk grade, what each can access, how popular it is, and how to install it.
| What | chrome-devtools-mcp | context7 |
|---|---|---|
| Risk grade | AA · Few risk signals Based on public adoption and transparency signals as of Oct 16, 2026. Our opinion, not a code audit or security guarantee. | AA · Few risk signals Based on public adoption and transparency signals as of Oct 16, 2026. Our opinion, not a code audit or security guarantee. |
| Type | App connector | App connector |
| Est. context load | ~3.8k tokens / turn (~22 tool schemas, 1.9% of 200k context) | ~480 tokens / turn (~2 tool schemas, 0.24% of 200k context) |
| GitHub stars | 54.4k | 63.9k |
| Weekly npm downloads | 3M | 478k |
| Local files | Reads & writes local folders | No local folder access noted |
| Command execution | Runs shell or system commands | Runs shell or system commands |
| Network reach | Fetches arbitrary web URLs | Local or standard API calls |
| Credentials | Requires API key or token | Requires API key or token |
| Package source | npm (chrome-devtools-mcp) | npm (@upstash/context7-mcp) |
| Install command | npx -y chrome-devtools-mcp | npx -y @upstash/context7-mcp |
| Bottom line | chrome-devtools-mcp (MCP server) requires careful permission scoping — credential exposure: Agents gain full access to Chrome DevTools, which may expose session cookies, auth tokens, and stored credentials to injected prompts or malicious agents. | context7 (MCP server) requires careful permission scoping — credential exposure: API keys for documentation sources must be securely managed; misconfiguration could leak access to private knowledge bases |
Based on public adoption and transparency signals as of Oct 28, 2026. Our opinion, not a code audit or security guarantee.
Go deeper
Want to inspect exact published files, install hooks and network hosts?
Run a pre-install check on any package, MCP config or SKILL.md, or open a full report with PDF export.