pulsemcp verified Safe content atomic mcp-remote

rqbit

This MCP server provides Python API wrapper and server integration for the rqbit BitTorrent client, enabling torrent management operations through HTTP API calls. Built by philogicae using Python with httpx for HTTP/2 support and FastMCP for the server framework, it offers eight core tools for listing torrents, adding torrents via magnet links, retrieving torrent details and statistics, and controlling torrent lifecycle with pause/start/delete/forget operations. The implementation features async HTTP client operations with proper error handling, environment-based configuration for rqbit instance URLs, and supports multiple transport modes including stdio, SSE, and HTTP with Docker deployment options. The server bridges AI agents with BitTorrent automation workflows, making it valuable for automated download management, torrent monitoring systems, and building AI assistants that need structured access to rqbit's torrent client functionality.

Cognium trust score

88%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: cloud-infra
Source: PulseMCP
Repository: github.com/philogicae/rqbit-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve rqbit from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"