Case file No.153 · npm · stdio · streamable-http

Chronary

ai.chronary/mcp · v1.5.2

Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.

Package ↗GitHub ↗Website ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 7 days ago

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

252 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v1.5.2)Oct 24, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is Chronary safe?

MCPWatch gives Chronary a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does Chronary have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the npm package @chronary/mcp. That is not proof of safety.

When was Chronary last updated?

The latest registry version is 1.5.2, published Jul 14, 2026. The last push to Chronary/chronary-mcp was on Oct 17, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does Chronary use?

GitHub reports the license of Chronary/chronary-mcp as Apache-2.0.

Related servers

same publisher / similar score