Chronary

warnings

api.chronary.ai

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

https://api.chronary.ai/mcpWebsiteNo authMCP 2025-11-25v1.0.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 959 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 54 tools listable
Credentials demanded in prose	✕subscribe_ical, create_proposal, list_proposals, get_proposal, respond_to_proposal, resolve_proposal, cancel_proposal, create_scoped_key, list_scoped_keys, revoke_scoped_key, create_webhook, list_webhooks, get_webhook, update_webhook, delete_webhook, list_webhook_deliveries, update_agent, delete_agent, get_usage, get_audit_log, accept_terms These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

21 of the 54 tools listed anonymously say in their own descriptions that they need an account or a key (subscribe_ical, create_proposal, list_proposals, get_proposal, respond_to_proposal, resolve_proposal, cancel_proposal, create_scoped_key, list_scoped_keys, revoke_scoped_key, create_webhook, list_webhooks, get_webhook, update_webhook, delete_webhook, list_webhook_deliveries, update_agent, delete_agent, get_usage, get_audit_log, accept_terms), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

Tools

accept_termscancel_connection_linkcancel_eventcancel_proposalclear_availability_rulesconfirm_eventcreate_agentcreate_booking_pagecreate_calendarcreate_connection_linkcreate_eventcreate_proposalcreate_scoped_keycreate_webhookdelete_agentdelete_booking_pagedelete_calendardelete_ical_subscriptiondelete_webhookfind_meeting_timeget_agentget_audit_logget_availabilityget_availability_rulesget_booking_pageget_calendarget_calendar_contextget_connection_linkget_eventget_ical_subscriptionget_proposalget_usageget_webhooklist_agentslist_booking_pageslist_calendarslist_eventslist_ical_subscriptionslist_proposalslist_scoped_keyslist_webhook_deliverieslist_webhooksrelease_eventresolve_proposalrespond_to_proposalrevoke_scoped_keyset_availability_rulessubscribe_icalsync_ical_subscriptionupdate_agentupdate_calendarupdate_eventupdate_ical_subscriptionupdate_webhook

Contract history

24 Aug 2026v1.0.0first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/chronary/badge.svg)](https://mcpi.app/servers/chronary)