pinkpixel-dev
6 MCP servers associated with this publisher in public records · generated 2026-09-22T12:17:45.454Z
incomplete 6 Findings medium 2
Records
| Server | Verdict | Package | Findings |
|---|---|---|---|
| ai.smithery/pinkpixel-dev-web-scout-mcp | incomplete | — | 0 finding(s) |
| github.com/pinkpixel-dev/deep-research-mcp | incomplete | @pinkpixel/deep-research-mcp@1.3.3 | 0 finding(s) |
| github.com/pinkpixel-dev/mcpollinations | incomplete | @pinkpixel/mcpollinations@1.3.1 | 1 finding(s), 1 above info |
| github.com/pinkpixel-dev/mem0-mcp | incomplete | @pinkpixel/mem0-mcp@0.8.0 | 1 finding(s), 1 above info |
| github.com/pinkpixel-dev/notification-mcp | incomplete | @pinkpixel/notification-mcp@0.2.0 | 0 finding(s) |
| github.com/pinkpixel-dev/npm-helper-mcp | incomplete | @pinkpixel/npm-helper-mcp@2.0.5 | 0 finding(s) |
Scope
Data comes from public registry entries and manifests of packages that were actually published. Each row opens a standalone evidence page.
Repository source is outside this index’s scan scope. Run the CLI locally for source scanning.
A finding is a matched shape, not a conclusion. It does not prove exploitability. Unmeasured work is listed on each server page and is never treated as clean.