Loading the registry…
Minimal MCP server for the Notion private (internal) API
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.
npm: notion-private-mcp @ 0.2.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- notion-private-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.7s
v2.0.11
5 findings · 7.8s
v0.3.74
4 findings · 1.3s
v0.1.0
1 finding · 4.0s
v0.1.0
4 findings · 4.0s
v0.1.0
0 findings · 7.8s
v0.71.0
31 findings · 0.2s
v2.3.8
31 findings · 7.0s
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
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged44 | — | 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 |
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 76 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 11 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
2 GHSA-frvp-7c67-39w9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/server.js · reported by agent-audit-kit
1 AAK-MCP-018
Files: src/server.js · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-13676
Files: package-lock.json · reported by trivy
1 CVE-2026-16221
Files: package-lock.json · reported by trivy
1 CVE-2026-18446
Files: package-lock.json · reported by trivy
1 CVE-2026-42338
Files: package-lock.json · reported by trivy
1 CVE-2026-44455
Files: package-lock.json · reported by trivy
1 CVE-2026-44456
Files: package-lock.json · reported by trivy
1 CVE-2026-44457
Files: package-lock.json · reported by trivy
1 CVE-2026-44458
Files: package-lock.json · reported by trivy
1 CVE-2026-44459
Files: package-lock.json · reported by trivy
1 CVE-2026-47673
Files: package-lock.json · reported by trivy
1 CVE-2026-47674
Files: package-lock.json · reported by trivy
1 CVE-2026-47675
Files: package-lock.json · reported by trivy
1 CVE-2026-47676
Files: package-lock.json · reported by trivy
1 CVE-2026-54286
Files: package-lock.json · reported by trivy
1 CVE-2026-54287
Files: package-lock.json · reported by trivy
1 CVE-2026-54288
Files: package-lock.json · reported by trivy
1 CVE-2026-54289
Files: package-lock.json · reported by trivy
1 CVE-2026-54290
Files: package-lock.json · reported by trivy
1 CVE-2026-59895
Files: package-lock.json · reported by trivy
1 CVE-2026-59896
Files: package-lock.json · reported by trivy
1 CVE-2026-59897
Files: package-lock.json · reported by trivy
1 CVE-2026-6321
Files: package-lock.json · reported by trivy
1 CVE-2026-6322
Files: package-lock.json · reported by trivy
1 CVE-2026-69192
Files: package-lock.json · reported by trivy
1 CVE-2026-69207
Files: package-lock.json · reported by trivy
1 CVE-2026-71848
Files: package-lock.json · reported by trivy
1 CVE-2026-71849
Files: package-lock.json · reported by trivy
1 CVE-2026-71850
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-2gcr-mfcq-wcc3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3hrh-pfw6-9m5x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-69xw-7hcm-h432
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-88fw-hqm2-52qc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9vqf-7f2p-gf9v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f577-qrjj-4474
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hm8q-7f3q-5f36
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hvrm-45r6-mjfj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j6c9-x7qj-28xf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mwp4-54f8-5fhr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p77w-8qqv-26rm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q3j6-qgpj-74h6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qp7p-654g-cw7p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rv63-4mwf-qqc2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v2v4-37r5-5v8g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v39h-62p7-jpjc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w62v-xxxg-mg59
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wgpf-jwqj-8h8p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wwfh-h76j-fc44
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xgm2-5f3f-mvvc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xrhx-7g5j-rcj5
Files: /repo/package-lock.json · reported by osv-scanner
1 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/notion-client.js · reported by nerlo-behavioral
10 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, opt.nerlo-rules.nerlo-install-run-bundled-artifact, SOCIAL_ENG_VAGUE_DESCRIPTION and 4 more · Files: SECURITY.md, /repo/CHANGELOG.md, /repo/README.md and 4 more · reported by agent-audit-kit, nerlo-install-instruction, cisco-skill-scanner
1 The model did not answer for these findings.
Rules: GHSA-v422-hmwv-36x6 · Files: /repo/package-lock.json · reported by osv-scanner
High-severity vulnerabilities and secret network egress detected.
The artifact contains multiple high-severity vulnerabilities in its dependencies, identified in `package-lock.json`. It also exhibits a capability for secrets to be sent over network egress from `src/notion-client.js`. Further high-severity findings include the use of an Anthropic SDK in `src/server.js` and another finding in the same file.
Concern level assessed by the review: High. 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.