Whenly — group meeting scheduler for AI agents
REMOTE · WHENLY.NOTDOWN-APP.WORKERS.DEV · SCANNED SEP 27
Find a time a group can meet: no-login availability poll that picks the best meeting slot.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 300 tokens (~150/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 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.
remote · whenly.notdown-app.workers.dev
claude mcp add --transport http dev-workers-notdown-app-whenly-group-meeting-sch 'https://whenly.notdown-app.workers.dev/mcp'
{
"mcpServers": {
"dev-workers-notdown-app-whenly-group-meeting-sch": {
"url": "https://whenly.notdown-app.workers.dev/mcp"
}
}
} {
"servers": {
"dev-workers-notdown-app-whenly-group-meeting-sch": {
"type": "http",
"url": "https://whenly.notdown-app.workers.dev/mcp"
}
}
} [mcp_servers.dev-workers-notdown-app-whenly-group-meeting-sch] url = "https://whenly.notdown-app.workers.dev/mcp"
{
"$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 mcp add dev-workers-notdown-app-whenly-group-meeting-sch --url 'https://whenly.notdown-app.workers.dev/mcp' --transport streamable-http
mcp_servers:
dev-workers-notdown-app-whenly-group-meeting-sch:
url: "https://whenly.notdown-app.workers.dev/mcp" {
"McpServers": {
"dev-workers-notdown-app-whenly-group-meeting-sch": {
"Transport": "http",
"Url": "https://whenly.notdown-app.workers.dev/mcp"
}
}
} assistant mcp add dev-workers-notdown-app-whenly-group-meeting-sch -t streamable-http -u 'https://whenly.notdown-app.workers.dev/mcp'
{
"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.
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.
- 26 Sept 26 +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.
- 25 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
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
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 27 Sept 2026 · Probed https://whenly.notdown-app.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=notdown-app.workers.dev | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ced6a57b0254c5df13a021c1a6d76d70 |
| SANs: notdown-app.workers.dev, *.notdown-app.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 whenly.notdown-app.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whenly.notdown-app.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://whenly.notdown-app.workers.dev/mcp | Served over HTTP | 200 |
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 →
create_event ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dates | array | yes | 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 | yes | 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"). |
No output schema declared.
No examples provided.
get_results ~73
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).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The 7-char event code from the event_url (the part after /e/). |
No output schema declared.
No examples provided.
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.