MCP server list / Chronary
Calendar API for AI agents — events, availability, scheduling, webhooks, and iCal feeds.
Answered:
4 of 4 checks
- Status
- responds
- Typical response time
- 605 ms
- Last checked
- Latest check:
- This server answered at its latest check.Last checked · MCP initialize · 8s limit · HTTP 200 · answered in 901 ms.
- Address
- https://api.chronary.ai/
mcp - Listed in:
- official MCP registry
mcp_registry - Registry name
- ai.chronary/
mcp - Transport
- streamable HTTP
streamable-http - Host
api.chronary.ai
An outside server from a public listing, not run by Licium; being listed here is not an endorsement.
What the server says about itself
We have not checked it.- Server name:
- chronary
- Version:
- 1.0.0
- MCP features it lists:
- tools, prompts, resources
- Tool names:
create_agentlist_agentscreate_calendarcreate_eventlist_eventsget_eventupdate_eventget_availabilityfind_meeting_timecancel_eventconfirm_eventrelease_event(first 40 recorded; the server may expose more)and 28 more
subscribe_icallist_ical_subscriptionsget_ical_subscriptionupdate_ical_subscriptiondelete_ical_subscriptionsync_ical_subscriptionget_calendar_contextcreate_proposallist_proposalsget_proposalrespond_to_proposalresolve_proposalcancel_proposalset_availability_rulesget_availability_rulesclear_availability_rulescreate_scoped_keylist_scoped_keysrevoke_scoped_keycreate_webhooklist_webhooksget_webhookupdate_webhookdelete_webhooklist_webhook_deliveriesget_agentupdate_agentdelete_agent- Instructions excerpt:
- Chronary is calendar-as-a-service for AI agents. Use these tools to give an agent its own calendars and events, request human-approved Google Calendar or Microsoft Outlook connections, check and coordinate combined availability, run multi-party scheduling proposals, place auto-expiring holds, manage availability rules, sync external iCal feeds, and configu…
Reported Aug 17, 2026, 04:59 AM UTC.
Check history
oldest to newest; each row is one recorded check| Checked | Status | Took | Check |
|---|---|---|---|
| responds | 651 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 559 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 363 ms | MCP initialize · 8s limit · HTTP 200 | |
| responds | 901 ms | MCP initialize · 8s limit · HTTP 200 |
Need a different server, page or part?
Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.
Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.
Latest recorded check ; every row above is one recorded call.