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/SwamiRama/solidtime-mcp-serverWrote 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/swamirama/solidtime-mcp-server/solidtime-mcp-server)<a href="https://agentmods.dev/mcp/swamirama/solidtime-mcp-server/solidtime-mcp-server"><img src="https://agentmods.dev/badge/mcp/swamirama/solidtime-mcp-server/solidtime-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
solidtime-mcp-server 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 6d 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
{ "solidtime-mcp-server": { "command": "npx", "args": [ "-y", "solidtime-mcp-server" ] } }
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.
- 6d ago First seen · 9 lines scan A 1b1db03d8719
solidtime-mcp-server is an MCP server published in the GitHub repository SwamiRama/solidtime-mcp-server (1 stars, last pushed 6mo 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
clockify-agent-plugin
Unofficial Clockify time tracking for coding sessions - MCP tools plus workflow skills. Not affiliated with Clockify/Cake.com. Runs locally from the @dustinestes/clockify-agent-plugin npm package. Needs 1 environment variable to run.
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.
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP. Runs locally from the obsidian-mcp-server npm package. Needs 10 environment variables to run.
google-workspace
Give AI agents access to Gmail, Calendar, Drive, and more — multi-account, manifest-driven. Runs locally from the @aaronsb/google-workspace-mcp npm package. Needs 2 environment variables to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
multi-account-gmail-mcp
Multi-account Gmail MCP server for AI agents. Runs locally from the multi-account-gmail-mcp Python package. Needs 3 environment variables to run.