| FMRS | 61 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 |
|---|
| Maintenance | 10 / 20 | 18 / 20 |
|---|
| Documentation | 16 / 20 | 18 / 20 |
|---|
| Setup experience | 13 / 20 | 15 / 20 |
|---|
| Best for | - Pi coding-agent users who want lower MCP context overhead
- Developers who need access to multiple MCP ecosystem services
- Users who want lazy connections, metadata caching, or optional direct tool registration
| - 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 do not use Pi
- Workflows requiring server-process sharing across Pi sessions
- MCP sampling workflows requiring context inclusion, tools, stop sequences, audio, or image content
| - 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 | - Read and write Pi MCP configuration, tool metadata caches, and OAuth credential directories
- Start configured local MCP processes and access their working directories
- Access configured HTTP MCP endpoints, headers, environment variables, and OAuth credentials
- Depending on the configured MCP servers, access files, browsers, databases, APIs, or other external resources
| - 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 | - Configured MCP servers may receive the file, network, database, or API access required by their configuration and use
- OAuth authorization URLs, codes, and tokens are sensitive credentials
- Oversized text results may be written to the system temporary directory and are not cleaned up automatically
- Review imported host configurations and their permission scope before relying on them
| - 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 | Pi | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 1 | 19 |
|---|