Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/dustinestes/clockify-agent-plugin/clockify-agent-plugingit clone --depth 1 https://github.com/dustinestes/clockify-agent-pluginGrade A, and why
clockify-agent-plugin scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"clockify-agent-plugin": {
"command": "npx",
"args": [
"-y",
"@dustinestes/clockify-agent-plugin"
],
"env": {
"CLOCKIFY_API_KEY": "${CLOCKIFY_API_KEY}"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 12 lines scan A 6c568a407cb9
clockify-agent-plugin is an MCP server published in the GitHub repository dustinestes/clockify-agent-plugin (0 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
timesheet-mcp
Model Context Protocol server for Timesheet API. Runs locally from the @timesheet/mcp npm package. Needs 1 environment variable to run.
smartsheet-rm
Enterprise Model Context Protocol (MCP) server for Smartsheet Resource Management (10,000ft API) — time tracking, projects, allocations, scheduling, and capacity planning. Runs locally from the mcp-server-smartsheet-rm Python package. Needs 2 environment variables to run.
goalslot-mcp
MCP server "goalslot-mcp" as configured in ZeeshanAdilButt/goalslot-mcp. Runs locally from the goalslot-mcp npm package.
sideshift
MCP server "sideshift", hosted remotely at app.sideshift.app, as configured in SideShiftApp/sideshift-mcp-server.
clockify-mcp
Full-coverage Clockify MCP — 112 tools across 18 domains (incl. invoices, scheduling, time-off & approvals), native OpenTelemetry observability, and a 3-tier read/time-tracking/full access model. Runs locally from the clockify-mcp Python package. Needs 3 environment variables to run.
clockify-mcp
MCP server "clockify-mcp", hosted remotely at clockify.velryx.cc, as configured in EdwyReed/clockify-mcp.