Skills/PyPI/iflow-mcp-markuspfundstein-mcp-obsidian

iflow-mcp-markuspfundstein-mcp-obsidian@0.2.3

CAUTION

Publisher claims: "MCP server to work with Obsidian via the remote REST plugin" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher iflow-iflow · joined 1 days agoInstalls 24Last detonated 1 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-03 and scored it 76/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Prompting user to enter sensitive credentials. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.6sprocessdependency install exit 1
0.7sprocessexec /usr/bin/timeout
0.7sprocessexec .venv/bin/mcp-obsidian
0.7sprocessexited 127: timeout: failed to run command '.venv/bin/mcp-obsidian': No such file or directory
0.7sclaimedno tools/list reply (exit 127)
0.7sprocessscript backend runs setup only

Static findings

CRITICAL
Prompting user to enter sensitive credentialsopenapi.yaml:58 · Prompting user to enter sensitive credentials — social engineeringFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST03

No other findings across 3,506 lines in 14 files.

What would make this Verified

4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Prompting user to enter sensitive credentials≈ +9 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  2. Unclaimed publisher≈ +8 on the totalClaim iflow-iflow: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim iflow-iflow