Loading the registry…
Production-ready MCP server for RAG operations with multimodal support
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.
1 critical finding reported by agent-audit-kit, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- rag-anything-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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
2 findings · 8.0s
v0.3.74
9 findings · 1.9s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 3.2s
v2.3.8
9 findings · 1.3s
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.9s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
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 21, 2026 | Flagged40 | — | 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 ·n/a: not applicableosv-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 20 findings across every scanner that examined this package. 1 of 1 finding rated critical by their scanner was among the dismissals.
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.
1 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-SECRET-002 · Files: tests/unit/test_utils.py · reported by agent-audit-kit
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.
2 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, requirements.txt · reported by agent-audit-kit
2 AAK-OAUTH-3P-001
Files: pyproject.toml, requirements.txt · reported by agent-audit-kit
1 AAK-ANTHROPIC-SDK-001
Files: main.py · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: pyproject.toml · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2024-40
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-107
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1616
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1618
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1812
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/requirements.txt · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
High-severity vulnerabilities in SDKs and dependencies require attention.
The artifact contains multiple high-severity vulnerabilities, including specific SDK issues in `main.py`, `pyproject.toml`, and `requirements.txt`. A potential DNS rebind vulnerability is present in `pyproject.toml`, which could facilitate network egress. Additionally, several high-severity Python security advisories are identified in the project's dependencies listed in `/repo/requirements.txt`, indicating potential risks such as remote code execution or data exposure. These findings collectively warrant careful review before deployment.
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.