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.
Available components
Last scanned (11 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Productivity and Notes
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 yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 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
- 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
- 4 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Aug 26 0
- Stability: 0.97 → pass security
- 26 Aug 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
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
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 25 Oct 2026 · Probed https://meetwhen.perch-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=perch-app.workers.dev | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e435da77a35b729a1301edcf7506f15b |
| SANs: perch-app.workers.dev, *.perch-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 meetwhen.perch-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 Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://meetwhen.perch-app.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://meetwhen.perch-app.workers.dev/mcp | Inconclusive | 404 |
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 ~321
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dates | array | yes | 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 | yes | Event name, e.g. 'Team sync' or 'D&D night' (max 80 chars). |
No output schema declared.
No examples provided.
get_event ~92
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).
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The event id returned by create_event. |
| timezone | string | – | IANA timezone to render the best-time labels in (default UTC). |
No output schema declared.
No examples provided.
How do I install the dev.workers.perch-app.meetwhen/meetwhen MCP server?
dev.workers.perch-app.meetwhen/meetwhen is a hosted endpoint at https://meetwhen.perch-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 · meetwhen.perch-app.workers.dev
claude mcp add --transport http dev-workers-perch-app-meetwhen-meetwhen 'https://meetwhen.perch-app.workers.dev/mcp'
What is the dev.workers.perch-app.meetwhen/meetwhen MCP server?
dev.workers.perch-app.meetwhen/meetwhen is an MCP server listed in the public MCP registry as dev.workers.perch-app.meetwhen/meetwhen. Free no-signup group scheduling (a modern When2meet): share one link, find a time for everyone. This page covers its hosted endpoint (https://meetwhen.perch-app.workers.dev/mcp).
Is the dev.workers.perch-app.meetwhen/meetwhen MCP server safe to use?
dev.workers.perch-app.meetwhen/meetwhen scores 18 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 dev.workers.perch-app.meetwhen/meetwhen MCP server expose?
dev.workers.perch-app.meetwhen/meetwhen exposes 2 tools: create_event, get_event. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.
Does the dev.workers.perch-app.meetwhen/meetwhen MCP server require authentication?
Its publisher declares no required credentials for dev.workers.perch-app.meetwhen/meetwhen. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the dev.workers.perch-app.meetwhen/meetwhen MCP server still maintained?
dev.workers.perch-app.meetwhen/meetwhen is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.