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/severment/cleyaWrote 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/severment/cleya/cleya)<a href="https://agentmods.dev/mcp/severment/cleya/cleya"><img src="https://agentmods.dev/badge/mcp/severment/cleya/cleya/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/severment/cleya/cleya"><img src="https://agentmods.dev/badge/mcp/severment/cleya/cleya.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cleya 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
{ "cleya": { "command": "npx", "args": [ "-y", "cleya" ] } }
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 · 9 lines scan A a3e4bbec3cd8
cleya is an MCP server published in the GitHub repository severment/cleya (0 stars, last pushed 2mo ago), licensed Apache-2.0. 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
claude-real-video
Let Claude (or any LLM) actually watch a video — scene-aware, deduplicated frames + transcript, from a URL or local file. Runs locally from the claude-real-video Python package.
crv
MCP server "crv" as configured in HUANGCHIHHUNGLeo/claude-real-video. Launched with crv-mcp.
imgcli
Convert, resize, crop, filter & composite images via the imgcli CLI (lightweight, no deps). Runs locally from the imgcli-mcp npm package. Needs 1 environment variable to run.
continuityguard
Local, zero-network CLI and library that scores AI-generated short-drama video clips for character-consistency drift and physics-plausibility issues before you re-render. Runs locally from the continuityguard-cli Python package.
ffmpeg-render-pro
Parallel video rendering tools: detect GPU encoders, render, color grade, merge audio, concat. Runs locally from the ffmpeg-render-pro npm package.
youtube-ai
YTAI: Python YouTube SDK, CLI, and MCP server without user-supplied API keys. Runs locally from the youtube-ai Python package.