timesheet-tms-mcp@1.0.1
VERIFIED· not startedPublisher 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.
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.
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 scenariosStatic findings
curl -LsSf https://astral.sh/uv/install.sh | shFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.curl -LsSf https://astral.sh/uv/install.sh | shFix: 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 timesheet-tms-mcp@1.0.1 as of 2 h ago. This is the package itself, not its dependencies.