Skip to content
anlyon.dev

ZenSched

com.zensched/zenschedzensched.comstreamable-httpv1.0.0Scanned

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

11 tools: 1 can delete or cancel things, 9 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 9 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

Anlyon alternative

10 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →
Compare with similar serversMarkdownJSONReport this listing

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Deletes or cancels 1Claude Code: deny
  • account_recover_verifyLost API key (step 2 of 2): verify the code.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Lost API key (step 2 of 2): verify the code. Issues a fresh key and revokes ALL previous keys.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 9Claude Code: ask
  • account_createCreate a ZenSched org without email (MCP-only agents).No findings

    Why it is in this group

    • The name "account_create" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • account_recover_startLost API key (step 1 of 2): sends a verification code to the org owner email.Reads text others writeNo findings

    Why it is in this group

    • The name "account_recover_start" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • account_signin_startReconnect an existing org without rotating keys (step 1 of 2): emails a 6-digit code to the owner.Reads text others writeNo findings

    Why it is in this group

    • The name "account_signin_start" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • account_signin_verifyReconnect an existing org without rotating keys (step 2 of 2): verify the emailed code.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • account_signup_startCreate a ZenSched org (step 1 of 2): sends a 6-digit verification code to the email.Reads text others writeNo findings

    Why it is in this group

    • The name "account_signup_start" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • account_signup_verifyCreate a ZenSched org (step 2 of 2): verify the emailed code.No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • account_use_keyAuthenticate this connector with an existing zsc_ API key.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • feedback_submitFile a grievance or product recommendation.Reads text others writeNo findings

    Why it is in this group

    • The name "feedback_submit" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • zensched_guideSTART HERE.1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "zensched_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • account_auth_statusCheck whether this connector is signed in as a ZenSched org.No findings

    Why it is in this group

    • The name "account_auth_status" says "status": a word for reading.
    Description, as the server wrote it
    Check whether this connector is signed in as a ZenSched org. Call this before account_get in a new session. Unauthenticated; never errors.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Oct 22, 2026, 14:44 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.zensched.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.zensched.com/
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (1 destructive, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.zensched.com/mcp: tools/list returned 11 tools to an anonymous client, including account_recover_verify (destructive), zensched_guide (write), feedback_submit (write), account_create (write), account_signup_start (write) and 5 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • Warnzensched_guide

    The server marks "zensched_guide" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "start": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http zensched https://mcp.zensched.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http zensched https://mcp.zensched.com/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__zensched__account_auth_status"
    ],
    "ask": [
      "mcp__zensched__zensched_guide",
      "mcp__zensched__feedback_submit",
      "mcp__zensched__account_create",
      "mcp__zensched__account_signup_start",
      "mcp__zensched__account_signup_verify",
      "mcp__zensched__account_recover_start",
      "mcp__zensched__account_signin_start",
      "mcp__zensched__account_signin_verify",
      "mcp__zensched__account_use_key"
    ],
    "deny": [
      "mcp__zensched__account_recover_verify"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zensched. Review it before you use it.

Capability tags behind 4 rules
  • mcp__zensched__feedback_submit untrusted-input
  • mcp__zensched__account_signup_start untrusted-input
  • mcp__zensched__account_recover_start untrusted-input
  • mcp__zensched__account_signin_start untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/com.zensched/zensched/verify?hash=8880dc531255ad54c95cda94235b953cbd8e737aabbf780b9fc2ee5272ca2092" | jq -e '.changed == false'

Pinned hash 8880dc531255, from Oct 21, 2026, 18:58 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.zensched/zensched/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for com.zensched/zensched
[![anlyon.dev](https://anlyon.dev/badge/com.zensched/zensched.svg)](https://anlyon.dev/servers/com.zensched/zensched)

Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.