Torrent Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YGG_PASSKEY | No | Your YggTorrent passkey for interacting with the API. Found in 'Mon compte' -> 'Mes paramètres' on the YggTorrent website. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| available_sourcesB | Get the list of available torrent sources. |
| search_torrentsA | Perform an advanced torrent search across multiple providers. Result Analysis & Ranking:
Response Requirements:
|
| popular_torrentsA | Get the most popular torrents right now across providers with an official top listing. Output is grouped per source (thepiratebay.org, uindex.org, 1337x.to, eztvx.to,
yts.vg, nyaa.si), keeping up to Response Requirements:
|
| get_torrentA | Get the magnet link for a specific torrent by id. |
| authorize_webappA | Authorize a browser on the Torrent Search webapp via its pairing code. The code comes from an user interaction on the webapp: they click "Open in Telegram", scan the QR code, or copy the prompt message, which sends "Authorize for Torrent Search" to you. Take the code from that message and call this tool with it and the user's Telegram chat id. Codes are single-use and expire after 5 minutes. After approval the user MUST go back to the webapp: the browser polls and completes the authentication there (it shows "Access granted" and unlocks the app permanently). |
| forward_torrentA | Send a torrent (filename + magnet) to the user's Telegram chat. The forward goes through the Torrent Search REST API, which owns the Telegram bot token; when PRUNE_MAGNET_LINKS is enabled the magnet is pruned to 'magnet:?xt=urn:btih:HASH&dn=' before sending. Requires TORRENT_SEARCH_API_KEY (same value as the API server) and TORRENT_SEARCH_API_URL. Forwards are rate-limited per chat (20/min). |
| torrent_webappA | Present the Torrent Search webapp and its Telegram pairing access system. Returns the webapp URL and how to get authorized by you. Tell the user to open the URL: on first visit the site shows a pairing dialog with a QR code and buttons ("Open in Telegram", "t.me" fallback, "Copy Prompt"). Ask the user to scan the QR code, click "Open in Telegram", or copy the prompt message and send it to you in the Telegram chat. That message ("Authorize for Torrent Search") carries the code; when it arrives, extract it and call authorize_webapp with it and the user's Telegram chat id. Codes expire after 5 minutes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The search, popular, get-by-id, source-list, forwarding, and webapp auth tools each target distinct actions, and the descriptions clearly separate them. search_torrents and popular_torrents are the closest pair, but query-based search vs. official top listings is explicit. torrent_webapp and authorize_webapp are complementary steps rather than overlapping tools.
Most tools follow a verb_noun pattern (get_torrent, search_torrents, authorize_webapp, forward_torrent), but available_sources and popular_torrents use adjective_noun phrasing and torrent_webapp is a bare resource name. These deviations are readable but break the otherwise consistent command-style convention.
Seven tools is a well-scoped size for a torrent search server with an additional Telegram/webapp pairing flow. Each tool covers a distinct step without redundancy or unnecessary breadth.
The core workflow is covered: discover sources, search or list popular torrents, resolve a magnet by id, and forward it to Telegram, plus the webapp authorization flow. Minor gaps remain such as source-specific browsing or more detailed torrent metadata, but they do not create dead ends for the main use case.