mcp-registry/dev.workers.notdown-app.whenly/schedule · v0.1.0
Also listed as mcp-registry/dev.workers.notdown-app.whenly/group-meeting-scheduler
As of 2026-10-27 06:16 UTC, the Workers Notdown App Whenly Schedule MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.2 hours.
Agent creates a group-scheduling poll, gets a shareable link, and reads the best meeting time.
Point your MCP client at this streamable-http endpoint: https://whenly.notdown-app.workers.dev/mcp
2 of 2 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.workers.notdown-app.whenly%2Fschedule/fixes
{
"name": "create_event",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"title",
"dates"
],
"properties": {
"tz": {
"type": "string",
"description": "Timezone label shown to participants, e.g. \"US/Eastern\" (default \"local\")."
},
"dates": {
"type": "array",
"items": {
"type": "string"
},
"description": "Candidate dates to consider, each as YYYY-MM-DD. 1–31 dates."
},
"title": {
"type": "string",
"description": "What the meeting is for, e.g. \"Team sync\" or \"Dinner with friends\"."
},
"end_hour": {
"type": "number",
"description": "Latest hour to consider, 1–24 (default 17 = 5 PM)."
},
"start_hour": {
"type": "number",
"description": "Earliest hour to consider, 0–23 (default 9 = 9 AM)."
},
"slot_minutes": {
"type": "number",
"description": "Time-slot granularity: 30 or 60 (default 60)."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "get_results",
"description": "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).",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"description": "The 7-char event code from the event_url (the part after /e/)."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.workers.notdown-app.whenly/schedule"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.workers.notdown-app.whenly/schedule"}) over MCP.
create_event ~296 tokensget_results ~109 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.workers.notdown-app.whenly%2Fschedule?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.workers.notdown-app.whenly%2Fschedule?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.workers.notdown-app.whenly%2Fschedule.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.workers.notdown-app.whenly%2Fschedule.svg :target: https://glimind.com/server/mcp-registry%2Fdev.workers.notdown-app.whenly%2Fschedule?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:88570859e676ffbf…, first seen 2026-10-17, included at leaf 10942 of 77,796. Version history · verify what your client received.
Compare: most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 06:16 UTC, the Workers Notdown App Whenly Schedule MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 26.2 hours.
Workers Notdown App Whenly Schedule MCP server advertises 2 tools, including create_event, get_results.
Point your MCP client at this streamable-http endpoint: https://whenly.notdown-app.workers.dev/mcp
Glimind scanned all 2 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.