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/TheStreamCode/chutes-media-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/thestreamcode/chutes-media-mcp/chutes-media-mcp)<a href="https://agentmods.dev/mcp/thestreamcode/chutes-media-mcp/chutes-media-mcp"><img src="https://agentmods.dev/badge/mcp/thestreamcode/chutes-media-mcp/chutes-media-mcp/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/thestreamcode/chutes-media-mcp/chutes-media-mcp"><img src="https://agentmods.dev/badge/mcp/thestreamcode/chutes-media-mcp/chutes-media-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chutes-media-mcp 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 10d 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
{
"chutes-media-mcp": {
"command": "npx",
"args": [
"-y",
"chutes-media-mcp"
],
"env": {
"CHUTES_API_KEY": ""
}
}
}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.
- 10d ago First seen · 12 lines scan A 54347d5b9184
chutes-media-mcp is an MCP server published in the GitHub repository TheStreamCode/chutes-media-mcp (1 stars, last pushed today), 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
mcp-imagenate
MCP server for image generation using multiple providers (Google Gemini, OpenAI, BFL FLUX). Runs locally from the mcp-imagenate npm package.
mcp-nanobanana-pro
MCP Server for NanoBanana AI Image Generation via AceDataCloud API. Runs locally from the mcp-nanobanana-pro Python package. Needs 1 environment variable to run.
mcp-seedream-pro
MCP Server for ByteDance Seedream AI Image Generation via AceDataCloud API. Runs locally from the mcp-seedream-pro Python package. Needs 1 environment variable to run.
mcp-flux-pro
MCP Server for Flux AI Image Generation via AceDataCloud API. Runs locally from the mcp-flux-pro Python package. Needs 1 environment variable to run.
tiktok-agent-publisher
Local-first TikTok Content Posting API for AI agents: OAuth checks, dry-run and live uploads. Runs locally from the tiktok-agent-publisher npm package. Needs 3 environment variables to run.
youtube-shorts-agent
Agent-first YouTube Shorts uploader: dry-run validation, OAuth checks, synthetic-media metadata. Runs locally from the youtube-shorts-agent npm package. Needs 3 environment variables to run.