# Whenly — group meeting scheduler for AI agents (remote · whenly.notdown-app.workers.dev)

Find a time a group can meet: no-login availability poll that picks the best meeting slot.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `whenly.notdown-app.workers.dev`: 72/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-notdown-app-whenly-group-meeting-scheduler/whenly.md), [page](https://verifymcp.io/servers/dev-workers-notdown-app-whenly-group-meeting-scheduler/whenly)

## Channel facts

- Endpoint: `https://whenly.notdown-app.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-09-27.

- **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 check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 300 tokens (~150/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
- **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 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Whenly — group meeting scheduler for AI agents MCP server?

Whenly — group meeting scheduler for AI agents is a hosted endpoint at https://whenly.notdown-app.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-notdown-app-whenly-group-meeting-sch 'https://whenly.notdown-app.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-whenly-group-meeting-sch": {
      "url": "https://whenly.notdown-app.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-notdown-app-whenly-group-meeting-sch": {
      "type": "http",
      "url": "https://whenly.notdown-app.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-notdown-app-whenly-group-meeting-sch]
url = "https://whenly.notdown-app.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-notdown-app-whenly-group-meeting-sch": {
      "type": "remote",
      "url": "https://whenly.notdown-app.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-notdown-app-whenly-group-meeting-sch --url 'https://whenly.notdown-app.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-notdown-app-whenly-group-meeting-sch:
    url: "https://whenly.notdown-app.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-notdown-app-whenly-group-meeting-sch": {
      "Transport": "http",
      "Url": "https://whenly.notdown-app.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-notdown-app-whenly-group-meeting-sch -t streamable-http -u 'https://whenly.notdown-app.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-whenly-group-meeting-sch": {
      "type": "http",
      "url": "https://whenly.notdown-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-09-26 (score 72, +1)

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

### 2026-09-25 (score 71, 0)

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

### 2026-09-24 (score 71, +1)

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

### 2026-09-22 (score 70, +1)

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

### 2026-09-20 (score 69, +1)

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

### 2026-09-18 (score 68, +1)

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

### 2026-09-15 (score 67, +1)

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

### 2026-09-13 (score 66, +1)

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

## MCP tools (2)

### `create_event` (~227 tokens)

Create a free group-scheduling event (like When2meet/Doodle) and get a shareable link. Use this when a human asks you to find a time for a group to meet. Returns a public event_url anyone can open (no login) to mark when they're free, plus an admin note. Then poll get_results to see the best time.

Input parameters:

- `dates` (array, required): Candidate dates to consider, each as YYYY-MM-DD. 1–31 dates.
- `end_hour` (number): Latest hour to consider, 1–24 (default 17 = 5 PM).
- `slot_minutes` (number): Time-slot granularity: 30 or 60 (default 60).
- `start_hour` (number): Earliest hour to consider, 0–23 (default 9 = 9 AM).
- `title` (string, required): What the meeting is for, e.g. "Team sync" or "Dinner with friends".
- `tz` (string): Timezone label shown to participants, e.g. "US/Eastern" (default "local").

### `get_results` (~73 tokens)

Read the current responses for a Whenly event and get the best meeting times (the slots where the most people are free). Pass the event slug (the code after /e/ in the event_url).

Input parameters:

- `slug` (string, required): The 7-char event code from the event_url (the part after /e/).

## Diagnostics

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

## Score history

- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61

## Common questions

### What is the Whenly — group meeting scheduler for AI agents MCP server?

Whenly — group meeting scheduler for AI agents is an MCP server listed in the public MCP registry as dev.workers.notdown-app.whenly/group-meeting-scheduler. Find a time a group can meet: no-login availability poll that picks the best meeting slot. This page covers its hosted endpoint (https://whenly.notdown-app.workers.dev/mcp).

### Is the Whenly — group meeting scheduler for AI agents MCP server safe to use?

Whenly — group meeting scheduler for AI agents scores 72 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 Whenly — group meeting scheduler for AI agents MCP server expose?

Whenly — group meeting scheduler for AI agents exposes 2 tools: create_event, get_results. Their descriptions and schemas cost roughly 300 tokens of context every time the server is loaded.

### Does the Whenly — group meeting scheduler for AI agents MCP server require authentication?

No. We connected to Whenly — group meeting scheduler for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Whenly — group meeting scheduler for AI agents MCP server still maintained?

Whenly — group meeting scheduler for AI agents is still listed as active in the MCP registry. We last reached this channel on 27 September 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://whenly.notdown-app.workers.dev/mcp
- Website: https://whenly.notdown-app.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-notdown-app-whenly-group-meeting-scheduler/whenly.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-notdown-app-whenly-group-meeting-scheduler/whenly.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-notdown-app-whenly-group-meeting-scheduler/whenly