masv
OfficialRelated Servers
Alternatives to masv
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceEnables 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 MCP-compatible agents to convert PDFs and images into Markdown, JSON, HTML, LaTeX, DOCX, or ZIP by wrapping a document parsing service's REST API as callable tools, including uploads, parsing jobs, progress polling, and result downloads.1Apache 2.0
- AlicenseAqualityAmaintenanceEnables an LLM to interact with the USPS EPF V2 REST Services API for listing files, requesting download manifests, streaming binary EPF files to disk, and updating file statuses.8MIT

EasySendofficial
AlicenseNot gradedqualityDmaintenanceEasySend MCP server lets AI assistants upload, download and share files instantly. No API key or authentication needed. Upload any file type up to 1GB, get a shareable link. Tools: upload_file, upload_multiple_files, get_bundle, download_file, download_bundle, delete_file, bundle_status.MIT
Pinata MCPofficial
AlicenseBqualityDmaintenanceProvides Claude with access to Pinata's API, allowing it to interact with both Public and Private IPFS for file uploading, searching, organization, and content retrieval.3557 npm6MIT- AlicenseNot gradedqualityAmaintenanceLets AI agents upload text, images, and files to Pixeldrain and download files back to the local machine, returning shareable file or album URLs. Supports optional API key binding so uploads belong to a user's account.73MIT
TDQS
Scored across 20 tools
Most tools target clearly distinct resource+action pairs (portals, packages, integrations, activities). The activity trio (get_activities, get_activity_events, get_activities_information) has some overlap—get_activities vs get_activities_information could be confused—but descriptions differentiate them. Package variants (get_packages vs get_portal_packages vs get_package_files) are well explained.
Consistent snake_case verb_noun pattern dominates (get_portal, create_portal, delete_package). Minor deviations: 'list_files_on_integration' uses list_ where siblings use get_, and 'update_package_expiration_date_and_time' is unusually verbose. Still readable and largely predictable.
20 tools is slightly heavy but well-scoped for a full file-transfer platform spanning portals, packages, integrations, activities, and team members. Each tool maps to a distinct operation, so no obvious filler.
Portals have full CRUD (get/get/create/update/delete) and packages cover retrieval, files, transfers, expiration, and deletion. Notable gap: no direct create_package for team packages (only integration-driven creation), and no delete for integrations—minor workarounds exist but the package-creation lifecycle is incomplete.