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/zernozerno/zerno-mcpWrote 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/zernozerno/zerno-mcp/zerno-lite)<a href="https://agentmods.dev/mcp/zernozerno/zerno-mcp/zerno-lite"><img src="https://agentmods.dev/badge/mcp/zernozerno/zerno-mcp/zerno-lite/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/zernozerno/zerno-mcp/zerno-lite"><img src="https://agentmods.dev/badge/mcp/zernozerno/zerno-mcp/zerno-lite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zerno-lite 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 11d 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
{
"zerno-lite": {
"url": "https://zerno.one/mcp",
"type": "streamable-http"
}
}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.
- 11d ago First seen · 6 lines scan A 12ab87f30419
zerno-lite is an MCP server published in the GitHub repository zernozerno/zerno-mcp (0 stars, last pushed 2mo 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
stellary
MCP server "stellary", hosted remotely at api.stellary.co, as configured in Anymfah/stellary-mcp.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.
plane-workflow
MCP server "plane-workflow" as configured in amirhosseinkz/plane-workflow-mcp. Runs locally from the plane-workflow Python package.
openproject-mcp-server
MCP server for OpenProject: 87 tools for work packages, attachments, git activity, time tracking, meetings and reporting over the API v3. Runs locally from the openproject-mcp-server Python package. Needs 5 environment variables to run.
taiga-mcp-server
MCP server connecting Claude, Cursor, Windsurf, and other AI assistants to Taiga (Cloud and self-hosted) — projects, epics, user stories, tasks, issues, sprints, wiki, and more. Runs locally from the @madebyclowd/taiga-mcp-server npm package.
moo-tasks
Robust, agentic task orchestration & management engine with MCP, Web UI, and human-in-the-loop controls. Runs locally from the moo-tasks npm package.