{"id":"mintopia-laravel-echo-server","name":"laravel-echo-server","homepage":"https://hub.docker.com/r/mintopia/laravel-echo-server","repo_url":"https://hub.docker.com/r/mintopia/laravel-echo-server","category":"messaging","subcategories":[],"tags":["laravel","websockets","broadcasting","realtime","pusher-protocol","nodejs","echo"],"what_it_does":"laravel-echo-server is a self-hosted WebSocket server that relays Laravel broadcast events (from Echo) to clients via the Pusher protocol (or compatible clients).","use_cases":["Real-time notifications (chat, alerts, dashboards) in Laravel apps","Implementing broadcasting with Laravel + WebSocket clients using Laravel Echo","Serving Pusher-compatible WebSocket traffic for front-end event subscriptions"],"not_for":["Serverless environments where persistent WebSockets are hard to maintain","High-security environments without careful TLS/auth/proxy configuration","Applications that need a full managed pub/sub service with dashboards, SLAs, and automatic scaling"],"best_when":"You already run your own infrastructure and want a lightweight, Pusher-compatible WebSocket relay for Laravel broadcasting.","avoid_when":"You cannot provide reliable process supervision, TLS termination, and rate-limit/proxy protections around a long-lived WebSocket service.","alternatives":["Pusher (managed)","Socket.IO (with suitable Laravel integration)","Laravel WebSockets (Soketi)","Centrii/Laravel broadcast with a managed real-time provider","Self-hosted message brokers with custom WebSocket gateway"],"af_score":31.8,"security_score":41.8,"reliability_score":27.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:40:16.951275+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":["WebSocket connections with configuration-based options (e.g., Pusher protocol compatibility)","Laravel broadcasting uses an auth endpoint pattern typically provided by the Laravel app (not by this package itself)"],"oauth":false,"scopes":false,"notes":"This package is primarily a WebSocket relay compatible with Pusher-style clients; authentication/authorization for private/presence channels is typically handled by your Laravel app’s broadcast auth routes rather than by a first-class OAuth/scopes model in this package."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source library; costs are operational (hosting a WebSocket server, TLS/proxy, monitoring)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":31.8,"security_score":41.8,"reliability_score":27.5,"mcp_server_quality":0.0,"documentation_accuracy":50.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":10.0,"tls_enforcement":55.0,"auth_strength":40.0,"scope_granularity":20.0,"dependency_hygiene":45.0,"secret_handling":50.0,"security_notes":"As a WebSocket relay, security depends heavily on correct TLS/proxy configuration, limiting origins, and using Laravel’s broadcast authorization for private/presence channels. Package-level scope granularity and documented security controls are not clearly inferable from the provided info.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":40.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is a long-lived WebSocket server; agent workflows that assume request/response REST semantics or automatic retries may not apply.","Correct functioning typically depends on external Laravel broadcast configuration and a working broadcast auth endpoint/routes for private/presence channels.","Operational configuration (TLS termination, reverse proxy settings, allowed origins, and process supervision) is critical and often not captured as API-level contracts."]}}