Loading the registry…
MCP server for interacting with Google Calendar 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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @smithery/mcp-google-calendar
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.
v1.4.0
0 findings · 0.5s
v2.0.11
3 findings · 6.2s
v0.3.74
8 findings · 0.9s
v0.1.0
0 findings · 2.8s
v0.1.0
0 findings · 2.8s
v0.71.0
12 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 · 1.8s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.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 20, 2026 | Flagged44 | — | 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 ·n/a: not applicabletrivy_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 23 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 23 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
23 The review call did not complete.
Rules: AAK-DNS-REBIND-002, CVE-2026-4926, AAK-SECRET-004 and 17 more · Files: package.json, package-lock.json, smithery.yaml and 7 more · reported by agent-audit-kit, trivy, cisco-skill-scanner
High severity findings: DNS rebind, exposed secret, and multiple CVEs.
The artifact contains high severity findings, including a DNS rebind vulnerability in `package.json` and an exposed secret in `smithery.yaml`. Multiple high severity CVEs, such as CVE-2025-65945 and CVE-2026-4926, are present in dependencies listed in `package-lock.json`. These issues indicate potential for network egress, credential access, and exploitation of known vulnerabilities.
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.