| FMRS | 54 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 9 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 11 / 20 | 15 / 20 |
|---|
| Best for | - Teams seeking self-hosted multi-agent orchestration
- Engineering and operations teams that want a lead agent to coordinate specialized workers
- Organizations needing shared memory, persistent identity, workflows, or human approval gates
- Users able to manage Docker, API keys, and agent-harness credentials
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users who only need a single MCP tool or simple chat assistant
- Environments that cannot run Docker or manage agent-harness credentials
- Teams that do not want tasks to flow among multiple agents, shared memory, or external integrations
- Users requiring documented compatibility with a ready-made desktop client
| - 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 | - Access to the local or remote Agent Swarm MCP endpoint
- An Agent Swarm API key supplied through an Authorization header with the Bearer prefix
- The X-Agent-ID of a registered agent
- Depending on enabled integrations and harnesses, credentials for Slack, code hosting, email, Linear, Jira, or other services
| - 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 | - Worker agents execute tasks in isolated Docker environments but may access the code, files, and services configured for them
- Shared memory retains learnings across sessions and can broaden the context visible to later tasks
- Enabled integrations can cause messages, emails, ticket updates, code changes, or pull requests
- Misconfigured API keys, Bearer headers, or agent IDs can cause connection failures or access to the wrong agent instance
- Automated workflows and external actions should be reviewed with human approval gates, especially for irreversible operations
| - 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 | | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 0 | 19 |
|---|