# ZenSched (remote · mcp.zensched.com)

Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `mcp.zensched.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-zensched-zensched/mcp.md), [page](https://verifymcp.io/servers/com-zensched-zensched/mcp)

## Channel facts

- Endpoint: `https://mcp.zensched.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-24.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 729 tokens (~66/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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.

## Install

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

ZenSched is a hosted endpoint at https://mcp.zensched.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-zensched-zensched 'https://mcp.zensched.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-zensched-zensched": {
      "url": "https://mcp.zensched.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-zensched-zensched": {
      "type": "http",
      "url": "https://mcp.zensched.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-zensched-zensched]
url = "https://mcp.zensched.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-zensched-zensched": {
      "type": "remote",
      "url": "https://mcp.zensched.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-zensched-zensched --url 'https://mcp.zensched.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-zensched-zensched:
    url: "https://mcp.zensched.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-zensched-zensched": {
      "Transport": "http",
      "Url": "https://mcp.zensched.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-zensched-zensched -t streamable-http -u 'https://mcp.zensched.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-zensched-zensched": {
      "type": "http",
      "url": "https://mcp.zensched.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-23 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `zensched_guide` (~56 tokens)

START HERE. The ZenSched agent guide: how to Connect (Claude.ai) or use a zsc_ key, then fund → locations → workers → shifts → timesheets. Also covers the suggestion box (feedback_submit).

Output parameters:

- `result` (string)

### `feedback_submit` (~126 tokens)

File a grievance or product recommendation. Free. Works even before you have an account. Categories: bug, friction, missing_capability, docs, billing, feature, other. Severity: low, medium, high, blocker. Include related_tool and paste error text in context when reporting a bug. A human reads every submission.

Input parameters:

- `body` (string, required)
- `category` (string)
- `context` (string)
- `idempotency_key` (string)
- `related_tool` (string)
- `severity` (string)
- `title` (string, required)

Output parameters:

- `result` (string)

### `account_create` (~67 tokens)

Create a ZenSched org without email (MCP-only agents). No OTP — returns org_id + zsc_ key immediately. Store the key securely. To attach a contact email later for human recovery, call account_set_contact. Rate-limited aggressively.

Input parameters:

- `org_name` (string, required)

Output parameters:

- `result` (string)

### `account_signup_start` (~61 tokens)

Create a ZenSched org (step 1 of 2): sends a 6-digit verification code to the email. Unauthenticated; rate-limited. Then call account_signup_verify.

Input parameters:

- `email` (string, required)
- `org_name` (string, required)

Output parameters:

- `result` (string)

### `account_signup_verify` (~78 tokens)

Create a ZenSched org (step 2 of 2): verify the emailed code. Returns org_id and your zsc_ API key (shown once). Claude.ai must then Connect → Sign in with the same email — do not keep calling org tools until Connect succeeds.

Input parameters:

- `code` (string, required)
- `email` (string, required)

Output parameters:

- `result` (string)

### `account_recover_start` (~63 tokens)

Lost API key (step 1 of 2): sends a verification code to the org owner email. Then call account_recover_verify. Prefer account_signin_start if you only need to reconnect — Recover revokes ALL keys.

Input parameters:

- `email` (string, required)

Output parameters:

- `result` (string)

### `account_recover_verify` (~50 tokens)

Lost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys.

Input parameters:

- `code` (string, required)
- `email` (string, required)

Output parameters:

- `result` (string)

### `account_signin_start` (~54 tokens)

Reconnect an existing org without rotating keys (step 1 of 2): emails a 6-digit code to the owner. Then account_signin_verify. Prefer this over Recover.

Input parameters:

- `email` (string, required)

Output parameters:

- `result` (string)

### `account_signin_verify` (~70 tokens)

Reconnect an existing org without rotating keys (step 2 of 2): verify the emailed code. Call this after account_signin_start. If later org tools fail, call account_signin_verify again or account_use_key.

Input parameters:

- `code` (string, required)
- `email` (string, required)

Output parameters:

- `result` (string)

### `account_use_key` (~66 tokens)

Authenticate this connector with an existing zsc_ API key. Prefer this when the key is already in the conversation. If the connector shows Connected but org tools fail, call this or account_signin_start — do not look for a Connect button.

Input parameters:

- `api_key` (string, required)

Output parameters:

- `result` (string)

### `account_auth_status` (~38 tokens)

Check whether this connector is signed in as a ZenSched org. Call this before account_get in a new session. Unauthenticated; never errors.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-zensched-zensched/mcp#diagnostics

## Score history

- 2026-09-24: 80
- 2026-09-23: 80
- 2026-09-22: 79
- 2026-09-21: 79
- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 77
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 71
- 2026-09-04: 71
- 2026-09-03: 70
- 2026-09-02: 70
- 2026-09-01: 74

## Common questions

### What is the ZenSched MCP server?

ZenSched is an MCP server listed in the public MCP registry as com.zensched/zensched. Field workforce scheduling for AI agents. GPS punches, forms, timesheets. No dashboard. This page covers its hosted endpoint (https://mcp.zensched.com/mcp).

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

ZenSched scores 80 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 ZenSched MCP server expose?

ZenSched exposes 11 tools: zensched_guide, feedback_submit, account_create, account_signup_start, account_signup_verify, and 6 more. Their descriptions and schemas cost roughly 729 tokens of context every time the server is loaded.

### Does the ZenSched MCP server require authentication?

Yes. ZenSched asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the ZenSched MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.zensched.com/mcp
- Authorisation metadata: https://mcp.zensched.com/.well-known/oauth-protected-resource/mcp
- Website: https://www.zensched.com/docs/quickstart/
- Changelog RSS feed: https://verifymcp.io/servers/com-zensched-zensched/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-zensched-zensched/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-zensched-zensched/mcp