Loading the registry…
A simple MCP server to render a cow saying whatevery you want. For educational purposes ;)
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 -- mcp-server-cowsay
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 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.
v1.4.0
0 findings · 0.6s
v2.0.11
3 findings · 8.6s
v0.3.74
5 findings · 1.1s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v0.71.0
11 findings · 0.3s
v2.3.8
11 findings · 8.4s
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.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 | Flagged51 | — | agentshield: completecisco-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 30 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 3 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 AAK-ANTHROPIC-SDK-001
Files: index.js · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-018
Files: index.js · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2025-13466
Files: package-lock.json · reported by trivy
1 CVE-2025-15284
Files: package-lock.json · reported by trivy
1 CVE-2025-66414
Files: package-lock.json · reported by trivy
1 CVE-2025-69873
Files: package-lock.json · reported by trivy
1 CVE-2026-0621
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-25536
Files: package-lock.json · reported by trivy
1 CVE-2026-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-4926
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-345p-7cg4-v4c7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8r9q-7v3j-jr4g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w48q-cv73-mx4w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
High-severity vulnerabilities found, including AI SDK and DNS rebinding risks.
The artifact includes an AI SDK in `index.js` that may transmit data to external services. A DNS rebinding vulnerability in `package.json` could enable access to internal network resources. Multiple high-severity supply chain vulnerabilities in `package-lock.json` also warrant attention.
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.