vikunja-mcp@0.10.3
VERIFIED· not startedPublisher claims: "MCP server for Vikunja task management" 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
PYPI_TOKENVIKUNJA_CLOUD_TOKENVIKUNJA_TOKENConfiguration, not credentials: VIKUNJA_DEBUG, VIKUNJA_INSTANCES, VIKUNJA_MCP_CONFIG_DIR, VIKUNJA_MCP_ENCRYPTION_KEY, VIKUNJA_PERF, VIKUNJA_URL- Where it talks to
- no vendor host named in the code
- What we saw when it ran
- 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. It asks for PYPI_TOKEN, VIKUNJA_CLOUD_TOKEN, VIKUNJA_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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-20 and scored it 90/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
what has been refused three or more times; that list exists to kill things, not to do them.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.depth, loudest first. The answer is do / shrink / park / kill — never defer again."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."one: do it, shrink it, park it, or kill it — but do not defer again.",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# loudly for a kill decision instead of sinking.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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
Not checked against OSV yet; the weekly check has not reached this version.