morgenmcp@0.5.0
VERIFIED· not startedPublisher claims: "Unofficial MCP server for Morgen: unified calendar, scheduling, and task management (Google Calendar, Outlook, iCloud)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MORGEN_API_KEYConfiguration, not credentials: MORGENMCP_DATA_DIR, MORGENMCP_READ_ONLY- Where it talks to
- no vendor host named in the codeAlso morgen.so, githubusercontent.com, slsa.dev — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names morgen.so, githubusercontent.com, slsa.dev as well as its own vendor. The guard injects MORGEN_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-12 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
echo 'MORGEN_API_KEY=...' > .env && export UV_ENV_FILE=.env # Configure API key (uv only)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…y/Application Support/morgenmcp/id_store/` (via `platformdirs.user_data_dir`), `chmod 0o700` after setup — persisted entries hold raw Morgen IDs, which decode to emai…Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.- Keep `.env` and credentials local; never add them to version control.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Requires MORGEN_API_KEY in .env or environment.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for morgenmcp@0.5.0 as of 3d ago. This is the package itself, not its dependencies.