Skills/PyPI/timesheet-tms-mcp

timesheet-tms-mcp@1.0.1

VERIFIED· not started

Publisher claims: "Timesheet Management System MCP Server - Based on FastMCP 2.0" Observed in sandbox: calls astral.sh only, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher yangyuezheng · publishing for 399 daysInstalls 52Last detonated 3 h ago
$claude mcp add timesheet-tms-mcp -- uvx timesheet-tms-mcp
WatchReport an issue

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: 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
TIMESHEET_API_TOKENConfiguration, not credentials: CACHE_TTL, ENABLE_CACHE, ENABLE_RATE_LIMIT, MCP_LOG_LEVEL, MCP_TRANSPORT, RATE_LIMIT_PER_MINUTE, TIMESHEET_API_BASE_URL
Where it talks to
no vendor host named in the codeAlso astral.sh, claude.ai, ktvsky.com — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · reached only astral.sh
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 astral.sh, claude.ai, ktvsky.com as well as its own vendor. The guard injects TIMESHEET_API_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx timesheet-tms-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 85/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: calls astral.sh only, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 3 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.2snetworkCONNECT tcp://astral.sh:443 · not in the allow-list, refused
0.2sprocessexec /usr/bin/uname
0.2sprocessexec /usr/bin/curl
0.2sprocessexited 1: curl: (22) The requested URL returned error: 403
0.6sprocessdependency install exit 1 ·
0.6sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.6sprocessscript backend runs setup only
0.6sprocesssecond launch, clock +45 days, CI unset
0.9snetworkCONNECT tcp://astral.sh:443 · not in the allow-list, refused
0.9sprocessexec /usr/bin/uname
0.9sprocessexec /usr/bin/curl
0.9sprocessexited 1: curl: (22) The requested URL returned error: 403

Static findings

CRITICAL
Pipe-to-shell patterninstall.sh:44 · Pipe-to-shell pattern — downloads and immediately executes remote codecurl -LsSf https://astral.sh/uv/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST06
MEDIUM
Remote installer piped to shellinstall.sh:44 · Remote installer piped to shellcurl -LsSf https://astral.sh/uv/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST07

Cost to the agent

Instructions loaded
≈54 tok
1 file · 42 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 timesheet-tms-mcp@1.0.1 as of 2 h ago. This is the package itself, not its dependencies.