Loading the registry…
A Model Context Protocol server for Datadog API integration
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-datadog
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
3 findings · 6.8s
v0.3.74
10 findings · 1.4s
v0.1.0
0 findings · 3.1s
v0.71.0
16 findings · 0.2s
v2.3.8
0 findings · 0.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.1s
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.1s
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 | Flagged74 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-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 29 findings across every scanner that examined this package.
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.
9 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/ci.yml, .github/workflows/lint.yml · 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.
1 AAK-SUPPLY-005
Files: Cargo.lock · reported by agent-audit-kit
1 CVE-2026-25541
Files: Cargo.lock · reported by trivy
1 CVE-2026-31812
Files: Cargo.lock · reported by trivy
1 CVE-2026-41676
Files: Cargo.lock · reported by trivy
1 CVE-2026-41677
Files: Cargo.lock · reported by trivy
1 CVE-2026-41678
Files: Cargo.lock · reported by trivy
1 CVE-2026-41681
Files: Cargo.lock · reported by trivy
1 CVE-2026-41898
Files:
The model could have called any of these a false positive and did not.
1 GHSA-4w2j-m93h-cj5j
Files: Cargo.lock · reported by trivy
1 GHSA-xgp8-3hg3-c2mh
Files: Cargo.lock · reported by trivy
Multiple high-severity vulnerabilities identified in dependencies.
The artifact includes dependencies with several high-severity vulnerabilities, primarily identified in the `Cargo.lock` file. These vulnerabilities could potentially lead to various security risks depending on the specific CVEs, such as remote code execution, denial of service, or information disclosure. Reviewing these specific vulnerabilities and their potential impact on the artifact's functionality is recommended 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.
1 CVE-2026-42327
Files: Cargo.lock · reported by trivy
1 CVE-2026-44662
Files: Cargo.lock · reported by trivy
1 CVE-2026-45784
Files: Cargo.lock · reported by trivy
1 GHSA-82j2-j2ch-gfr8
Files: Cargo.lock · reported by trivy
1 GHSA-965h-392x-2mh5
Files: Cargo.lock · reported by trivy
1 GHSA-cq8v-f236-94qc
Files: Cargo.lock · reported by trivy
1 GHSA-pwjx-qhcg-rvj4
Files: Cargo.lock · reported by trivy
1 HIDDEN_DATA_FILE
Files: /repo/.codecov.yml · 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