{"id":"linuxserver-snapdrop","name":"snapdrop","homepage":"https://hub.docker.com/r/linuxserver/snapdrop","repo_url":"https://hub.docker.com/r/linuxserver/snapdrop","category":"storage","subcategories":[],"tags":["file-transfer","peer-to-peer","webrtc","browser","local-network","p2p"],"what_it_does":"Snapdrop is a web-based “send files to nearby devices” clone of Apple’s AirDrop concept. Users open the site on multiple devices, establish a peer connection in the browser, and transfer files/establish sessions via client-side networking (typically WebRTC) mediated by the Snapdrop server.","use_cases":["Peer-to-peer file transfer between a user’s devices (phone↔laptop)","Quick sharing of photos/docs without installing apps","Small-team or personal device-to-device transfers in local networks","Lightweight browser-based sharing for prototypes/demos"],"not_for":["High-volume enterprise file distribution","Compliance-heavy workflows requiring audited access control and detailed logging guarantees","Long-term managed storage or backup"],"best_when":"You need a simple, browser-first, local-device file transfer experience with minimal setup.","avoid_when":"You require strong authentication/authorization, durable storage, or formal SLA-level reliability.","alternatives":["File sharing services (e.g., Dropbox/Google Drive)","Peer-to-peer transfer apps (e.g., Syncthing)","Local network transfer tools (e.g., Resilio/Syncthing-based workflows)","AirDrop-like alternatives via vendor ecosystems"],"af_score":27.2,"security_score":37.2,"reliability_score":28.8,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:49:30.811038+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"No clear authentication/authorization interface was provided in the supplied information. Snapdrop-style deployments are typically unauthenticated or rely on ephemeral session/peer discovery."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Pricing not determined from provided information; open-source style tooling is commonly self-hosted."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":27.2,"security_score":37.2,"reliability_score":28.8,"mcp_server_quality":0.0,"documentation_accuracy":40.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":0.0,"tls_enforcement":70.0,"auth_strength":15.0,"scope_granularity":0.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Security properties depend heavily on the deployment. WebRTC peer-to-peer transfers should be protected by secure transport (TLS for the signaling server; DTLS/SRTP for media/data). Auth/authorization and abuse prevention appear likely minimal in typical deployments, so treat peer discovery and signaling as potentially reachable by unintended clients unless the server is locked down (firewalling, network policy, TLS, and optional auth if implemented). Secret handling and dependency hygiene cannot be verified from the provided information.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":40.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Likely lacks a stable machine-to-machine API contract (primarily browser UI + real-time peer connections).","Browser-networking constraints (NAT/firewalls, WebRTC ICE configuration) can cause intermittent failures that are hard for agents to reason about without explicit logs/observability.","If self-hosted, behavior depends on deployment configuration (server signaling, TURN/STUN, TLS, reverse proxy)."]}}