A command line tool for setting up Rember MCP server
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
3 critical findings reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
npm: @getrember/mcp @ 1.1.3, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @getrember/mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
16 findings · 6.5s
v0.3.74
4 findings · 2.4s
v0.2.0
1 finding · 3.7s
v0.2.0
3 findings · 3.7s
v0.1.0
0 findings · 9.0s
v0.71.0
38 findings · 0.3s
v2.3.8
107 findings · 6.9s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
7 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 11, 2026 | Flagged38 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Jul 30, 2026 | Flagged33 | — | cisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable | completed |
| Jul 21, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completetrivy: completeosv-scanner: complete | rejected |
| Jul 20, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completetrivy: completeosv-scanner: complete | rejected |
| Jul 20, 2026 | Scan Halted | Clean → Flagged | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completetrivy: completeosv-scanner: complete | rejected |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
| Jul 20, 2026 | Clean100 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-audit-kit: completetrivy: completeosv-scanner ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 169 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
3 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: LOW_ANALYZABILITY, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/src/test, /repo/src/test/SKILL.md · reported by cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
5 YARA_prompt_injection_unicode_steganography
Files: /repo/assets/what-is-active-recall.gif · reported by cisco-skill-scanner
2 CVE-2025-15284
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-2391
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-82417
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-8723
Files: pnpm-lock.yaml · reported by trivy
2 FILE_MAGIC_MISMATCH
Files: /repo/context/mcp-docs.txt, /repo/context/mcp-readme-typescript-sdk.txt · reported by cisco-skill-scanner
2 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-11525
Files: pnpm-lock.yaml · reported by trivy
Critical vulnerabilities found in dependencies
Multiple critical vulnerabilities are present in the artifact's dependencies, which could lead to remote code execution or denial of service. Additionally, high-severity findings indicate potential DNS rebinding risks and the use of an Anthropic SDK. The DNS rebinding risk could enable network egress to internal services, while the SDK use implies network egress for API calls and potential credential handling in `src/server-mcp.ts`.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4mjr-xmp4-gh2g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6rw7-vpxm-498p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-82fw-gwwq-j7x9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh29-5h37-fv8m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8mj-m7cp-5q26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w7fw-mjwx-w883
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/server-mcp.ts · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 CVE-2025-66414
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-0621
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12151
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13697
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-15157
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1525
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1526
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1527
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-1528
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16728
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16729
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22036
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2229
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-32887
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33532
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33671
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33672
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41907
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45736
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48779
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4923
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4926
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-63376
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6733
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-77465
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-9678
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-9679
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-27v5-c462-wpq7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-356w-63v5-8wf4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-35p6-xmwp-9g52
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-37ch-88jc-xwx2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-38f7-945m-qr2g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-395f-4hp3-45gv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-48c2-rrv3-qjmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4cwx-7wf7-3272
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4r4m-qw57-chr8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-73rr-hh4g-fpgx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-73wf-gq98-2v4g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7f8r-222p-6f5g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-82x6-q7mm-w9cf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-859w-5945-r5v3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8xcm-r25x-g524
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-93m4-6634-74q7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-96hv-2xvq-fx4p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c83g-rgw3-j3cx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f269-vfmq-vjvj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g9hg-qhmf-q45m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jr45-8vmc-qm54
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p498-v437-472g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pr7r-676h-xcf6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v5mp-jgw5-2x6j
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v9p9-hfj2-hcw8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vrm6-8vpv-qv8q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w5hq-g745-h8pq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7jw-789q-3m8p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x574-m823-4x7w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xcj6-pq6g-qj4x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xffm-g5w8-qvg7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xwg4-73v4-xw9w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-install-pipe-to-shell
Files: /repo/context/mcp-docs.txt · reported by nerlo-install-instruction
1 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/context/mcp-docs.txt · reported by nerlo-install-instruction
1 opt.nerlo-rules.nerlo-install-shell-inline-command
Files: /repo/context/mcp-docs.txt · reported by nerlo-install-instruction
1 opt.nerlo-rules.nerlo-js-websocket-unauthenticated
Files: /repo/src/server-mcp.ts · reported by nerlo-behavioral
1 OVERSIZED_FILE
Files: /repo/assets/what-is-active-recall.gif · reported by cisco-skill-scanner
1 PIPELINE_TAINT_FLOW
Files: /repo/context/mcp-docs.txt · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 YARA_capability_inflation_generic
Files: /repo/context/mcp-docs.txt · reported by cisco-skill-scanner
Showing 25 of 70; the rest are in the per-scanner reports above.