Chronary MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Chronary calendar and scheduling proposals: Do scheduling proposals retain human setup and scoped keys before committing calendar changes?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Agent calendar, scheduling, availability, proposals, webhooks and iCal management.

What we know

Calendar MCP with read/write tools for agents, calendars, events, availability, meeting proposals, availability rules, webhooks, iCal subscriptions, scoped keys, audit log and usage.

Maintenance / activity evidence

@chronary/mcp 1.5.2 published 2026-07-14T21:12:54.331Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Calendar/event/agent/scheduling/webhook/scoped-key read-write authority. Writes: Create/update/delete calendars/events/agents; Cancel/release events; Create/respond/cancel proposals; Set/clear availability; Manage webhooks/iCal subscriptions; Create/revoke scoped keys.
Chronary API key.
Sensitive access: Calendar events, Attendee information, Webhook destinations, API/scoped credentials

Can create/cancel meetings and change integration credentials; user confirmation appropriate for destructive actions.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do scheduling proposals retain human setup and scoped keys before committing calendar changes?

The bounded review of the publisher's documented Chronary calendar and scheduling proposals and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can create/cancel meetings and change integration credentials; user confirmation appropriate for destructive actions.
Calendar/event/agent/scheduling/webhook/scoped-key read-write authority.
Chronary API key.
Calendar/event/attendee/scheduling data is handled by Chronary.
Reviewed write actions: Create/update/delete calendars/events/agents; Cancel/release events; Create/respond/cancel proposals; Set/clear availability; Manage webhooks/iCal subscriptions; Create/revoke scoped keys
Sensitive access: Calendar events, Attendee information, Webhook destinations, API/scoped credentials
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Broad write/destructive calendar surface.
API key/account required.
Tool count can consume substantial client context unless filtered.
Scoped key revocation can lock out integrations.

Original activity observations

@chronary/mcp 1.5.2 published 2026-07-14T21:12:54.331Z

Technical identity

npm/@chronary/mcp

Exact implementation source: https://www.npmjs.com/package/@chronary/mcp ↗
Reviewed resource type: MCP Server
Repository identity: Chronary/chronary-mcp
Package identity: npm:@chronary/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@chronary/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
CHRONARY_API_KEY required; publisher includes per-client config and optional Smithery install route.
publisher install or stdio launch · Publisher instructions
npx -y @chronary/mcp
Configure / authenticate
MCP100 setup guide
Register `npx -y @chronary/mcp` with CHRONARY_API_KEY; publisher also documents Smithery CLI installation and Windows cmd /c wrapper.
Check connection
Suggested check
Check tool discovery and read-only calendar listing; do not create appointments.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `chronary-mcp`, run `claude mcp remove chronary-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove chronary-mcp

Official Documentation & Sources

What it does

Calendar MCP with read/write tools for agents, calendars, events, availability, meeting proposals, availability rules, webhooks, iCal subscriptions, scoped keys, audit log and usage.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Agent calendar, scheduling, availability, proposals, webhooks and iCal management.

Representative uses

List/create/update/delete calendars/events
Find meeting times
Run/respond to scheduling proposals
Manage availability rules
Manage webhooks/iCal subscriptions/scoped keys

Limitations

Broad write/destructive calendar surface.
API key/account required.
Tool count can consume substantial client context unless filtered.
Scoped key revocation can lock out integrations.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Chronary API key.
Permissions: Calendar/event/agent/scheduling/webhook/scoped-key read-write authority.
Data handling: Calendar/event/attendee/scheduling data is handled by Chronary.
Cost: plan_based
Risk and cautions: Can create/cancel meetings and change integration credentials; user confirmation appropriate for destructive actions.

Access scope and cautions

Write actions: Create/update/delete calendars/events/agents Cancel/release events Create/respond/cancel proposals Set/clear availability Manage webhooks/iCal subscriptions Create/revoke scoped keys
Sensitive access: Calendar events Attendee information Webhook destinations API/scoped credentials
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List/create/update/delete calendars/events; Find meeting times; Run/respond to scheduling proposals; Manage availability rules; Manage webhooks/iCal subscriptions/scoped keys.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @chronary/mcp. Recorded transport: stdio. Recorded environment-variable notes: CHRONARY_API_KEY. No configuration values are supplied here. Prerequisites: Chronary account; Node.js >=18. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Chronary API key.

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete calendars/events/agents; Cancel/release events; Create/respond/cancel proposals; Set/clear availability; Manage webhooks/iCal subscriptions; Create/revoke scoped keys. Recorded permission boundary: Calendar/event/agent/scheduling/webhook/scoped-key read-write authority.

What data-handling boundary should I consider?

Calendar/event/attendee/scheduling data is handled by Chronary. Recorded sensitive-access context: Calendar events; Attendee information; Webhook destinations; API/scoped credentials.

What limitations and risks should I check before use?

Can create/cancel meetings and change integration credentials; user confirmation appropriate for destructive actions. Broad write/destructive calendar surface. API key/account required. Tool count can consume substantial client context unless filtered. Scoped key revocation can lock out integrations. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.