Skip to main content
Glama
philogicae

Torrent Search MCP Server

by philogicae
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
YGG_PASSKEYNoYour 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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": false,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
available_sourcesB

Get the list of available torrent sources.

search_torrentsA

Perform an advanced torrent search across multiple providers.

Result Analysis & Ranking:

  1. Quality: Prefer 1080p or 4k, over 720p.

  2. Efficiency: Prefer h265/HEVC for better quality/size ratio.

  3. Health: Maximize seeders + leechers.

  4. Size: Prefer smaller files within the same quality bracket.

  5. Language: Ultimately, if multiple equivalent options are available, choose the one with more languages.

Response Requirements:

  • Recommend the top 3-5 results maximum.

  • For each recommendation, include: Filename, Size, Seeds/Leechs, Date, Source, and a 1-sentence "Why this?" reason.

  • If results are poor, irrelevant or too diverse, suggest specific keywords to improve the search.

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 per_source results per site, each site's entries pre-ranked by swarm health.

Response Requirements:

  • Recommend the top 5-10 results maximum, focused on latest releases.

  • For each recommendation, include: Filename, Size, Seeds/Leechs, Date, Source, and a 1-sentence "Why this?" reason.

get_torrentA

Get the magnet link for a specific torrent by id.

The result is wrapped in the untrusted-data fence: the magnet is the fenced value itself, the notice and tag lines are not part of the link.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation4/5

Most tools have clearly distinct purposes: search, popular listings, source listing, magnet retrieval, forwarding, and webapp authorization. The main potential confusion is between torrent_webapp and authorize_webapp, though the descriptions distinguish presenting the webapp from performing the actual authorization.

Naming Consistency4/5

All tool names use snake_case, which is consistent and readable. However, the naming patterns vary between verb_noun (get_torrent, forward_torrent), adjective_noun (available_sources, popular_torrents), and noun_noun (torrent_webapp), so it is not a uniform verb_noun convention.

Tool Count5/5

Seven tools is a well-scoped set for torrent search plus Telegram forwarding and webapp authorization. Each tool appears to earn its place, with no obvious redundant operations.

Completeness4/5

The set covers the core workflows: discovering sources, searching, browsing popular torrents, retrieving a magnet link, forwarding to Telegram, and authorizing the webapp. Minor gaps might include richer torrent detail retrieval or pagination/filtering by source, but agents can work around them.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources