things3-mcp-gtd@2.0.1
CAUTION· not startedPublisher claims: "Local MCP server for Things 3 on macOS" 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: Caution 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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-13 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: Access to sensitive file paths; Collapsed <details> block carrying instructions; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
Provides type-safe, validated configuration with automatic .env file loading.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary><strong>Already using Things MCP 1.x?</strong></summary> Review the [upgrade notes](https://github.com/Chevalicious/things3-mcp-gtd/blob/v2.0.1/docs/REFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.2. .env file in the server's working directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Prefer the launcher environment or .env over the legacy file."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."""Application settings with validation and .env support.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.in communicate() cleanup. This helper closes all pipes before kill andFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.D-state that survives SIGKILL. CPython's subprocess.run() then hangs foreverFix: 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.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 things3-mcp-gtd@2.0.1 as of 15 h ago. This is the package itself, not its dependencies.
What would make this Verified
4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim chevalicious: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.