# TimeZest (oci · ghcr.io/wyre-ai/timezest-mcp)

MCP server for TimeZest — appointment scheduling, agents, appointment types, and resources for MSPs.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- oci · `ghcr.io/wyre-ai/timezest-mcp`: 40/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-timezest-mcp/ghcr-io-wyre-ai-timezest-mcp.md), [page](https://verifymcp.io/servers/wyre-ai-timezest-mcp/ghcr-io-wyre-ai-timezest-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/timezest-mcp`
- Version: `v3.0.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 822 tokens (~63/item across 13 items; 12 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the TimeZest MCP server?

TimeZest runs locally as a container image, launched with docker run --rm -i -e TIMEZEST_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/timezest-mcp:v3.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-timezest-mcp -- docker run --rm -i -e TIMEZEST_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/timezest-mcp:v3.0.2
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-timezest-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TIMEZEST_API_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"
      ]
    }
  }
}
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "wyre-ai-timezest-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TIMEZEST_API_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"
      ]
    }
  }
}
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add wyre-ai-timezest-mcp -- docker run --rm -i -e TIMEZEST_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/timezest-mcp:v3.0.2
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-timezest-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "TIMEZEST_API_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"
      ],
      "enabled": true
    }
  }
}
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  wyre-ai-timezest-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "TIMEZEST_API_TOKEN", "-e", "MCP_TRANSPORT", "-e", "AUTH_MODE", "-e", "LOG_LEVEL", "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"]
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-timezest-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TIMEZEST_API_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"
      ]
    }
  }
}
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "wyre-ai-timezest-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "TIMEZEST_API_TOKEN",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"
      ]
    }
  }
}
```

This image reads TIMEZEST_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 40, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-15 (score 39, +33)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Capabilities: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-14 (score 6)

First indexed and scored.

## MCP tools (12)

### `timezest_status` (~21 tokens)

Show TimeZest connection status and the available tools

### `timezest_agents_list` (~69 tokens)

List all agents (technicians) available for scheduling

Input parameters:

- `filter` (string): TQL filter string (e.g., "active:true AND department:\"IT Support\"")
- `pageSize` (number): Number of results per page (default: 50, max: 100)

### `timezest_agents_get` (~30 tokens)

Get details for a specific agent by ID

Input parameters:

- `agentId` (string, required): Agent ID

### `timezest_teams_list` (~85 tokens)

List teams available for scheduling. Deleted teams are omitted, using the same live set as timezest_resources_list (teams GET /v1/resources still returns).

Input parameters:

- `filter` (string): TQL filter string (e.g., "active:true")
- `pageSize` (number): Number of results per page (default: 50, max: 100)

### `timezest_teams_get` (~31 tokens)

Get details for a specific team by ID

Input parameters:

- `teamId` (string, required): Team ID

### `timezest_appointment_types_list` (~62 tokens)

List all appointment types available for scheduling

Input parameters:

- `filter` (string): TQL filter string (e.g., "active:true")
- `pageSize` (number): Number of results per page (default: 50, max: 100)

### `timezest_appointment_types_get` (~35 tokens)

Get details for a specific appointment type by ID

Input parameters:

- `appointmentTypeId` (string, required): Appointment type ID

### `timezest_resources_list` (~75 tokens)

List all resources (agents and teams) available for scheduling

Input parameters:

- `filter` (string): TQL filter string (e.g., "active:true")
- `pageSize` (number): Number of results per page (default: 50, max: 100)
- `type` (string): Filter by resource type

### `timezest_scheduling_list` (~166 tokens)

List scheduling requests

Input parameters:

- `filter` (string): TQL filter string (e.g., "createdAt:>=2024-01-01")
- `pageSize` (number): How many records to return from this page (1–20). TimeZest list pages are fixed at 20 and ignore a page_size query parameter; smaller values truncate that page. Larger values still return at most one…
- `status` (string): Filter by TimeZest status: new, sent, scheduled, cancelled, closed. Legacy aliases are accepted and mapped: pending→sent, booked→scheduled, completed→closed. Sent as a TQL filter (scheduling_request.…

### `timezest_scheduling_get` (~33 tokens)

Get details for a specific scheduling request by ID

Input parameters:

- `requestId` (string, required): Scheduling request ID

### `timezest_scheduling_create_request` (~154 tokens)

Create a new scheduling request - supports PSA ticket association

Input parameters:

- `appointmentTypeId` (string): Appointment type ID (required)
- `associatedEntities` (array): Associated PSA tickets/entities
- `endUser` (object, required): End user contact information
- `notes` (string): Additional notes or requirements
- `resourceIds` (array): Resource IDs (agent or team ids) to book with. Sent to TimeZest as the JSON array resource_ids. Omit to send an empty array — TimeZest requires the field to be an array.
- `timeRange` (object): Preferred scheduling window
- `triggerMode` (string, required): pod = fires PSA workflow, generate_url = returns booking link

### `timezest_scheduling_cancel` (~40 tokens)

Cancel a scheduling request

Input parameters:

- `reason` (string): Reason for cancellation
- `requestId` (string, required): Scheduling request ID to cancel

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-timezest-mcp/ghcr-io-wyre-ai-timezest-mcp#diagnostics

## Score history

- 2026-10-18: 40
- 2026-10-17: 40
- 2026-10-16: 39
- 2026-10-15: 39
- 2026-10-14: 6

## Common questions

### What is the TimeZest MCP server?

TimeZest is an MCP server listed in the public MCP registry as io.github.WYRE-AI/timezest-mcp. MCP server for TimeZest, appointment scheduling, agents, appointment types, and resources for MSPs. This page covers its container image (ghcr.io/wyre-ai/timezest-mcp).

### Is the TimeZest MCP server safe to use?

TimeZest scores 40 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the TimeZest MCP server expose?

TimeZest exposes 12 tools: timezest_status, timezest_agents_list, timezest_agents_get, timezest_teams_list, timezest_teams_get, and 7 more. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.

### Is the TimeZest MCP server still maintained?

TimeZest is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the TimeZest MCP server under?

TimeZest declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/wyre-ai/timezest-mcp
- Repository: https://github.com/WYRE-AI/timezest-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-timezest-mcp/ghcr-io-wyre-ai-timezest-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-timezest-mcp/ghcr-io-wyre-ai-timezest-mcp.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-timezest-mcp/ghcr-io-wyre-ai-timezest-mcp