Loading the registry…
Demo 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.
12 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 -- demo-mcp-github
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.1s
v0.3.74
14 findings · 1.5s
v0.1.0
0 findings · 3.4s
v0.1.0
0 findings · 3.4s
v0.71.0
106 findings · 0.3s
v2.3.8
112 findings · 1.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 · 2.0s
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 | Flagged30 | — | 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 240 findings across every scanner that examined this package. None of the 12 findings rated critical by their scanner were dismissed.
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.
4 GHSA-4gg8-gxpx-9rph
Files: requirements.txt, uv.lock, /repo/requirements.txt and 1 more · reported by trivy, osv-scanner
4 GHSA-4xgf-cpjx-pc3j
Files: /repo/requirements.txt, /repo/uv.lock, requirements.txt and 1 more · reported by osv-scanner, trivy
4 GHSA-537c-gmf6-5ccf
Files: requirements.txt, uv.lock, /repo/requirements.txt and 1 more · reported by trivy, osv-scanner
4 GHSA-pjjw-68hj-v9mw
Files: /repo/requirements.txt, /repo/uv.lock, requirements.txt and 1 more · reported by osv-scanner, trivy
4 GHSA-rcfx-77hg-w2wv
Files: requirements.txt, uv.lock, /repo/requirements.txt and 1 more · reported by trivy, osv-scanner
3 AAK-ANTHROPIC-SDK-001
Files: mcp_client.py, mcp_client_ref_servers.py, mcp_client_adding_prompt_resource_features.py · reported by agent-audit-kit
3 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock, requirements.txt · reported by agent-audit-kit
3 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/mcp_client.py, /repo/mcp_client_adding_prompt_resource_features.py, /repo/mcp_client_ref_servers.py · reported by cisco-skill-scanner
2 AAK-DNS-REBIND-002
Files: requirements.txt, pyproject.toml · reported by agent-audit-kit
2 AAK-OAUTH-3P-001
Files: pyproject.toml, requirements.txt · reported by agent-audit-kit
2 CVE-2025-64340
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-66416
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-66418
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-66471
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-68158
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-69196
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2025-69872
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-21441
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-24486
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-25645
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-26007
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-27124
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-27962
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28490
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28498
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28684
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-28802
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-32597
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-32871
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-34073
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-39892
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-40347
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-41425
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-41479
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-42561
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-44431
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-44681
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-4539
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-45409
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48522
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48523
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48524
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48525
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48526
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48710
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48817
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-48818
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-52869
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-53537
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-53538
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-53539
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-53540
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-54283
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-59950
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-69247
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-69249
Files: requirements.txt, uv.lock · reported by trivy
2 PYSEC-2025-183
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-120
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1201
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-141
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1469
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-161
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1617
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-175
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-176
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-177
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-178
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-179
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1852
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-188
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1994
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1996
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1998
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2116
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2117
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2118
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2119
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2132
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2141
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-215
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2270
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2275
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2280
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2281
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2447
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2474
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2475
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2476
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-248
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-249
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-25
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-287
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2987
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3036
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3037
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3038
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3039
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3040
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3041
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-338
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3482
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3483
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-35
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3552
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3553
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-3554
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-36
Files: /repo/requirements.txt, /repo/uv.lock · reported by osv-scanner
1 AAK-MCP-HTTP-NOAUTH-SERVER-001
Files: mcp_server.py · reported by agent-audit-kit
1 AAK-MCP-SSRF-001
Files: mcp_client_adding_prompt_resource_features.py · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SECRET-006
Files: .env.example · reported by agent-audit-kit
1 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/check_server.py · reported by cisco-skill-scanner
1 FILE_MAGIC_MISMATCH
Files: /repo/requirements.txt · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 CVE-2026-54282
Files: requirements.txt, uv.lock · reported by trivy
2 CVE-2026-69248
Files: requirements.txt, uv.lock · reported by trivy
Critical vulnerabilities and unauthenticated network services detected.
The artifact contains critical vulnerabilities in its dependencies, as identified in `requirements.txt` and `uv.lock`, which could lead to various exploits. An unauthenticated HTTP server is present in `mcp_server.py`, posing a risk of unauthorized network access and data exposure. Additionally, the artifact includes code that may lead to resource abuse or infinite loops in `mcp_client.py` and related files.
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 25 of 122; the rest are in the per-scanner reports above.