Chronary
REMOTE · API.CHRONARY.AI · 2 COMPONENTS
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
Available components
Last scanned (2 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6549 tokens (~111/item across 59 items; 58 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "cancel_event" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cancel_proposal” rewrote its description, which is the text the model reads security
- New tool “cancel_upgrade_request” functional
- New tool “get_billing” functional
- New tool “get_upgrade_request” functional
- New tool “request_upgrade” functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.chronary.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chronary.ai | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8fef31ad123555d01377949c4918f922 |
| SANs: chronary.ai, api.chronary.ai, *.api.chronary.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.chronary.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| chronary.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.chronary.ai/mcp | Verified | 200 | |
| http (plaintext) | http://api.chronary.ai/mcp | HTTPS enforced | 301 | https://api.chronary.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
set_availability_rules ~172
Set or replace the availability rules on a calendar — buffer times before/after events and optional per-day working hours. When these rules are set, every availability query on this calendar automatically applies them (busy-block expansion for buffers, masking outside working hours). Upsert: overwrites any existing rules.
| Name | Type | Req | Description |
|---|---|---|---|
| buffer_after_minutes | integer | – | Minutes of buffer after each event (0–120) |
| buffer_before_minutes | integer | – | Minutes of buffer before each event (0–120) |
| calendar_id | string | yes | Calendar to configure |
| timezone | string | – | IANA timezone used to interpret working_hours (e.g. America/New_York) |
| working_hours | – | – | Per-day working hours map in the calendar's timezone; omit keys for off-days. Pass null to remove any working-hours constraint. |
No output schema declared.
No examples provided.
subscribe_ical ~144
Link an external iCal feed (e.g. a human's Google Calendar) to an agent's calendar so external events appear in availability calculations. The target calendar must be owned by the specified agent — create the calendar with that agent_id first (org-level calendars without an agent_id cannot host external iCal subscriptions; create a dedicated per-agent calendar for sync targets).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent ID that will own this subscription |
| calendar_id | string | yes | Calendar ID to sync external events into |
| label | string | – | Optional label for this subscription |
| url | string | yes | HTTPS URL of the iCal feed (.ics) to subscribe to |
No output schema declared.
No examples provided.
sync_ical_subscription ~52
Trigger an immediate sync of an external iCal feed subscription instead of waiting for the next scheduled poll. Returns once the sync has been queued.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | iCal subscription ID to sync |
No output schema declared.
No examples provided.
update_agent ~100
Update an agent's name, description, metadata, or status (active/paused). Requires an org-level API key — agent-scoped keys cannot mutate agents.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent ID to update |
| description | string|null | – | New description (null to clear) |
| metadata | object | – | Arbitrary metadata (max 16KB) |
| name | string | – | New display name |
| status | string | – | Operational status |
No output schema declared.
No examples provided.
update_calendar ~128
Update a calendar's name, timezone, agent status, default reminders, or metadata. Agent-scoped keys may only update calendars owned by their agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_status | string | – | Owning agent's status |
| calendar_id | string | yes | Calendar ID to update |
| default_reminders | – | – | Default reminder offsets in minutes; null for system default, [] for none |
| metadata | object | – | Arbitrary metadata (max 16KB) |
| name | string | – | New calendar name |
| timezone | string | – | New IANA timezone (e.g. America/New_York) |
No output schema declared.
No examples provided.
update_event ~302
Reschedule or edit an event — change its title, description, start/end times, location, status, reminders, or metadata. Use this to move an appointment to a new time or update its details. Provide only the fields you want to change. Holds cannot be edited via this tool (use confirm_event / release_event). External iCal events are read-only. `calendar_id` is optional — if omitted it is resolved from the event.
| Name | Type | Req | Description |
|---|---|---|---|
| all_day | boolean | – | Whether this is an all-day event |
| calendar_id | string | – | Calendar ID that owns the event. Optional — if omitted the calendar is resolved from the event. |
| description | string|null | – | New description, or null to clear it |
| end_time | string | – | New end time (ISO 8601) |
| event_id | string | yes | Event ID to update |
| metadata | object | – | Replacement metadata object |
| recurrence_rule | – | – | Set/change the recurring series rule (RFC 5545 RRULE subset, full-series semantics), or null to make the event a one-off. Changing the rule or start_time resets cancelled occurrences. |
| reminders | – | – | Reminder offsets in minutes before start_time. Omit to leave unchanged, null to inherit the calendar default, [] for no reminders. |
| start_time | string | – | New start time (ISO 8601) |
| status | string | – | New event status |
| title | string | – | New event title |
No output schema declared.
No examples provided.
update_ical_subscription ~82
Update an external iCal feed subscription — change its label or its feed URL. Changing the URL forces a full re-sync on the next poll.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | New label for this subscription |
| subscription_id | string | yes | iCal subscription ID to update |
| url | string | – | New HTTPS URL of the iCal feed (.ics) |
No output schema declared.
No examples provided.
update_webhook ~104
Update a webhook subscription — change its delivery URL, the set of subscribed event types, or pause/resume it via active. At least one field must be supplied. Requires an org-level API key.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Set false to pause deliveries, true to resume |
| events | array | – | Replacement set of event types to subscribe to |
| url | string | – | New HTTPS delivery endpoint |
| webhook_id | string | yes | Webhook subscription to update |
No output schema declared.
No examples provided.
How do I install the Chronary MCP server?
Chronary is a hosted endpoint at https://api.chronary.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.chronary.ai
claude mcp add --transport http ai-chronary-mcp 'https://api.chronary.ai/mcp'
What is the Chronary MCP server?
Chronary is an MCP server listed in the public MCP registry as ai.chronary/mcp. Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal. This page covers its hosted endpoint (https://api.chronary.ai/mcp).
Is the Chronary MCP server safe to use?
Chronary scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Chronary MCP server expose?
Chronary exposes 58 tools: create_agent, list_agents, create_calendar, create_event, list_events, and 53 more. Their descriptions and schemas cost roughly 6,285 tokens of context every time the server is loaded.
Does the Chronary MCP server require authentication?
Yes. Chronary asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Chronary MCP server still maintained?
Chronary is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.