A template for Model Context Protocol (MCP) server development
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.
8 critical findings reported by agent-audit-kit, trivy, osv-scanner, 7 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 -- openshift-partner-labs-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
41 findings · 10.8s
v0.3.74
30 findings · 5.6s
v0.1.0
1 finding · 4.9s
v0.1.0
0 findings · 4.9s
v0.71.0
76 findings · 0.4s
v2.3.8
77 findings · 1.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.3s
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 19, 2026 | Flagged29 | — | 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 225 findings across every scanner that examined this package. 1 of 8 findings rated critical by their scanner was among the dismissals.
Not reviewed is not the same as clean. Those 87 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
5 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-OAUTH-004, AAK-OAUTH-006 · Files: tests/test_oauth_handler.py, tests/test_oauth_controller.py, tests/test_storage_service.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: AAK-DNS-REBIND-001, AAK-SSRF-002 · Files: examples/langgraph_client.py, examples/fastmcp_client.py · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
2 GHSA-c2jp-c369-7pvx
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-f4xh-w4cj-qxq8
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 SECRET_CONNECTION_STRING
Files: /repo/openshift_partner_labs_mcp_server/src/storage/storage_service.py · reported by cisco-skill-scanner
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-OAUTH-001
Files: openshift_partner_labs_mcp_server/src/api.py · reported by agent-audit-kit
1 AAK-OAUTH-005
Files: openshift_partner_labs_mcp_server/src/oauth/handler.py · reported by agent-audit-kit
1
52 The review call did not complete.
Rules: PYSEC-2026-1852, CVE-2026-42561, CVE-2026-21441 and 19 more · Files: /repo/uv.lock, uv.lock, /repo/tests/test_oauth_controller.py and 16 more · reported by osv-scanner, trivy, cisco-skill-scanner and 1 more
34 The review budget for this scan was already spent before these findings were reached.
Rules: PYSEC-2026-2987, PYSEC-2026-3040, HIDDEN_DATA_FILE and 14 more · Files: /repo/uv.lock, /repo/.gitlab-ci.yml, uv.lock and 11 more · reported by osv-scanner, cisco-skill-scanner, trivy
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001 · Files: SECURITY.md · reported by agent-audit-kit
Critical vulnerabilities and exposed connection strings found.
The artifact includes dependencies with critical vulnerabilities that could enable remote code execution or data compromise. It exposes connection strings in `openshift_partner_labs_mcp_server/src/storage/storage_service.py` and has a high-severity finding for potential secret exfiltration via network egress from `openshift_partner_labs_mcp_server/src/oauth/handler.py`. Further high-severity findings point to OAuth configuration issues in `openshift_partner_labs_mcp_server/src/api.py` and Splunk token logging in `openshift_partner_labs_mcp_server/src/oauth/controller.py`.
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.
Files: openshift_partner_labs_mcp_server/src/oauth/controller.py · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: openshift_partner_labs_mcp_server/src/oauth/controller.py · reported by agent-audit-kit
1 CVE-2025-54121
Files: uv.lock · reported by trivy
1 CVE-2025-61920
Files: uv.lock · reported by trivy
1 CVE-2025-62706
Files: uv.lock · reported by trivy
1 CVE-2025-62727
Files: uv.lock · reported by trivy
1 CVE-2025-62800
Files: uv.lock · reported by trivy
1 CVE-2025-62801
Files: uv.lock · reported by trivy
1 CVE-2025-64340
Files: uv.lock · reported by trivy
1 CVE-2025-64439
Files: uv.lock · reported by trivy
1 CVE-2025-65106
Files: uv.lock · reported by trivy
1 CVE-2025-66416
Files: uv.lock · reported by trivy
1 CVE-2025-66418
Files: uv.lock · reported by trivy
1 CVE-2025-67221
Files: uv.lock · reported by trivy
1 CVE-2025-68146
Files: uv.lock · reported by trivy
1 CVE-2025-68158
Files: uv.lock · reported by trivy
1 CVE-2025-68664
Files: uv.lock · reported by trivy
1 CVE-2025-69196
Files: uv.lock · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-0994
Files: uv.lock · reported by trivy
1 CVE-2026-22701
Files: uv.lock · reported by trivy
1 CVE-2026-22702
Files: uv.lock · reported by trivy
1 CVE-2026-23490
Files: uv.lock · reported by trivy
1 CVE-2026-24486
Files: uv.lock · reported by trivy
1 CVE-2026-25528
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-27124
Files: uv.lock · reported by trivy
1 CVE-2026-27794
Files: uv.lock · reported by trivy
1 CVE-2026-27962
Files: uv.lock · reported by trivy
1 CVE-2026-28277
Files: uv.lock · reported by trivy
1 CVE-2026-28490
Files: uv.lock · reported by trivy
1 CVE-2026-28498
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-30922
Files: uv.lock · reported by trivy
1 CVE-2026-32871
Files: uv.lock · reported by trivy
1 CVE-2026-34070
Files: uv.lock · reported by trivy
1 CVE-2026-39892
Files: uv.lock · reported by trivy
1 CVE-2026-40087
Files: uv.lock · reported by trivy
1 CVE-2026-40347
Files: uv.lock · reported by trivy
1 CVE-2026-41182
Files: uv.lock · reported by trivy
1 CVE-2026-41425
Files: uv.lock · reported by trivy
1 CVE-2026-41479
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-44681
Files: uv.lock · reported by trivy
1 CVE-2026-44843
Files: uv.lock · reported by trivy
1 CVE-2026-45134
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48775
Files: uv.lock · reported by trivy
1 CVE-2026-48776
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-52869
Files: uv.lock · reported by trivy
1 CVE-2026-53539
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-59884
Files: uv.lock · reported by trivy
1 CVE-2026-59885
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-69247
Files: uv.lock · reported by trivy
1 CVE-2026-69248
Files: uv.lock · reported by trivy
1 GHSA-537c-gmf6-5ccf
Files: uv.lock · reported by trivy
1 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/openshift_partner_labs_mcp_server/src/oauth/handler.py · reported by nerlo-behavioral
1 PYSEC-2026-107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1200
Files: /repo/uv.lock · reported by osv-scanner
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-1203
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1364
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-1375
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1518
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1527
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1805
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1810
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-188
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1941
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2009
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2116
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2117
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2119
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2193
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2263
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
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-2474
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2475
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-25
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2563
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2564
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2573
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2574
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2575
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2584
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-338
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3457
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-373
Files: /repo/uv.lock · reported by osv-scanner
Showing 25 of 90; the rest are in the per-scanner reports above.