TimeZest
OCI · GHCR.IO/WYRE-AI/TIMEZEST-MCP
MCP server for TimeZest — appointment scheduling, agents, appointment types, and resources for MSPs.
Available components
Last scanned (19 hours ago)
Scores higher than 54% of OCI servers
Category Project Management
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 822 tokens (~63/item across 13 items; 12 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 15 Oct 26 +33
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 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 functional
- 14 Oct 26 6
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed oci/ghcr.io/wyre-ai/timezest-mcp@v3.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
timezest_agents_get ~30
Get details for a specific agent by ID
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Agent ID |
No output schema declared.
No examples provided.
timezest_agents_list ~69
List all agents (technicians) available for scheduling
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | TQL filter string (e.g., "active:true AND department:\"IT Support\"") |
| pageSize | number | – | Number of results per page (default: 50, max: 100) |
No output schema declared.
No examples provided.
timezest_appointment_types_get ~35
Get details for a specific appointment type by ID
| Name | Type | Req | Description |
|---|---|---|---|
| appointmentTypeId | string | yes | Appointment type ID |
No output schema declared.
No examples provided.
timezest_appointment_types_list ~62
List all appointment types available for scheduling
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | TQL filter string (e.g., "active:true") |
| pageSize | number | – | Number of results per page (default: 50, max: 100) |
No output schema declared.
No examples provided.
timezest_resources_list ~75
List all resources (agents and teams) available for scheduling
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
timezest_scheduling_cancel ~40
Cancel a scheduling request
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | – | Reason for cancellation |
| requestId | string | yes | Scheduling request ID to cancel |
No output schema declared.
No examples provided.
timezest_scheduling_create_request ~154
Create a new scheduling request - supports PSA ticket association
| Name | Type | Req | Description |
|---|---|---|---|
| appointmentTypeId | string | – | Appointment type ID (required) |
| associatedEntities | array | – | Associated PSA tickets/entities |
| endUser | object | yes | 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 | yes | pod = fires PSA workflow, generate_url = returns booking link |
No output schema declared.
No examples provided.
timezest_scheduling_get ~33
Get details for a specific scheduling request by ID
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | Scheduling request ID |
No output schema declared.
No examples provided.
timezest_scheduling_list ~166
List scheduling requests
| Name | Type | Req | Description |
|---|---|---|---|
| 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.… |
No output schema declared.
No examples provided.
timezest_status ~21
Show TimeZest connection status and the available tools
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
timezest_teams_get ~31
Get details for a specific team by ID
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | yes | Team ID |
No output schema declared.
No examples provided.
timezest_teams_list ~85
List teams available for scheduling. Deleted teams are omitted, using the same live set as timezest_resources_list (teams GET /v1/resources still returns).
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | TQL filter string (e.g., "active:true") |
| pageSize | number | – | Number of results per page (default: 50, max: 100) |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/wyre-ai/timezest-mcp
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.
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.