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/philogicae/torrent-search-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/philogicae/torrent-search-mcp/torrent-search-mcp)<a href="https://agentmods.dev/mcp/philogicae/torrent-search-mcp/torrent-search-mcp"><img src="https://agentmods.dev/badge/mcp/philogicae/torrent-search-mcp/torrent-search-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/philogicae/torrent-search-mcp/torrent-search-mcp"><img src="https://agentmods.dev/badge/mcp/philogicae/torrent-search-mcp/torrent-search-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
torrent-search-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 12d 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
{ "torrent-search-mcp": { "command": "uvx", "args": [ "torrent-search-mcp" ] } }
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.
- 12d ago First seen · 8 lines scan A 5fbcf4f2d9af
torrent-search-mcp is an MCP server published in the GitHub repository philogicae/torrent-search-mcp (30 stars, last pushed 2d 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-30.
Other mcp servers, from other repositories
fr-torrent-search-mcp
FR Torrent MCP Server. Runs locally from the fr-torrent-search-mcp Python package.
roam-code
MCP server "roam-code" as configured in silkweave/silkweave. Launched with roam mcp.
lighthouse
A comprehensive Model Context Protocol (MCP) server that provides web performance auditing, accessibility testing, SEO analysis, security assessment, and Core Web Vitals monitoring using Google Lighthouse. Enables LLMs and AI agents to perform detailed we. Runs locally from the @danielsogl/lighthouse-mcp npm package.
silkweave
MCP server "silkweave" as configured in silkweave/silkweave. Launched with pnpm mcp.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
proximo-proxmox
The Proxmox MCP you can hand the keys: VE/PBS/PMG/PDM. Plan, prove, undo, diagnose. MCP/A2A/API. Runs locally from the proximo-proxmox Python package.