Pandafile MCP Server
OfficialRelated Servers
Alternatives to Pandafile MCP Server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely transfer files between machines via encrypted, expiring share links, with tools for upload, download, status checks, and link management.MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to privately store files and create controlled share links with expiry, open limits, recipient restrictions, approval gates, revocation, and access logging.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to send and receive files securely via JustDrop, with end-to-end encryption, QR codes, and no server-side storage.4143 npmMIT

@vitalsend/mcpofficial
AlicenseAqualityBmaintenanceEnables an AI agent to send files end-to-end encrypted, encrypting on the user's computer and keeping the download link key, password, and login away from the model.141 npmAGPL 3.0- FlicenseAqualityBmaintenanceEnables AI agents to split large files, zips, or folders into size-capped parts with SHA-256 checks, verify or regenerate missing parts, and rebuild the original across platforms so handoffs respect strict per-file upload limits.81-
- AlicenseBqualityDmaintenanceEnables AI agents to perform FTP/FTPS/SFTP file operations including upload, download, sync, and directory management with multi-server support.36107 npm8MIT
TDQS
Scored across 13 tools
Each tool maps to a distinct resource and action: transfers (send/get/list/update/delete), recipients (add/remind), imports (send_from_urls/get_import_status), and file requests (create/list/close). The potentially ambiguous pair send_files vs send_from_urls is clearly separated by source (local upload vs public HTTPS URLs), and get_transfer vs get_account vs get_import_status target different entities. No two tools could be plausibly confused in normal use.
All 13 tools use consistent snake_case verb_noun naming (send_files, get_transfer, list_transfers, update_transfer, delete_transfer, create_file_request, close_file_request). The verb set is small and predictable — send/get/list/add/remind/update/delete/create/close — with no camelCase or stylistic mixing.
13 tools sits squarely in the well-scoped range for a file-transfer service with three sub-domains (transfers, imports, file requests). Each tool covers a distinct operation and none appears redundant or like filler.
Transfers have full lifecycle coverage (send, list, get detail, update, delete) plus recipient management, and file requests cover create/list/close. Minor gaps remain: no remove_recipient, no get_file_request for a single upload page's detail, and no reopen_file_request (the description says reopening is dashboard-only), which slightly limits programmatic file-request management.