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/trackly-app/trackly-cliWrote 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/trackly-app/trackly-cli/trackly-trackly)<a href="https://agentmods.dev/mcp/trackly-app/trackly-cli/trackly-trackly"><img src="https://agentmods.dev/badge/mcp/trackly-app/trackly-cli/trackly-trackly/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/trackly-app/trackly-cli/trackly-trackly"><img src="https://agentmods.dev/badge/mcp/trackly-app/trackly-cli/trackly-trackly.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
trackly 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
{
"trackly": {
"type": "http",
"url": "https://mcp.usetrackly.app/api/plugin/trackly/mcp"
}
}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 First seen · 6 lines scan A 453d52460194
trackly is an MCP server published in the GitHub repository trackly-app/trackly-cli (3 stars, last pushed 2d 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
chainlink-safe-fetch
MCP server "chainlink-safe-fetch" as configured in dollspace-gay/chainlink. Runs .claude/mcp/safe-fetch-server.py with python.
job-seeker
An utility downloader for a job search at seek.com.au. Runs locally from the job-seeker Python package.
skillmatch-mcp
Job search and ranking pipeline accessible via MCP (Model Context Protocol). Runs locally from the skillmatch-mcp Python package.
tierline
MCP server "tierline" as configured in jayj221/tierline. Runs locally from the tierline npm package.
socialgo
Model Context Protocol server for SocialGO — lets AI assistants (Claude, etc.) search services and place SMM orders, including keyless guest checkout (buy without an account, no API key). Runs locally from the @socialgo/mcp npm package. Needs 3 environment variables to run.
interactive-terminal
MCP server for real interactive terminal sessions — REPLs, SSH, databases, Docker. Runs locally from the mcp-interactive-terminal npm package. Needs 3 environment variables to run.