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/aslamanver/mcp_clockify/mcp_clockifygit clone --depth 1 https://github.com/aslamanver/mcp_clockifyWrote 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/aslamanver/mcp_clockify/mcp_clockify)<a href="https://agentmods.dev/mcp/aslamanver/mcp_clockify/mcp_clockify"><img src="https://agentmods.dev/badge/mcp/aslamanver/mcp_clockify/mcp_clockify.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp_clockify 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 9 lines scan A 4cd7cbf6a6fa
mcp_clockify is an MCP server published in the GitHub repository aslamanver/mcp_clockify (5 stars, last pushed 6mo ago), with no licence file. 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
habitica
MCP server "habitica" as configured in rodcordeiro/habitica-mcp. Runs ../../dist/index.js with node. Needs 3 environment variables to run.
weekly-review-skill
MCP server "weekly-review-skill" as configured in testman2025/weekly-review-skill. Runs locally from the weekly-review-skill Python package.
calendly-mcp
MCP server connecting Claude Desktop/Code to Calendly for natural-language scheduling management. Runs locally from the calendly-mcp Python package.
mcp-obsidian-tools
Model Context Protocol server for Obsidian Vaults with write/append capabilities. Runs locally from the mcp-obsidian-tools npm package.
sse-email-mcp-server
基于 MCP 协议的邮件服务器，支持 SMTP/IMAP/POP3 协议，可发送和接收邮件。支持 Gmail、Outlook、QQ、163、126、Sina 等主流邮箱服务商，支持附件、HTML/文本格式，动态认证。完美集成 Cursor、Claude Desktop 等 AI 助手，实现邮件自动化处理。. Runs locally from the sse-email-mcp-server npm package.
gmail-mcp
Gmail MCP Server. Runs locally from the gmail-mcp Python package.