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.
git clone --depth 1 https://github.com/dustinestes/clockify-agent-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/dustinestes/clockify-agent-plugin/clockify-agent-plugin)<a href="https://agentmods.dev/mcp/dustinestes/clockify-agent-plugin/clockify-agent-plugin"><img src="https://agentmods.dev/badge/mcp/dustinestes/clockify-agent-plugin/clockify-agent-plugin/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/dustinestes/clockify-agent-plugin/clockify-agent-plugin"><img src="https://agentmods.dev/badge/mcp/dustinestes/clockify-agent-plugin/clockify-agent-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade 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 1mo ago.
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@latest"
],
"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.
- 1mo ago Changed 5319fa6ff831
- 1mo ago 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 1mo 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.
rize-mcp-server
MCP server "rize-mcp-server" as configured in rize-io/mcp-server. Runs locally from the rize-mcp-server npm package.
clockify-mcp
MCP server "clockify-mcp", hosted remotely at clockify.velryx.cc, as configured in EdwyReed/clockify-mcp.
solidtime-mcp-server
MCP server "solidtime-mcp-server" as configured in SwamiRama/solidtime-mcp-server. Runs locally from the solidtime-mcp-server npm package.
tmetric-minimal-mcp
MCP server "tmetric-minimal-mcp" as configured in guglielmo/tmetric-minimal-mcp. Runs locally from the @guglielmo/tmetric-minimal-mcp npm package.
mcp-telegram
Unofficial Telegram MCP server — read, search, reply and react in your own Telegram account. Runs locally from the @overpod/mcp-telegram npm package. Needs 2 environment variables to run.