Timesheet (npm) MCP Server
timesheet-mcp-server
npm
v1.0.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for generating monthly timesheets from GitLab and Calendar activities
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (activity-collector-mcp/src/utils/oauthFlow.ts)MTC-SRC-002
In the server's implementation (`activity-collector-mcp/src/utils/oauthFlow.ts:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; import { exec } from 'child_process'; import { promisify } from 'util'; const execAsync = promisify(exec); /** * Op
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server activity-collector-mcp/src/utils/oauthFlow.ts
Tools 22
Each tool and what it can reach — statically extracted from the published source.
clear_cacheingests untrusted inputfetch_github_activityingests untrusted inputfetch_gitlab_activityingests untrusted inputfetch_google_calendar_eventsingests untrusted inputfetch_outlook_calendar_eventsingests untrusted inputgenerate_daily_timesheetingests untrusted inputgenerate_date_range_timesheetingests untrusted inputgenerate_timesheetingests untrusted inputgenerate_weekly_timesheetingests untrusted inputauthenticate_gitlabno sensitive capability
Show 12 more tools ↓
authenticate_googleno sensitive capabilitycheck_authentication_statusno sensitive capabilityconfigure_githubno sensitive capabilityconfigure_gitlabno sensitive capabilityconfigure_google_calendarno sensitive capabilityconfigure_outlook_calendarno sensitive capabilityconfigure_psino sensitive capabilityget_psi_tasksno sensitive capabilitygoogle_calendar_callbackno sensitive capabilityinspect_psi_pageno sensitive capabilityoutlook_calendar_callbackno sensitive capabilitysubmit_to_psino sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (22 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 92/100 | 1 | 1.13.0 | 2026-09-08 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan timesheet-mcp-server --onlineOther implementations of Timesheet 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Productivity & Workflow
MCP AgentChat - 让 AI Agent 通过 Telegram 与用户实时交互：发送消息、图片，等待用户回复
A Model Context Protocol (MCP) server for Airthings Air Quality Monitor devices.
MCP server for Anki
TypeScript package for reading and searching Apple Notes on macOS via direct SQLite access. Includes markdown conversion, attachment support, and offers a local MCP server!
Verified biotech catalyst calendar (PDUFA/AdComm/trial readouts) anchored to official sources.
Appointment booking platform letting agents check provider availability and create bookings.