# MeetZone (remote · meetzone-api.mike-tusa.workers.dev)

Find meeting times that overlap working hours across IANA time zones, DST-aware. Free tier.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-19

## Components

- remote · `meetzone-api.mike-tusa.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-mike-tusa-meetzone-api-meetzone-api/meetzone-api.md), [page](https://verifymcp.io/servers/dev-workers-mike-tusa-meetzone-api-meetzone-api/meetzone-api)

## Channel facts

- Endpoint: `https://meetzone-api.mike-tusa.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-10-19.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-workers-mike-tusa-meetzone-api-meetzone-api 'https://meetzone-api.mike-tusa.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-meetzone-api-meetzone-api": {
      "url": "https://meetzone-api.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-mike-tusa-meetzone-api-meetzone-api": {
      "type": "http",
      "url": "https://meetzone-api.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-mike-tusa-meetzone-api-meetzone-api]
url = "https://meetzone-api.mike-tusa.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-mike-tusa-meetzone-api-meetzone-api": {
      "type": "remote",
      "url": "https://meetzone-api.mike-tusa.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-mike-tusa-meetzone-api-meetzone-api --url 'https://meetzone-api.mike-tusa.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-mike-tusa-meetzone-api-meetzone-api:
    url: "https://meetzone-api.mike-tusa.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-mike-tusa-meetzone-api-meetzone-api": {
      "Transport": "http",
      "Url": "https://meetzone-api.mike-tusa.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-mike-tusa-meetzone-api-meetzone-api -t streamable-http -u 'https://meetzone-api.mike-tusa.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-mike-tusa-meetzone-api-meetzone-api": {
      "type": "http",
      "url": "https://meetzone-api.mike-tusa.workers.dev/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-10-19 (score 67, +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.

### 2026-10-17 (score 66, +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.

### 2026-10-16 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 65)

First indexed and scored.

## MCP tools (2)

### `find_meeting_overlap` (~251 tokens)

Find meeting times that overlap working hours across time zones

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.

Input parameters:

- `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, required): IANA zone ids, e.g. ["America/New_York","Europe/London"]

Output parameters:

- `count` (number)
- `ics` (string)
- `ok` (boolean)
- `plan_note` (string)
- `query` (object)
- `slots` (array)

### `search_timezones` (~131 tokens)

Search IANA time zones by city, country or abbreviation

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.

Input parameters:

- `date` (string): Optional YYYY-MM-DD for offsets/abbreviations
- `limit` (integer): Max results (default 5)
- `q` (string, required): Search text, e.g. "london"

Output parameters:

- `count` (number)
- `ok` (boolean)
- `plan_note` (string)
- `query` (string)
- `zones` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-mike-tusa-meetzone-api-meetzone-api/meetzone-api#diagnostics

## Score history

- 2026-10-19: 67
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65

## Common questions

### 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.

## Links

- Remote endpoint: https://meetzone-api.mike-tusa.workers.dev/mcp
- Website: https://meetzone-api.mike-tusa.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-mike-tusa-meetzone-api-meetzone-api/meetzone-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-mike-tusa-meetzone-api-meetzone-api/meetzone-api.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-mike-tusa-meetzone-api-meetzone-api/meetzone-api