An MCP server named vamoose that runs in Docker. The description does not explain what tasks or external services it provides.

Use it only when you already know which vamoose functions your workflow needs. The input does not provide enough information to name specific jobs.

Its purpose cannot be determined from the available description. It requires two environment variables to run.

vamoose — MCP server for Claude Code and Codex by dcadolph

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/dcadolph/vamoose

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/mcp/dcadolph/vamoose/vamoose.svg)](https://agentmods.dev/mcp/dcadolph/vamoose/vamoose)

Your own site

<a href="https://agentmods.dev/mcp/dcadolph/vamoose/vamoose"><img src="https://agentmods.dev/badge/mcp/dcadolph/vamoose/vamoose.svg" alt="Measured on agentmods" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

vamoose scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

server.json · 15 lines

What it actually says

{
  "vamoose": {
    "command": "docker",
    "args": [
      "run",
      "-i",
      "--rm",
      "ghcr.io/dcadolph/vamoose:v0.35.0"
    ],
    "env": {
      "VAMOOSE_PROVIDER": "",
      "VAMOOSE_TIMEZONE": ""
    }
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 15 lines scan A 85cca48d7133

Subscribe to this mod's changes

vamoose is an MCP server published in the GitHub repository dcadolph/vamoose (0 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

caldav calendar cli go google-calendar mcp

vamoose

Getting it into your agent

Wrote this? Show the measurements

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

renfield-mcp-calendar

homebutler

gograph

kdbx

backscroll

caldav-mcp