C

Chronary

ai.chronary/mcp · v1.5.2 · MCP server

by ai.chronaryScan grade: AcceptableOfficial MCP registry · source scanned

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

Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is Chronary a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • MCP
  • 1 MCP server

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

  • 5 medium findings from the scan. See the evidence
  • The publisher has not verified ownership on HOL.
  • No license declared in the manifest.

What is Chronary?

Chronary is a published mcp server plugin for AI coding agents in the MCP ecosystem, developed by ai.chronary and distributed through the HOL AI plugin registry. Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.

Canonical slug
ai.chronary/mcp
Version
v1.5.2 · updated Jul 14, 2026

Registry snapshot

Owner verification
Not verified
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
No

Trust and security

Provenance

Plugin root
.
Source repo
https://github.com/Chronary/chronary-mcp
Source commit
00b86e6e810e…
Publisher verified
No
Owner verified
Not owner verified
Needs review
Security result
73
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
C · Acceptable
Version
3.24.2
cisco-mcp-scanner: skipped

Security

13/16

9 checks

Operational Security

9/20

5 checks

Best Practices

6/6

4 checks

Code Quality

10/10

2 checks

Published advisories

None matched in OSV, checked . This covers published advisories only, not problems nobody has reported.

OSV is matched against the exact package versions this listing names.

Findings

mediumoperational-securityGITHUB_ACTION_UNPINNED

.github/workflows/release-artifact.yml references "actions/checkout@v4" instead of a full 40-character commit SHA.

Pin third-party GitHub Actions and reusable workflows to a full commit SHA.

mediumoperational-securityGITHUB_ACTION_UNPINNED

.github/workflows/release-artifact.yml references "pnpm/[email protected]" instead of a full 40-character commit SHA.

Pin third-party GitHub Actions and reusable workflows to a full commit SHA.

mediumoperational-securityGITHUB_ACTION_UNPINNED

.github/workflows/release-artifact.yml references "actions/setup-node@v4" instead of a full 40-character commit SHA.

Pin third-party GitHub Actions and reusable workflows to a full commit SHA.

mediumoperational-securityGITHUB_ACTION_UNPINNED

.github/workflows/release-artifact.yml references "actions/attest-build-provenance@v2" instead of a full 40-character commit SHA.

Pin third-party GitHub Actions and reusable workflows to a full commit SHA.

mediumoperational-securityDEPENDENCY_LOCKFILE_MISSING

package.json is present without a corresponding lockfile or pinned dependency snapshot.

Commit a lockfile or use fully pinned requirements for reproducible dependency resolution.

lowsecuritySECURITY_MD_MISSING

Plugins should publish a SECURITY.md file for responsible disclosure and support guidance.

Add a SECURITY.md file with reporting guidance and supported versions.

lowoperational-securityDEPENDABOT_MISSING

Automation or dependency surfaces exist, but .github/dependabot.yml is missing.

Add Dependabot updates for GitHub Actions and dependency manifests.

Install guidance

Install in MCP

Connect the bundled MCP server shipped in the repository .mcp.json file.

MCP docs
  1. 1

    Clone the repository

    shell
  2. 2

    Register the server in your MCP client

    Claude Code reads a project .mcp.json file and asks you to approve its servers when you open the folder. Other clients keep their own MCP configuration, so copy the server entry from .mcp.json into that client. If this repository configures its server differently, follow the MCP setup the publisher documents.

  3. 3

    Verify the server

    Check the MCP server list in your client. The server declared in .mcp.json should report as connected. In Claude Code, run /mcp to see it.

Did setup work in MCP?

No setup reports for MCP yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W43, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

Loading reviews

Plugin manifest

{
  "source": "official-mcp-registry",
  "evidenceState": "scanned_source",
  "registryName": "ai.chronary/mcp",
  "publishedAt": "2026-07-14T21:12:59.153451Z",
  "packages": [
    {
      "registryType": "npm",
      "identifier": "@chronary/mcp",
      "version": "1.5.2",
      "transport": "stdio",
      "requiredEnvironment": [
        "CHRONARY_API_KEY"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://api.chronary.ai/mcp"
    }
  ],
  "sourceScannedAt": "2026-10-30T09:37:12.877Z",
  "sourceScanCommit": "00b86e6e810e3807c558bd107ed375996c9c6cca"
}

File inventory

File inventory is unavailable for this plugin right now.

Chronary — Frequently asked questions

What is Chronary?
Chronary is an AI plugin in the HOL registry. Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
How do I install Chronary?
Install Chronary in your harness: MCP — git clone https://github.com/Chronary/chronary-mcp. Full step-by-step guidance is on the HOL plugin page.
How do I install Chronary in MCP?
To install Chronary in MCP, start with git clone https://github.com/Chronary/chronary-mcp. The complete step-by-step install guide for MCP is on the HOL plugin page.
Who publishes Chronary?
Chronary is published by ai.chronary and listed on HOL.

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W43. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.