Chronary
REMOTE · API.CHRONARY.AI · 2 COMPONENTS · SCANNED AUG 3
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
Available components
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 →
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 Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 6199 tokens (~112/item across 55 items; 54 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.chronary.ai
claude mcp add --transport http ai-chronary-mcp https://api.chronary.ai/mcp
[mcp_servers.ai-chronary-mcp] url = "https://api.chronary.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-chronary-mcp": {
"type": "remote",
"url": "https://api.chronary.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-chronary-mcp --url https://api.chronary.ai/mcp --transport streamable-http
mcp_servers:
ai-chronary-mcp:
url: "https://api.chronary.ai/mcp" {
"mcpServers": {
"ai-chronary-mcp": {
"type": "http",
"url": "https://api.chronary.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +4
- 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 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 73
First indexed and scored.
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 3 Aug 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 | 8 Jun 2026 | 6 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 922827676e3f3fa3137fd996cb782bd5 |
| 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 |
DNSSEC insecure
Validation of api.chronary.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 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 |
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.
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 ~299
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 | — | — | 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.