ToolsMCP
scheduling
Listed in the official MCP Registry with an installable mcpb package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- theluckystrike (GitHub)
- Prerequisites
- Install https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/timezone.mcpb from mcpb (stdio transport). Declares 1 secret input. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.22.6 · updated
- Official links
Publisher’s description
Meeting scheduling across time zones: slot finding, DST checks, .ics invites.
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 0.22.6, registry status active. 1 package (mcpb)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- theluckystrike (GitHub)
- Version observed
- 0.22.6
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Fscheduling/versions/0.22.6
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Manage calendar events from an assistant | Publisher description mentions “ics”, “meeting”, “invites”. | No connection check or task run. Capability is as described by the publisher. | Rule calendar-events matched: “ics”, “meeting”, “invites”. 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
- Packages
https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/timezone.mcpb(mcpb, stdio, 1 secret input)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.theluckystrike/scheduling
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.