Skills/PyPI/timedoctor-mcp

timedoctor-mcp@1.3.0

CAUTION· not started

Publisher claims: "MCP Server for extracting Time Doctor time tracking data via AI assistants" Observed in sandbox: sends data to cdn.playwright.dev.

Registry PyPI (MCP server)Publisher frifster · publishing for 380 daysInstalls 65Last detonated 2 h ago

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 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
TD_PASSWORDConfiguration, not credentials: BROWSER_TIMEOUT, CONFIG_PATH, HEADLESS, PYTHON_PATH, TD_BASE_URL, TD_EMAIL, USE_CACHE
Where it talks to
timedoctor.com (its own)
What we saw when it ran
no credential files read · contacted cdn.playwright.dev (undeclared)
What we could not test
server startup · the tool list · tool behavior

Find out what these hosts are first. In the honeypot it contacted cdn.playwright.dev, which nothing in the package names as its own. If that is the vendor's service, fine; if you cannot place it, do not connect it.

$vet-skills run --net cdn.playwright.dev -- uvx timedoctor-mcp

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 (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-19 and scored it 51/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; Access to sensitive file paths; Access to sensitive file paths. Summary: sends data to cdn.playwright.dev.

Behavior trace

Honeypot run · 21 s · 3 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
7.9sfilesystemread ~/.cache/ms-playwright/.links · ~/.cache/ms-playwright/.links/012449f02ce4f07fac91ce0c44bf51274bc3c21b · ~/.cache/ms-playwright outside project
7.9sfilesystemwrote ~/.cache/ms-playwright/.links/012449f02ce4f07fac91ce0c44bf51274bc3c21b
7.9snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
7.9snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
7.9snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
7.9snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
7.9snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
7.9sprocessexec /usr/bin/awk
7.9sprocessexec /app/apps/web/node_modules/.bin/playwright
7.9sprocessexec /usr/bin/sed
7.9sprocessexec /usr/bin/dirname
7.9sprocessexec /usr/bin/uname
7.9sprocessexec /usr/bin/cp
7.9sprocessexec /usr/bin/mkdir
7.9sprocessinstall script run in the sandbox
8.0snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
8.0snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
8.0snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
8.0snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
8.0snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
8.0sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'
8.4sprocessdependency install exit 1 ·
8.4sclaimednot started: dependency install failed (exit 1); the server itself was not observed
8.4sprocessscript backend runs setup only
13sprocesssecond launch, clock +45 days, CI unset
20sfilesystemread ~/.cache/ms-playwright/.links · ~/.cache/ms-playwright/.links/012449f02ce4f07fac91ce0c44bf51274bc3c21b · ~/.cache/ms-playwright outside project
20sfilesystemwrote ~/.cache/ms-playwright/.links/012449f02ce4f07fac91ce0c44bf51274bc3c21b
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20sprocessexec /usr/bin/awk
20sprocessexec /app/apps/web/node_modules/.bin/playwright
20sprocessexec /usr/bin/sed
20sprocessexec /usr/bin/dirname
20sprocessexec /usr/bin/uname
20sprocessexec /usr/bin/mkdir
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20snetworkCONNECT tcp://cdn.playwright.dev:443 · not in the allow-list, refused
20sprocessexited 1: ModuleNotFoundError: No module named 'setuptools'

Static findings

HIGH
Access to sensitive file pathsbuild-docker.sh:25 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "⚠️ Warning: .env file not found"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsbuild-docker.sh:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ ! -f .env ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsbuild-docker.sh:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Check if .env existsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdocker-mcp-wrapper.sh:6 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load environment from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsbuild-docker.sh:27 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "You'll need to create .env with:"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsinstall.sh:56 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Create .env if it doesn't existFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsinstall.sh:58 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "Creating .env file..."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsinstall.sh:57 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ ! -f ".env" ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsexample.py:225 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint(" Edit .env and set TD_EMAIL and TD_PASSWORD\n")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsinstall.sh:59 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Destructive file system command detecteddocker-mcp-wrapper.sh:12 · Destructive file system command detecteddocker run -i --rm \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Access to sensitive file pathsexample.py:224 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint("\n⚠️ WARNING: Please configure your credentials in .env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdocker-mcp-wrapper.sh:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesexport $(cat "$(dirname "$0")/.env" | grep -v '^#' | xargs)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdocker-mcp-wrapper.sh:7 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ -f "$(dirname "$0")/.env" ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:11 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Check if .env existsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup-with-uv.sh:78 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho " nano .env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/scraper.py:66 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_path = project_dir / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/README.md:144 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescp .env.example .env # Add your credentialsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:14 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "Please create .env with your credentials:"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/scraper.py:104 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesraise ValueError("TD_EMAIL and TD_PASSWORD must be set in .env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:24 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Read credentials from .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Destructive file system command detectedDockerfile:8 · Destructive file system command detected&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif [ ! -f .env ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssetup_mcp.sh:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesecho "⚠️ .env file not found!"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
LOW
Account verification phishing language detectedPUBLISHING.md:9 · Account verification phishing language detected · informational: not an instruction file- Verify your email addressFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
MEDIUM
Access to sensitive file pathstests/README.md:137 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- Valid Time Doctor credentials in `.env`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File type combined with upload actiontests/README.md:22 · File type combined with upload action — agent may exfiltrate local data files│ └── test_complete_flow_output.csv # Sample CSV outputFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
Access to sensitive file pathstests/integration/test_date_navigation.py:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Start browser (set HEADLESS=false in .env to see browser)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/scraper.py:68 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load .env file from project directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/integration/debug_login.py:208 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint(" 1. Credentials in .env are correct")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstests/integration/debug_login.py:22 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint("❌ Please configure TD_EMAIL and TD_PASSWORD in .env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈56 tok
1 file · 47 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 timedoctor-mcp@1.3.0 as of 2 h ago. This is the package itself, not its dependencies.

What would make this Verified

29 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
  2. Unclaimed publisher≈ +8 on the totalClaim frifster: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
  4. 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.
  5. Destructive file system command detected≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  6. File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim frifsterPropose a patch to the maintainer