Loading the registry…
Model Context Protocol server for Textual TUI framework with vector search
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.
9 critical findings reported by trivy, osv-scanner. 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 -- textual-mcp-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
8 findings · 7.5s
v0.3.74
2 findings · 4.4s
v0.1.0
0 findings · 3.5s
v0.1.0
1 finding · 3.5s
v0.71.0
96 findings · 0.4s
v2.3.8
112 findings · 2.5s
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.8s
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 | Flagged41 | — | 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 219 findings across every scanner that examined this package. None of the 9 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 185 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.
1 CVE-2025-2999
Files: uv.lock · reported by trivy
1 CVE-2025-3730
Files: uv.lock · reported by trivy
1 CVE-2025-62800
Files: uv.lock · reported by trivy
1 CVE-2025-64340
Files: uv.lock · reported by trivy
1 CVE-2026-21860
Files: uv.lock · reported by trivy
1 CVE-2026-22701
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-27199
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-40347
Files: uv.lock · reported by trivy
1 CVE-2026-41425
Files: uv.lock · reported by trivy
1 CVE-2026-42308
Files: uv.lock · reported by trivy
1 CVE-2026-42309
Files: uv.lock · reported by trivy
1 CVE-2026-42310
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-59198
Files: uv.lock · reported by trivy
1 CVE-2026-9335
Files: uv.lock · reported by trivy
1 PYSEC-2026-1201
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1202
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1365
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1374
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-188
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1970
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2119
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2251
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2320
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2475
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner
124 The model's answer could not be read.
Rules: PYSEC-2026-36, PYSEC-2026-1486, PYSEC-2026-338 and 119 more · Files: /repo/uv.lock, uv.lock, /repo/README.md · reported by osv-scanner, trivy, agent-audit-kit and 1 more
60 The review budget for this scan was already spent before these findings were reached.
Rules: CVE-2026-48817, PYSEC-2026-1375, PYSEC-2026-2046 and 54 more · Files: uv.lock, /repo/uv.lock, /repo/README.md and 4 more · reported by trivy, osv-scanner, cisco-skill-scanner and 1 more
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK · Files: /repo/repo/README.md · reported by cisco-skill-scanner
Critical vulnerabilities and potential code execution risks identified.
The artifact contains multiple critical vulnerabilities in its dependencies, primarily identified in `uv.lock` files. Additionally, several high-severity findings from the 'bearer' scanner indicate potential risks within the installed code, including in `src/textual_mcp/config.py` and `src/textual_mcp/tools/documentation_tools.py`. One high-severity finding from 'nerlo-install-instruction' points to a 'pipe-to-shell' pattern in `README.md`, which could lead to shell execution if installation instructions are followed directly.
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.
Showing 18 of 18; the rest are in the per-scanner reports above.