ToolsMCP
Chronary
Listed in the official MCP Registry with a hosted streamable-http endpoint and an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- chronary.ai
- Prerequisites
- An MCP client that supports streamable-http. The publisher declares a required credential header. Install @chronary/mcp from npm (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.5.2 · updated
- Official links
Publisher’s description
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.5.2, registry status active. 1 remote endpoint (streamable-http); 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- chronary.ai
- Version observed
- 1.5.2
- Source
- registry.modelcontextprotocol.io/v0.1/servers/ai.chronary%2Fmcp/versions/1.5.2
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Manage calendar events from an assistant | Publisher description mentions “calendar”, “ical”, “events”, “availability”. | No connection check or task run. Capability is as described by the publisher. | Rule calendar-events matched: “calendar”, “ical”, “events”, “availability”. Rule calendar-events. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://api.chronary.ai/mcp(streamable-http, declares a required credential)- Packages
@chronary/mcp(npm, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
ai.chronary/mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.