io.github.theluckystrike/scheduling
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 30
Meeting scheduling across time zones: slot finding, DST checks, .ics invites.
Available components
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. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1634 tokens (~125/item across 13 items; 11 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
How do I install the io.github.theluckystrike/scheduling MCP server?
io.github.theluckystrike/scheduling is a hosted endpoint at https://mcp.zovo.one/mcp/scheduling, 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-scheduling 'https://mcp.zovo.one/mcp/scheduling'
{
"mcpServers": {
"theluckystrike-scheduling": {
"url": "https://mcp.zovo.one/mcp/scheduling"
}
}
} {
"servers": {
"theluckystrike-scheduling": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/scheduling"
}
}
} [mcp_servers.theluckystrike-scheduling] url = "https://mcp.zovo.one/mcp/scheduling"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-scheduling": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/scheduling",
"enabled": true
}
}
} openclaw mcp add theluckystrike-scheduling --url 'https://mcp.zovo.one/mcp/scheduling' --transport streamable-http
mcp_servers:
theluckystrike-scheduling:
url: "https://mcp.zovo.one/mcp/scheduling" {
"McpServers": {
"theluckystrike-scheduling": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/scheduling"
}
}
} assistant mcp add theluckystrike-scheduling -t streamable-http -u 'https://mcp.zovo.one/mcp/scheduling'
{
"mcpServers": {
"theluckystrike-scheduling": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/scheduling"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Sept 26 81
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 30 Sept 2026 · Probed https://mcp.zovo.one/mcp/scheduling
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"
Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/scheduling | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/scheduling | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/scheduling |
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 →
business_days Count business days ~159
Count business days between two dates in a place, inclusive, with the calendar total and the weekend and holiday counts. It has NO holiday calendar: without holidays, only weekends are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start date, YYYY-MM-DD (inclusive). A date that does not exist, such as 2026-02-30, is refused, never rolled forward |
| holidays | array | – | Dates to exclude, strict YYYY-MM-DD. This tool has no national holiday calendar: unless you pass holidays here only weekends are excluded, so do not report the answer as a public-holiday-adjusted cou… |
| to | string | yes | End date, YYYY-MM-DD (inclusive) |
| zone | string | yes | Place whose calendar to use |
No output schema declared.
No examples provided.
contacts_list List saved contacts ~44
List saved contacts with their zone, local time now, working hours and whether they are inside them; weekends count as outside. It also prints YOUR zone from the shared business profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
contacts_set Save a contact's zone ~107
Save one person's zone and working hours so later calls can name them. Returns the resolved zone and their local time now. Saving the same name REPLACES that contact and says so. Free: 5 contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Their name |
| work_end | string | – | Local day end, default 17:00 |
| work_start | string | – | Local day start, default 09:00 |
| zone | string | yes | Their place or IANA zone |
No output schema declared.
No examples provided.
convert_time Convert a time between zones ~213
Convert one time from from_zone into every zone in to_zones, marking any day change, plus the UTC instant. The time is wall-clock in from_zone unless it carries an offset or a trailing Z. '3pm tomorrow' works.
| Name | Type | Req | Description |
|---|---|---|---|
| fold | string | – | Which occurrence of a time that happens twice because the clocks went back. Default 'first'. |
| from_zone | string | yes | Place the time is given in, e.g. 'Warsaw' or 'Europe/Warsaw' |
| gap | string | – | What to do with a time that does not exist because the clocks jumped forward: 'forward' takes the time after the jump, 'backward' the time before it. Without this, such a time is refused. |
| time | string | yes | '2026-09-10 15:00', '2026-09-10T15:00:00Z', '3pm tomorrow', 'now' |
| to_zones | array | yes | Places to convert into |
No output schema declared.
No examples provided.
dst_changes Daylight-saving changes ~73
The clock changes in a place for a year, with the exact UTC instant and the offset before and after. Use it to check whether a recurring call moves for one of you in March or October.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | Calendar year, default this year |
| zone | string | yes | Place or IANA zone |
No output schema declared.
No examples provided.
find_meeting_slots Find meeting slots ~303
Rank the times when every participant is inside their own working hours. Returns each slot as a UTC instant with the local time for every participant and a fairness score, best first.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days ahead to search, default 5, at most 366. Free tier: a search longer than 5 days is shortened to 5, not refused |
| duration_minutes | integer | – | Meeting length in minutes, default 60, at most 1440 |
| earliest_date | string | – | First date to consider, YYYY-MM-DD, default today |
| limit | integer | – | How many slots to return, default 8. Slots are ranked by fairness: the score is the WORST participant's distance in hours from 13:00 local, so a slot that is 07:00 for one person never outranks one t… |
| participants | array | yes | Who has to attend. A zone is OPTIONAL per person: a saved contact supplies their own, and anyone left without one (you, typically) takes the timezone on your shared business profile, so never ask the… |
| recurring | boolean | – | Pro: also report the weekly recurring times that work on every searched weekday |
No output schema declared.
No examples provided.
ics_create Write a calendar invite ~345
Call this tool to write a .ics for one meeting and return the path plus the start in UTC and in your zone. Times are stored in UTC so it lands correctly in any client. Free: 3 files a month.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | array | – | Attendees. An entry with an email is invited (ATTENDEE:mailto:...); a name with no email is listed in the description instead, because a calendar cannot invite a name. |
| description | string | – | Body text |
| duration_minutes | integer | yes | Length in minutes, at most 1440 |
| fold | string | – | Which occurrence of a time that happens twice because the clocks went back. Default 'first'. |
| gap | string | – | What to do with a time that does not exist because the clocks jumped forward: 'forward' takes the time after the jump, 'backward' the time before it. Without this, such a time is refused. |
| location | string | – | Where, or a meeting link |
| organizer_email | string | – | Your email address, written as the ORGANIZER so replies have somewhere to go. Leave it out and your shared business profile's email is used; with neither, the ORGANIZER line is omitted rather than fi… |
| organizer_name | string | – | Your display name for the ORGANIZER line |
| out_path | string | – | Name for the downloaded file, default meeting.ics |
| start | string | yes | Start time, read in `zone` unless it carries an offset |
| title | string | yes | Event title |
| zone | string | yes | Place the start time is given in |
No output schema declared.
No examples provided.
license_activate Activate license ~76
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
now Current time in zones ~74
The current time in one or more places, each with the zone it resolved to and the local date, time and offset, under one UTC instant. Accepts IANA zones, cities, countries and abbreviations.
| Name | Type | Req | Description |
|---|---|---|---|
| zones | array | – | Places or IANA zones, e.g. ['Warsaw','New York','India'] |
No output schema declared.
No examples provided.
overlap Daily working-hours overlap ~117
The window each day when every listed place is inside working hours. Computed on a real date, so a DST week that widens or narrows the overlap is reflected.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date to compute on, YYYY-MM-DD, default today |
| work_end | string | – | Local working day end, default 17:00 |
| work_start | string | – | Local working day start, default 09:00 |
| zones | array | yes | Places, e.g. ['Warsaw','New York','Bangalore'] |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/scheduling MCP server?
io.github.theluckystrike/scheduling is an MCP server listed in the public MCP registry as io.github.theluckystrike/scheduling. Meeting scheduling across time zones: slot finding, DST checks, .ics invites. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/scheduling).
Is the io.github.theluckystrike/scheduling MCP server safe to use?
io.github.theluckystrike/scheduling scores 84 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 io.github.theluckystrike/scheduling MCP server expose?
io.github.theluckystrike/scheduling exposes 11 tools: license_status, license_activate, now, convert_time, overlap, and 6 more. Their descriptions and schemas cost roughly 1,566 tokens of context every time the server is loaded.
Does the io.github.theluckystrike/scheduling MCP server require authentication?
Yes. io.github.theluckystrike/scheduling 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 io.github.theluckystrike/scheduling MCP server still maintained?
io.github.theluckystrike/scheduling is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.