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/weskerllc/cronicornWrote 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/weskerllc/cronicorn/mcp-server-cronicorn-mcp-server)<a href="https://agentmods.dev/mcp/weskerllc/cronicorn/mcp-server-cronicorn-mcp-server"><img src="https://agentmods.dev/badge/mcp/weskerllc/cronicorn/mcp-server-cronicorn-mcp-server/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/weskerllc/cronicorn/mcp-server-cronicorn-mcp-server"><img src="https://agentmods.dev/badge/mcp/weskerllc/cronicorn/mcp-server-cronicorn-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cronicorn-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 2mo 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 2mo ago First seen · 13 lines scan A 54a5b111ec8b
cronicorn-mcp-server is an MCP server published in the GitHub repository weskerllc/cronicorn (3 stars, last pushed 8mo 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
agent-scheduler
A deterministic, subscription-aware coding agent scheduler. Runs locally from the agent-scheduler Python package.
datasieve
On-chain watches, web-page monitors, dead-man switches, cron, and agent coordination, paid via x402. Runs locally from the datasieve-mcp npm package. Needs 2 environment variables to run.
agentcron
Schedule tasks for later from your AI agent: reminders, delayed webhooks, recurring jobs. Remote server at cron.mgm-llc.org.
time
Timezone, dates, cron, timestamps for AI agents. Runs locally from the @rog0x/mcp-time-tools npm package.
habitica
MCP server "habitica" as configured in rodcordeiro/habitica-mcp. Runs ../../dist/index.js with node. Needs 3 environment variables to run.
pomodoro-ai-mcp
Pomodoro Ai MCP server. Tools: start session, stop session, get stats. Built by MEOK AI Labs. Runs locally from the pomodoro-ai-mcp Python package.