| FMRS | 64 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 14 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - AI agents and developers conducting evidence-first code research.
- Teams analyzing both local workspaces and GitHub repositories.
- Code review, refactoring, and architecture work requiring semantic navigation, structural search, and compact context.
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users seeking browser automation, cloud storage, collaboration, or database operations.
- Environments that cannot grant local workspace or GitHub access.
- Clients requiring a transport other than stdio.
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Local tools can access paths permitted by configuration; local tools are enabled by default.
- GitHub tools require GitHub authentication; personal access tokens support repo, read:user, and read:org scopes.
- When cloning is enabled, the server accesses GitHub repositories and uses a local cache.
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Local tools may read code and files within permitted paths; the server blocks many sensitive files and directories.
- GitHub tokens are sensitive credentials and should be supplied through environment variables or secure credential management, never committed to version control.
- Secret scanning and automatic redaction may reduce returned-content completeness.
- Enabling repository cloning expands local caching and external repository data handling.
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Cursor, VS Code, VS Code Insiders, Windsurf, Kiro, Goose, LM Studio, Claude Code | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 12 | 19 |
|---|