Chronary

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v1.5.2

1. Real tool

   passrules 2026-09-29.1 · 4 hours ago

2. Static scan

   failrules 2026-09-29.1 · 4 hours ago
   • criticalPairs a secret with an instruction to send data.tool:create_proposal.description
   • criticalPairs a secret with an instruction to send data.tool:create_webhook.description
   • criticalPairs a secret with an instruction to send data.tool:get_agent.description
   • criticalPairs a secret with an instruction to send data.tool:list_calendars.description

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.chronary.ai/mcp"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• create_agent

  Register your agent (AI assistant, human participant, or resource) with Chronary so it can own calendars, events, and webhooks.

• list_agents

  List all agents in your organization

• create_calendar

  Create a calendar to hold events and track availability. Calendars are required before creating events — call this first when setting up a new agent. An agent can have multiple calendars (e.g. "Work", "Personal"). Org-level calendars (no agent_id) can be used as shared resources like meeting rooms.

• create_event

  Create a booking, appointment, meeting, hold, or any scheduled event on a calendar. The calendar_id comes from create_calendar or list_events. Once created, this event blocks the agent's availability during that time and appears in availability queries. Use status="hold" with hold_expires_at to tentatively reserve a slot that auto-releases on TTL.

• list_events

  List events on a calendar or across an agent's calendars, including internally created events and externally synced events from iCal subscriptions (e.g. Google Calendar, Outlook). Provide `calendar_id` OR `agent_id`. Narrow with `start_after`/`start_before` (time window), `status`, and `source`.

• get_event

  Retrieve a single event by ID, including its title, times, status, location, reminders, and metadata. Works for both internally created events and externally synced iCal events. `calendar_id` is optional — if omitted the calendar is resolved from the event. Provide `calendar_id` to fail fast on cross-calendar typos.

• update_event

  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.