when-free
PYPI · WHEN-FREE
Which days and times am I free? Reads your calendar feeds and answers with the slots you can offer.
Available components
Last scanned (3 hours ago)
Scores higher than 67% of PyPI servers
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to YauhenBichel/when-free). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 740 tokens (~246/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 23 Oct 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.
- 22 Oct 26 −12
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.27 ▲ functional
- 20 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 17 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 14 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 50
First indexed and scored.
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 23 Oct 2026 · Analysed pypi/when-free@0.4.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | YauhenBichel/when-free |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/YauhenBichel/when-free/.github/workflows/release.yml@refs/tags/v0.4.1 |
| Rekor log index | 3162637971 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6c576bc6aba3cc0d1c673d81ed7b3d651ee6cd8cd70b0739b4fcc99b37a62a04 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_calendars ~63
Check that the user's calendars can be read. Returns each calendar's name, how many events it holds and how many block time in the next 14 days. Use it when free_slots fails or to confirm the setup. Returns no event details and no calendar addresses.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
free_slots ~521
Find when the user is free. Reads the user's own calendars and returns, for each day asked about, the time ranges with no events, in the user's time zone. Use it when the user needs to offer, choose or confirm times for a meeting, call or interview. Say which days in one of three ways: `days` (explicit dates), `from` and `to` (a range), or `message` (text such as a recruiter's email, from which the days and a daily window are read). With none of them, the next working days are returned. It never guesses: if a calendar cannot be read it returns an error instead of slots, and days already past are listed under `past`. It only reads. It cannot create or change events.
| Name | Type | Req | Description |
|---|---|---|---|
| all_day_busy | boolean | – | Treat whole-day events as busy. Default false. |
| buffer_minutes | integer | – | Time kept free before and after every event. Default: the user's setting, usually 15. |
| days | string | – | Specific days, comma-separated. ISO dates are safest: "2026-10-05, 2026-10-06". Also understood: "Thu 1 Oct, Fri 2 Oct", "tomorrow", "next week". |
| from | string | – | First day of a range, YYYY-MM-DD. Default: today. |
| hours | string | – | The part of the day to offer, HH:MM-HH:MM, for example "10:00-16:00", or "morning", "afternoon", "evening". Default: the user's configured hours. |
| include_busy | boolean | – | Also return what blocks each day, with event titles. Titles are private: ask only if the user wants to see them. Default false. |
| message | string | – | Text to read the proposed days and hours from, for example the email asking for availability. Explicit dates are read, and when there are none, phrases relative to today: "tomorrow", "Thursday", "nex… |
| min_minutes | integer | – | Shortest slot to return, in minutes. Set it to the meeting length. Default: the user's setting, usually 60. |
| timezone | string | – | Time zone for the answer, like "Europe/London". Default: the user's zone. |
| to | string | – | Last day of a range, YYYY-MM-DD. |
| weekends | boolean | – | Include Saturday and Sunday in a range. Default false. |
No output schema declared.
No examples provided.
status ~100
Whether the user is free right now, until when, and their next free slot. Use it for "am I free now?", "when is my next gap?" or before interrupting the user. Returns no event titles.
| Name | Type | Req | Description |
|---|---|---|---|
| min_minutes | integer | – | Shortest gap that counts as the next free slot. Default: the user's setting. |
| timezone | string | – | Time zone for the answer, like "Europe/London". Default: the user's zone. |
No output schema declared.
No examples provided.
How do I install the when-free MCP server?
when-free runs locally as a PyPI package, launched with uvx when-free. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · when-free
claude mcp add yauhenbichel-when-free -- uvx when-free
What is the when-free MCP server?
when-free is an MCP server listed in the public MCP registry as io.github.YauhenBichel/when-free. Which days and times am I free? Reads your calendar feeds and answers with the slots you can offer. This page covers its PyPI package (when-free).
Is the when-free MCP server safe to use?
when-free scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. Its build provenance is signed and verified. 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 when-free MCP server expose?
when-free exposes 3 tools: free_slots, status, check_calendars. Their descriptions and schemas cost roughly 684 tokens of context every time the server is loaded.
Is the when-free MCP server still maintained?
when-free is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the when-free MCP server under?
when-free declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.