io.github.dcadolph/vamoose
OCI · GHCR.IO/DCADOLPH/VAMOOSE:V0.35.0
Calendar workflow engine for time off, approvals, and quick actions on any calendar backend.
Available components
Last scanned (23 hours ago)
Scores higher than 71% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 114 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1379 tokens (~91/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (11)
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (5)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 23 Oct 26 −5
- Source repository: pass → fail ▼ security
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 5 Nov 2026 · Analysed oci/ghcr.io/dcadolph/vamoose:v0.35.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
cancel_hold ~53
Cancel a hold and notify its attendees.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Hold id; omit for the most recent hold |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
No output schema declared.
No examples provided.
create_event ~115
Create a quick calendar event, optionally inviting attendees.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | string | – | Comma-separated attendee emails to invite |
| end | string | yes | End date as YYYY-MM-DD or an RFC3339 time |
| free | boolean | – | Show the event as free instead of busy |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
| start | string | yes | Start date as YYYY-MM-DD or an RFC3339 time |
| subject | string | yes | Event subject |
No output schema declared.
No examples provided.
create_workflow ~99
Create or replace a reusable user workflow from a JSON definition, so it can then be previewed and run by name. The definition is validated and rejected with the reason if invalid. Model it on the built-ins from list_workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| definition | string | yes | The workflow as a JSON object with a name, description, and steps. Step verbs are hold, approve, notify, note, away, event, cancel, message, and wait. |
No output schema declared.
No examples provided.
leave_balance ~42
Show remaining time off read from the configured HR system.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Date to check the balance as of, YYYY-MM-DD; omit for today |
No output schema declared.
No examples provided.
list_schedules ~20
List the recurring workflow schedules and when each next runs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_workflows ~43
List every workflow that can be run, built-in and user-defined, with its description. Call this first to discover what run_workflow and preview_workflow can run.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
preview_workflow ~183
Show the plan a workflow would carry out for a date window, without creating or changing anything. Use this to explain what will happen before calling run_workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | string | – | Comma-separated attendees, for an event workflow |
| end | string | – | End date as YYYY-MM-DD; overrides the phrase |
| manager | string | – | Approver email for a directory-less backend |
| phrase | string | – | Date phrase like "next week" or "tomorrow" |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
| start | string | – | Start date as YYYY-MM-DD; overrides the phrase |
| subject | string | – | Event subject; defaults per workflow |
| workflow | string | yes | Workflow name, e.g. pto, notify-only, away (see list_workflows) |
No output schema declared.
No examples provided.
promote_to_team ~57
Add the team as optional attendees to an approved hold.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Hold id; omit for the most recent hold |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
No output schema declared.
No examples provided.
request_time_off ~124
Create a time-off hold shown as free and invite the manager to approve it.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | End date as YYYY-MM-DD or an RFC3339 time |
| manager | string | – | Manager email; omit to resolve from the directory |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
| start | string | yes | Start date as YYYY-MM-DD or an RFC3339 time |
| subject | string | yes | Event subject |
| watch | boolean | – | Auto-promote to the team once approved |
No output schema declared.
No examples provided.
run_workflow ~213
Run a named workflow over a date phrase or explicit dates: it creates the hold and runs the steps up to any approval gate. Set watch so the daemon advances it once approved. Prefer preview_workflow first.
| Name | Type | Req | Description |
|---|---|---|---|
| attendees | string | – | Comma-separated attendees, for an event workflow |
| end | string | – | End date as YYYY-MM-DD; overrides the phrase |
| manager | string | – | Approver email for a directory-less backend |
| phrase | string | – | Date phrase like "next week" or "tomorrow" |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
| start | string | – | Start date as YYYY-MM-DD; overrides the phrase |
| subject | string | – | Event subject; defaults per workflow |
| watch | boolean | – | Watch for approval so the daemon advances the workflow once the manager accepts |
| workflow | string | yes | Workflow name, e.g. pto, notify-only, away (see list_workflows) |
No output schema declared.
No examples provided.
schedule_workflow ~153
Schedule a workflow to rerun on an interval, such as weekly. The daemon fires it, resolving the date phrase fresh each run. Intervals are Go durations, so weekly is 168h.
| Name | Type | Req | Description |
|---|---|---|---|
| every | string | yes | Interval between runs as a Go duration, e.g. 168h for weekly |
| manager | string | – | Approver email for a directory-less backend |
| phrase | string | yes | Date phrase resolved each run, e.g. "next week" |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
| subject | string | – | Event subject |
| workflow | string | yes | Workflow name to rerun (see list_workflows) |
No output schema declared.
No examples provided.
set_away ~97
Mark yourself out of office over a date range, with no approval.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | End date as YYYY-MM-DD or an RFC3339 time |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
| start | string | yes | Start date as YYYY-MM-DD or an RFC3339 time |
| subject | string | – | Event subject (default: Out of office) |
No output schema declared.
No examples provided.
team_coverage ~81
Show who already has time off booked in a window, before booking or approving more.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Explicit end date as YYYY-MM-DD; overrides the phrase |
| phrase | string | – | Date phrase such as "next week"; omit for next week |
| start | string | – | Explicit start date as YYYY-MM-DD; overrides the phrase |
No output schema declared.
No examples provided.
time_off_status ~58
Show whether the manager has approved the latest or given hold.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Hold id; omit for the most recent hold |
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
No output schema declared.
No examples provided.
whoami ~41
Print the signed-in user, manager, and resolved team.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | Calendar provider: graph, google, icloud, or caldav |
No output schema declared.
No examples provided.
How do I install the io.github.dcadolph/vamoose MCP server?
io.github.dcadolph/vamoose runs locally as a container image, launched with docker run --rm -i -e VAMOOSE_PROVIDER -e VAMOOSE_TIMEZONE ghcr.io/dcadolph/vamoose:v0.35.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/dcadolph/vamoose:v0.35.0
claude mcp add dcadolph-vamoose -- docker run --rm -i -e VAMOOSE_PROVIDER -e VAMOOSE_TIMEZONE ghcr.io/dcadolph/vamoose:v0.35.0 mcp
This image reads VAMOOSE_PROVIDER and VAMOOSE_TIMEZONE. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the io.github.dcadolph/vamoose MCP server?
io.github.dcadolph/vamoose is an MCP server listed in the public MCP registry as io.github.dcadolph/vamoose. Calendar workflow engine for time off, approvals, and quick actions on any calendar backend. This page covers its container image (ghcr.io/dcadolph/vamoose:v0.35.0).
Is the io.github.dcadolph/vamoose MCP server safe to use?
io.github.dcadolph/vamoose scores 48 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 io.github.dcadolph/vamoose MCP server expose?
io.github.dcadolph/vamoose exposes 15 tools: whoami, request_time_off, time_off_status, promote_to_team, cancel_hold, and 10 more. Their descriptions and schemas cost roughly 1,379 tokens of context every time the server is loaded.
Is the io.github.dcadolph/vamoose MCP server still maintained?
io.github.dcadolph/vamoose is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.dcadolph/vamoose MCP server under?
io.github.dcadolph/vamoose declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the io.github.dcadolph/vamoose MCP server?
VerifyMCP ran 11 checks on io.github.dcadolph/vamoose, covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.dcadolph/vamoose: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.