Fr Torrent Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YGG_DOMAIN | No | The domain to use for YggTorrent | www.yggtorrent.org |
| YGG_ENABLE | No | Enable (1) or disable (0) the YggTorrent provider | 0 |
| YGG_BASE_URL | No | The base URL for YggTorrent (useful if using a local bridge like YggAPI) | http://localhost:8715 |
| YGG_PASSWORD | No | Your YggTorrent password | |
| YGG_USERNAME | No | Your YggTorrent username | |
| TURBO_ENABLED | No | Whether to enable turbo mode for searches | true |
| LA_CALE_DOMAIN | No | The domain to use for LaCale | la-cale.space |
| LA_CALE_ENABLE | No | Enable (1) or disable (0) the LaCale provider | 0 |
| LA_CALE_PASSKEY | No | Your LaCale passkey, found on https://la-cale.space/profile | |
| LA_CALE_TRACKER | No | The tracker announce URL for LaCale | https://tracker.la-cale.space/announce |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_torrentsA | Perform an advanced torrent search across multiple providers. Arguments:
Query Construction Rules:
Result Analysis & Ranking:
Response Requirements:
|
| get_torrentC | Get a specific torrent (either magnet link or torrent file path) by id. |
| get_magnet_linkB | Get the magnet link for a specific torrent by id. |
| download_torrent_fileC | Download the torrent file for a specific torrent by id. |
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 4 tools
There is significant overlap between `get_torrent`, `download_torrent_file`, and `get_magnet_link`—all retrieve a torrent by id but differ only in output format. An agent could easily call the wrong tool or be uncertain which one to use.
All four tool names follow a consistent verb_noun pattern in snake_case (download_torrent_file, get_magnet_link, get_torrent, search_torrents), making the naming predictable and uniform.
Four tools is a reasonable count for a focused torrent search server. It covers search and retrieval without being excessive, though the split of retrieval into three tools could be streamlined to two.
The tool surface covers the essential operations: advanced search and retrieval of torrent files/magnet links. A minor gap might be a tool to list available categories or providers, but the core search-to-download workflow is complete.