Is the Theluckystrike Scheduling MCP server down?

mcp-registry/io.github.theluckystrike/scheduling · v0.22.6

down
Last checked 2026-10-22 08:58 UTC · handshake 89ms

As of 2026-10-22 08:58 UTC, the Theluckystrike Scheduling MCP server is down with a Glimind reliability score of 24/100 (grade F). Over the last 30 days it answered 29.7% of Glimind's liveness checks. It had 514 outages in 90 days, with a median recovery of 42 minutes.

uptime (30d checks)
29.7%
checks observed
2,461
outages (90d)
514
tools
11

Meeting scheduling across time zones: slot finding, DST checks, .ics invites.

Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/scheduling

Agent-readiness: B (86/100)

B (86/100): 2 error(s), 0 warning(s) across 11 tool(s); ~3,067 tokens of tool definitions.
Scores higher than 53% of 15,554 MCP servers Glimind has audited.
Its tool list costs an agent ~3,067 tokens per session — more than 55% of servers.
88 → 88 since 2026-10-20
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (3)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

Reachable 29.7% of the time over the last 30 days; median recovery 42 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.theluckystrike/scheduling"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.theluckystrike/scheduling"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Fscheduling.svg)](https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fscheduling?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fscheduling?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Fscheduling.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Fscheduling.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fscheduling?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e4a53cdbbaf1a550…, first seen 2026-10-17, included at leaf 6583 of 47,510. Version history · verify what your client received.

Working alternatives

Tools (11)

Compare: most reliable productivity servers · most reliable communication servers · most reliable knowledge servers · most reliable calendar servers · most reliable files servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Theluckystrike Scheduling MCP server down right now?

As of 2026-10-22 08:58 UTC, the Theluckystrike Scheduling MCP server is down with a Glimind reliability score of 24/100 (grade F). Over the last 30 days it answered 29.7% of Glimind's liveness checks. It had 514 outages in 90 days, with a median recovery of 42 minutes.

How many tools does Theluckystrike Scheduling MCP server provide?

Theluckystrike Scheduling MCP server advertises 11 tools, including business_days, contacts_list, contacts_set, convert_time, dst_changes.

How do I install Theluckystrike Scheduling MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/scheduling

Is the Theluckystrike Scheduling MCP server safe to connect to an AI agent?

Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Theluckystrike Scheduling MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve