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/slima-ai/slima-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/slima-ai/slima-mcp/slima)<a href="https://agentmods.dev/mcp/slima-ai/slima-mcp/slima"><img src="https://agentmods.dev/badge/mcp/slima-ai/slima-mcp/slima.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
slima 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 8d 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
{
"slima": {
"command": "npx",
"args": [
"-y",
"slima-mcp"
],
"env": {
"SLIMA_API_TOKEN": ""
}
}
}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.
- 8d ago First seen · 12 lines scan A f6a85b78f53f
slima is an MCP server published in the GitHub repository slima-ai/slima-mcp (1 stars, last pushed 4mo 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
mcp-ffmpeg
A Model Context Protocol server for FFmpeg media processing. Runs locally from the mcp-ffmpeg Python package.
tiktok-instagram-downloader
Extract & download TikTok, Instagram, YouTube, Douyin media — HD, no watermark, MP3 export. Runs locally from the @ssavecc/mcp-server npm package. Needs 1 environment variable to run.
after-effects-mcp
MCP server that gives AI assistants deep programmatic control of Adobe After Effects: arbitrary ExtendScript execution, background rendering, deep project/layer inspection, and native Arabic/RTL and multilingual support. Runs locally from the after-effects-mcp npm package.
agent-canvas
Local MCP canvas for Modellix image generation, editing, task recovery, and visual project work. Runs locally from the @modellix/agent-canvas npm package.
blender-mcp-2-79
MCP server "blender-mcp-2-79" as configured in AaronBrunckhurst/blender-mcp-2.79. Runs locally from the blender-mcp-2-79 Python package.
shotpipe-mcp
Screenshot any URL and see it, or mint a social card — hosted, SSRF-safe, cached. No Chrome to run. Runs locally from the shotpipe-mcp npm package. Needs 3 environment variables to run.