Loading the registry…
Meraki MCP Server for Cisco Meraki Dashboard API
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.
6 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 -- meraki-mcp
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 · 8.3s
v0.3.74
8 findings · 3.1s
v0.1.0
0 findings · 3.9s
v0.1.0
0 findings · 3.9s
v0.71.0
86 findings · 0.3s
v2.3.8
108 findings · 1.6s
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.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 19, 2026 | Flagged37 | — | 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 243 findings across every scanner that examined this package. None of the 6 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 78 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 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/docker-deploy.yml · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
2 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock · reported by agent-audit-kit
2 GHSA-537c-gmf6-5ccf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-c2jp-c369-7pvx
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
1 CVE-2025-59420
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-64340
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-66471
Files: uv.lock · reported by trivy
1 CVE-2025-68158
Files: uv.lock · reported by trivy
1 CVE-2025-69196
Files: uv.lock · reported by trivy
1 CVE-2025-69223
Files: uv.lock · reported by trivy
1 CVE-2025-69227
Files: uv.lock · reported by trivy
1 CVE-2025-69228
Files: uv.lock · reported by trivy
1 CVE-2025-69229
Files: uv.lock · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-21441
Files: uv.lock · reported by trivy
1 CVE-2026-22815
Files: uv.lock · reported by trivy
1 CVE-2026-24049
Files: uv.lock · reported by trivy
1 CVE-2026-24486
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-26007
Files: uv.lock · reported by trivy
1 CVE-2026-27124
Files: uv.lock · reported by trivy
1 CVE-2026-27962
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-32871
Files: uv.lock · reported by trivy
1 CVE-2026-34515
Files: uv.lock · reported by trivy
1 CVE-2026-34516
Files: uv.lock · reported by trivy
1 CVE-2026-34525
Files: uv.lock · reported by trivy
1 CVE-2026-34993
Files: uv.lock · reported by trivy
1 CVE-2026-39892
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-41479
Files: uv.lock · reported by trivy
1 CVE-2026-42561
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-45409
Files: uv.lock · reported by trivy
1 CVE-2026-47265
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-49476
Files: uv.lock · reported by trivy
1 CVE-2026-49477
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-54273
Files: uv.lock · reported by trivy
1 CVE-2026-54274
Files: uv.lock · reported by trivy
1 CVE-2026-54276
Files: uv.lock · reported by trivy
1 CVE-2026-54278
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-59881
Files: uv.lock · reported by trivy
1 CVE-2026-59890
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-69243
Files: uv.lock · reported by trivy
1 CVE-2026-69244
Files: uv.lock · reported by trivy
1 CVE-2026-69247
Files: uv.lock · reported by trivy
1 CVE-2026-69249
Files: uv.lock · reported by trivy
1 GHSA-rcfx-77hg-w2wv
Files: uv.lock · reported by trivy
1 PYSEC-2026-1100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1107
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-1389
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-188
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-2047
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2113
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-2249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2250
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2252
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
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-237
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-2476
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-287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
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-3071
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3072
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-338
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3447
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
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-3493
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
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
78 The review budget for this scan was already spent before these findings were reached.
Rules: PYSEC-2026-25, CVE-2026-69248, CVE-2026-54277 and 38 more · Files: /repo/uv.lock, uv.lock, SECURITY.md and 38 more · reported by osv-scanner, trivy, agent-audit-kit and 1 more
Critical vulnerabilities detected in artifact dependencies.
The artifact contains dependencies with critical vulnerabilities, including PYSEC-2026-36, PYSEC-2026-2102, PYSEC-2026-338, CVE-2026-27962, CVE-2026-32871, and PYSEC-2026-287. These issues, found in uv.lock and pyproject.toml, could lead to capabilities like remote code execution, unauthorized data access, or denial of service. Multiple high-severity vulnerabilities, such as AAK-MCP-SDK-CVE-2026-52869-001 and GHSA-537c-gmf6-5ccf, also warrant attention. These findings indicate a substantial risk to system integrity and operational security.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 94; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.