MeetZone
REMOTE · MEETZONE-API.MIKE-TUSA.WORKERS.DEV
Find meeting times that overlap working hours across IANA time zones, DST-aware. Free tier.
Available components
Last scanned (2 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 19 Oct 2026.
Category Maps and Location
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 521 tokens (~260/item across 2 items; 2 tools + 0 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 Management13
- Stability observed for 4 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 19 Oct 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 65
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 19 Oct 2026 · Probed https://meetzone-api.mike-tusa.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mike-tusa.workers.dev | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f05aa95d8943eeed0e4e86dd1f6f1e02 |
| SANs: mike-tusa.workers.dev, *.mike-tusa.workers.dev | ||||||
| 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 meetzone-api.mike-tusa.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meetzone-api.mike-tusa.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://meetzone-api.mike-tusa.workers.dev/mcp | Inconclusive | 405 |
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 →
find_meeting_overlap Find meeting times that overlap working hours across time zones ~251
Given 2-5 IANA time zones (e.g. America/New_York, Europe/London, Asia/Tokyo), a local working window applied in every zone (default 09:00-17:00) and up to 7 calendar days, returns up to 5 ranked meeting slots in UTC with each zone's local time, UTC offset and abbreviation, DST-aware, plus an optional ICS event for the top slot. Read-only, pure computation (no calendars are read). Same engine as POST /v1/overlap on the free BASIC plan.
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | – | Dates YYYY-MM-DD (default: today + 6 days, UTC) |
| duration_minutes | integer | – | Meeting length in minutes (default 30) |
| include_ics | boolean | – | Include an ICS VEVENT for the top slot (default true) |
| limit | integer | – | Max ranked slots (default 5, max 5) |
| work_hours | object | – | Local working window applied in each zone (default 09:00-17:00) |
| zones | array | yes | IANA zone ids, e.g. ["America/New_York","Europe/London"] |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| ics | string | – | – |
| ok | boolean | yes | – |
| plan_note | string | – | – |
| query | object | – | – |
| slots | array | yes | – |
No examples provided.
search_timezones Search IANA time zones by city, country or abbreviation ~131
Look up IANA time zone ids by city, country, alias or a raw IANA id (e.g. "tokyo", "india", "PST"). Returns up to 5 matches; with a date, also each zone's UTC offset and abbreviation on that day. Read-only. Same engine as GET /v1/zones/search on the free BASIC plan.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional YYYY-MM-DD for offsets/abbreviations |
| limit | integer | – | Max results (default 5) |
| q | string | yes | Search text, e.g. "london" |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| ok | boolean | yes | – |
| plan_note | string | – | – |
| query | string | – | – |
| zones | array | yes | – |
No examples provided.
How do I install the MeetZone MCP server?
MeetZone is a hosted endpoint at https://meetzone-api.mike-tusa.workers.dev/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.
remote · meetzone-api.mike-tusa.workers.dev
claude mcp add --transport http dev-workers-mike-tusa-meetzone-api-meetzone-api 'https://meetzone-api.mike-tusa.workers.dev/mcp'
What is the MeetZone MCP server?
MeetZone is an MCP server listed in the public MCP registry as dev.workers.mike-tusa.meetzone-api/meetzone-api. Find meeting times that overlap working hours across IANA time zones, DST-aware. Free tier. This page covers its hosted endpoint (https://meetzone-api.mike-tusa.workers.dev/mcp).
Is the MeetZone MCP server safe to use?
MeetZone scores 67 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 MeetZone MCP server expose?
MeetZone exposes 2 tools: find_meeting_overlap, search_timezones. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.
Does the MeetZone MCP server require authentication?
No. We connected to MeetZone without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MeetZone MCP server still maintained?
MeetZone is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.