io.github.wyre-technology/timezest-mcp
TimeZest
Is the TimeZest MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-02.
MCP server for TimeZest — appointment scheduling, agents, appointment types, and resources for MSPs.
alive probed 2026-11-15 · unchanged since 2026-11-02
- Run it
- docker run -i --rm ghcr.io/wyre-technology/timezest-mcp:v1.2.6 (stdio, probed in a container with the network off)
- Host
- ghcr.io
- Reports itself as
- timezest-mcp 0.1.0
- Capabilities
- resources, tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 186 tokens in Claude Opus 5.5, exact, measured 2026-11-02. With the Claude Code prefix mcp__…__ on each tool name: 210. The o200k_base estimate is 97. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/wyre-technology/timezest-mcp
- Website
- https://github.com/wyre-technology/timezest-mcp
- Registry
- active, updated 2026-08-11 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.92×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| timezest_navigate | 128 | 67 | 69 % |
| timezest_status | 58 | 30 | 31 % |
Compare this server with others.
More servers
Other registry entries on ghcr.io, the ones next to this name; all of them.
- Spanning Cloud Backup io.github.wyre-technology/spanning-mcp · alive
- SuperOps io.github.wyre-technology/superops-mcp · alive
- Syncro io.github.wyre-technology/syncro-mcp · alive
- ThreatLocker io.github.wyre-technology/threatlocker-mcp · alive
- Unitrends Backup io.github.wyre-technology/unitrends-mcp · alive
- Xero io.github.wyre-technology/xero-mcp · alive
- Crawlberg io.github.xberg-io/crawlberg · error
- io.github.xkid1/reed-solomon-alg-mcp · alive
Servers that mention timezest or appointment or scheduling.
- io.github.sagarkalra-tech/timezest-mcp · alive
- TimeZest io.github.WYRE-AI/timezest-mcp · alive
- BAMF.ai ai.bamf/bamf · not MCP
- Chronary ai.chronary/mcp · alive
- RadiusOS CRM ai.radiusos.www/crm · needs auth
- app.g-guest/g-guest · alive
- app.reassign/reassign · needs auth
- Schedii app.schedii/mcp · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-02 08:24 | alive | 1.4 s | 2 | 186 | 97 |
| 2026-10-26 07:05 | alive | 409 ms | 2 | 97 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.