Loading the registry…
Open source self-hosted MCP server for project memory and context optimization
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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- snipara-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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.
v2.0.11
14 findings · 11.4s
v0.3.74
11 findings · 22.8s
v0.1.0
1 finding · 12.6s
v0.1.0
1 finding · 12.6s
v0.71.0
26 findings · 0.4s
v2.3.8
70 findings · 1.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.6s
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 22, 2026 | Flagged28 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: 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 123 findings across every scanner that examined this package.
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.
4 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: AAK-TASKS-003, AAK-OAUTH-005 · Files: tests/test_htask_task_adapter.py, tests/test_htask_coordinator.py, tests/test_htask_policy.py and 1 more · reported by agent-audit-kit
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/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.
3 GHSA-jm82-fx9c-mx94
Files: /repo/requirements-prod.txt, /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 AAK-MCP-NOAUTH-DEFAULT
Files: src/config.py, mcp-stdio-bridge/server.py · reported by agent-audit-kit
2 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/scripts/svg_context_builder.py · reported by cisco-skill-scanner
2 FILE_MAGIC_MISMATCH
Files: /repo/requirements-prod.txt, /repo/scripts/setup.sh · reported by cisco-skill-scanner
2 GHSA-4xgf-cpjx-pc3j
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/prisma/migrations/SKILL.md
The model could have called any of these a false positive and did not.
1 CVE-2026-54282
Files: uv.lock · reported by trivy
Artifact exhibits network egress, credential access, and unauthenticated access risks.
The artifact contains a hardcoded secret that could lead to network egress from `/repo/scripts/svg_context_builder.py` and exposes credentials in `src/services/agent_memory.py`. Unauthenticated access is possible via `mcp-stdio-bridge/server.py` and `src/config.py`. Additionally, the artifact includes components with known high-severity vulnerabilities that could lead to resource exhaustion in `/repo/src/mcp_transport.py` and `/repo/src/server.py`.
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.
2 PYSEC-2024-38
Files: /repo/requirements-prod.txt, /repo/requirements.txt · reported by osv-scanner
2 PYSEC-2026-1917
Files: /repo/requirements-prod.txt, /repo/requirements.txt · reported by osv-scanner
2 PYSEC-2026-3004
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3009
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3010
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3016
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3018
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3020
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3022
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3025
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3610
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3611
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3612
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3613
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3655
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3656
Files: /repo/requirements-prod.txt, /repo/uv.lock · reported by osv-scanner
2 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/src/mcp_transport.py, /repo/src/server.py · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/prisma/migrations/SKILL.md · reported by cisco-skill-scanner
1 AAK-ANTHROPIC-SDK-001
Files: mcp-stdio-bridge/server.py · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-OAUTH-008
Files: src/mcp_transport.py · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/services/agent_memory.py · reported by agent-audit-kit
1 AAK-TASKS-003
Files: src/models/requests.py · reported by agent-audit-kit
1 CVE-2025-3000
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-44432
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-48155
Files: uv.lock · reported by trivy
1 CVE-2026-48156
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48735
Files: uv.lock · reported by trivy
1 CVE-2026-48817
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-49460
Files: uv.lock · reported by trivy
1 CVE-2026-49461
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-54530
Files: uv.lock · reported by trivy
1 CVE-2026-54531
Files: uv.lock · reported by trivy
1 CVE-2026-54651
Files: uv.lock · reported by trivy
1 CVE-2026-59890
Files: uv.lock · reported by trivy
1 CVE-2026-59935
Files: uv.lock · reported by trivy
1 CVE-2026-59936
Files: uv.lock · reported by trivy
1 CVE-2026-59937
Files: uv.lock · reported by trivy
1 CVE-2026-59938
Files: uv.lock · reported by trivy
1 CVE-2026-71852
Files: uv.lock · reported by trivy
1 CVE-2026-71870
Files: uv.lock · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-rrmf-rvhw-rf47
Files: /repo/uv.lock · reported by osv-scanner
1 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/prisma/migrations/README.md · reported by nerlo-install-instruction
1 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/scripts/svg_context_builder.py · reported by nerlo-behavioral
1 PYSEC-2026-139
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-142
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1827
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-1828
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-1829
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-1830
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-1831
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-1832
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-1833
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3005
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3006
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3007
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3011
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3012
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3013
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3014
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3015
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3017
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3019
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3021
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3023
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3024
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3026
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3027
Files: /repo/requirements-prod.txt · reported by osv-scanner
1 PYSEC-2026-3447
Files: /repo/uv.lock · reported by osv-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/CODE_OF_CONDUCT.md · reported by cisco-skill-scanner
Showing 25 of 26; the rest are in the per-scanner reports above.