{"id":"oanhnn-laravel-echo-server","name":"laravel-echo-server","homepage":"https://hub.docker.com/r/oanhnn/laravel-echo-server","repo_url":"https://hub.docker.com/r/oanhnn/laravel-echo-server","category":"messaging","subcategories":[],"tags":["laravel","websockets","real-time","broadcasting","nodejs","redis","laravel-echo"],"what_it_does":"laravel-echo-server is a Node.js WebSocket server that works with Laravel apps (via Laravel Echo) to broadcast events to clients over WebSockets, typically using a Redis-based event layer.","use_cases":["Real-time dashboards and notifications","Chat/instant messaging (event-based)","Live updates for dashboards, counters, and activity feeds","Broadcasting server-side Laravel events to browser/mobile clients"],"not_for":["Public, internet-facing deployments without appropriate network and TLS hardening","Use as a generic message broker replacement unrelated to Laravel/Echo workflows","Use when you need strict REST/HTTP API contracts or formal OpenAPI documentation"],"best_when":"You’re building a Laravel-based app that already uses Laravel Echo and needs a WebSocket event gateway for broadcasting events to clients.","avoid_when":"You need a managed SaaS with built-in observability/SLA, or you require standardized HTTP API tooling rather than WebSocket event broadcasting.","alternatives":["Pusher (managed WebSocket/events)","Ably (managed real-time messaging)","Laravel WebSockets (Laravel-first WebSocket server)","Socket.IO (alternative Node real-time server)","Centric solutions via Redis Streams + custom WebSocket gateway"],"af_score":31.0,"security_score":41.8,"reliability_score":35.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:40:30.760308+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":["Not applicable as a standalone API auth layer in the typical configuration; WebSocket authentication is usually handled via Laravel/Echo token/cookie/session mechanisms and/or server configuration"],"oauth":false,"scopes":false,"notes":"Because this is a WebSocket server, authentication behavior depends on how the Echo client and server are configured (e.g., auth endpoints in Laravel, tokens, cookies, or middleware). No single standardized OAuth/scope model is provided by the package interface itself."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source/self-hosted component; operational costs come from your infrastructure (Node process, WebSocket traffic, Redis, hosting)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":31.0,"security_score":41.8,"reliability_score":35.0,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":45.0,"rate_limit_clarity":15.0,"tls_enforcement":55.0,"auth_strength":40.0,"scope_granularity":20.0,"dependency_hygiene":45.0,"secret_handling":50.0,"security_notes":"Security posture largely depends on deployment configuration: ensure TLS termination, restrict access (firewall/reverse proxy), and ensure authentication for private channels is enforced by the Laravel side. As a self-hosted WebSocket server, it is sensitive to misconfiguration (exposed ports, weak auth, missing origin checks, lack of rate limiting/DDoS protections at the edge).","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":45.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is primarily a WebSocket server; it’s not designed for request/response pagination patterns typical of REST APIs.","Agent-driven integration may require careful handling of connection lifecycle (connect/reconnect), event payload validation, and backpressure/queueing on the client side."]}}