# dev.workers.perch-app.meetwhen/meetwhen (remote · meetwhen.perch-app.workers.dev)

Free no-signup group scheduling (a modern When2meet): share one link, find a time for everyone.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `meetwhen.perch-app.workers.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-perch-app-meetwhen-meetwhen/meetwhen.md), [page](https://verifymcp.io/servers/dev-workers-perch-app-meetwhen-meetwhen/meetwhen)

## Channel facts

- Endpoint: `https://meetwhen.perch-app.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 450 tokens (~225/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**: 17/100
  - Stability observed for 5 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-workers-perch-app-meetwhen-meetwhen https://meetwhen.perch-app.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.dev-workers-perch-app-meetwhen-meetwhen]
url = "https://meetwhen.perch-app.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-perch-app-meetwhen-meetwhen": {
      "type": "remote",
      "url": "https://meetwhen.perch-app.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-perch-app-meetwhen-meetwhen --url https://meetwhen.perch-app.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-perch-app-meetwhen-meetwhen:
    url: "https://meetwhen.perch-app.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-perch-app-meetwhen-meetwhen": {
      "type": "http",
      "url": "https://meetwhen.perch-app.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-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 61)

First indexed and scored.

## MCP tools (2)

### `create_event` (~321 tokens)

Create a free, no-signup group-scheduling event (like When2meet) and get a shareable link. Give it candidate dates and a daily time window; it builds the availability grid. Send the returned url to everyone in the group — each person paints when they're free in their own timezone, and the best overlapping time surfaces automatically. Ideal when a user asks you to 'find a time' or 'set up a poll' for a meeting.

Input parameters:

- `dates` (array, required): Candidate dates as YYYY-MM-DD strings (1-21 days).
- `earliest_hour` (integer): Earliest hour of day to consider, 0-23 (default 9). Ignored when mode='day'.
- `latest_hour` (integer): Latest hour of day to consider, 1-24 (default 17). Must be greater than earliest_hour.
- `mode` (string): 'time' (default): find an overlapping hour within a daily window. 'day': a whole-day poll — respondents just mark which dates work, no time-of-day. Use 'day' when the user only needs to pick a date.
- `slot_minutes` (integer): Granularity of each time slot in minutes (default 30).
- `timezone` (string): IANA timezone the hours are expressed in, e.g. 'America/New_York' (default UTC). Respondents still answer in their own local time.
- `title` (string, required): Event name, e.g. 'Team sync' or 'D&D night' (max 80 chars).

### `get_event` (~92 tokens)

Read the current state of a meetwhen event: how many people responded, who, and the best overlapping time(s) so far. Use the event id returned by create_event (or found in a meetwhen /e/<id> URL).

Input parameters:

- `event_id` (string, required): The event id returned by create_event.
- `timezone` (string): IANA timezone to render the best-time labels in (default UTC).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-perch-app-meetwhen-meetwhen/meetwhen#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 60
- 2026-07-29: 61

## Links

- Remote endpoint: https://meetwhen.perch-app.workers.dev/mcp
- Website: https://meetwhen.perch-app.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-perch-app-meetwhen-meetwhen/meetwhen/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-perch-app-meetwhen-meetwhen/meetwhen/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-perch-app-meetwhen-meetwhen/meetwhen