{"id":"francknouama-movies-mcp-server","name":"movies-mcp-server","homepage":null,"repo_url":"https://github.com/francknouama/movies-mcp-server","category":"ai-ml","subcategories":[],"tags":["mcp","model-context-protocol","movies","database","postgresql","go","json-rpc","stdio","search","images","recommendations"],"what_it_does":"Movies MCP Server is an MCP (Model Context Protocol) server that manages a PostgreSQL-backed movie database, exposing tools for movie and actor CRUD, linking/unlinking cast, search (multi-criteria, by decade, by rating range), bulk import, recommendations, and director career analysis. It also provides MCP resources for returning full database stats and base64-encoded poster images.","use_cases":["Integrating a movie/actor database with an AI assistant via MCP (JSON-RPC over stdio)","AI-assisted movie discovery (search, decade filters, rating ranges, similarity/recommendations)","Building interactive desktop agent experiences (e.g., Claude Desktop MCP integration)","Maintaining a structured movie catalog and cast/filmography relationships","Serving poster images as MCP resources to other agent components"],"not_for":["Direct public Internet APIs without additional hardening (it’s primarily an MCP stdio server)","Workloads that require a classic REST/GraphQL endpoint for web clients","Use cases needing third-party auth integration/SSO as described in the README (auth details are environment-variable based and not clearly specified for MCP)"],"best_when":"You want an MCP-native toolset that an agent can call locally (stdio) while using a PostgreSQL database as the source of truth.","avoid_when":"You need externally exposed HTTP endpoints, complex enterprise auth flows, or a clearly documented, fine-grained authorization model for the MCP tools.","alternatives":["Expose the same data via a REST/GraphQL API (custom service) and have agents call it","Use an existing open-source movie database/search API (e.g., TMDb) with an agent tool wrapper","Implement an MCP server wrapper around your own database/data-access layer using the official Go MCP SDK","Use a vector-search/recommendation service if you specifically need ML-based retrieval rather than rules/search"],"af_score":60.0,"security_score":47.5,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:21:52.799900+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":true,"sdk_languages":["Go"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Environment-variable based authentication configuration is mentioned (JWT_SECRET, API_KEY), but the README does not clearly describe how auth is enforced for MCP tool calls in the SDK server."],"oauth":false,"scopes":false,"notes":"Auth behavior for MCP is not fully specified in the provided README: it lists security-related environment variables (JWT_SECRET, API_KEY, RATE_LIMIT, TLS_*), but does not document the actual MCP authentication/authorization model, supported methods, or per-tool/role enforcement."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information is provided; repo appears to be a self-hosted open-source server."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":60.0,"security_score":47.5,"reliability_score":32.5,"mcp_server_quality":88.0,"documentation_accuracy":70.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":30.0,"tls_enforcement":60.0,"auth_strength":45.0,"scope_granularity":20.0,"dependency_hygiene":55.0,"secret_handling":60.0,"security_notes":"README mentions security-related env vars (JWT_SECRET, API_KEY, TLS_ENABLED/TLS_CERT_FILE/TLS_KEY_FILE, RATE_LIMIT) and also specifies non-root Docker execution and monitoring/health checks. However, the actual MCP authentication/authorization enforcement for tools, scope/role model, and whether TLS applies to the stdio MCP transport are not clearly documented. Rate limiting clarity for MCP is also limited in the provided content. Dependency hygiene and CVE status are not provided.","uptime_documented":20.0,"version_stability":35.0,"breaking_changes_history":30.0,"error_recovery":45.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"context-based pagination (search context + pages)","retry_guidance_documented":false,"known_agent_gotchas":["Because it’s an MCP stdio server, an agent integration must run the command and manage stdin/stdout correctly (not an HTTP URL).","Pagination is handled via “search context” tools rather than typical page/limit parameters; agents need to follow the context/page flow.","Auth and rate-limiting behavior are not clearly documented for MCP tool invocation in the README, so agent-side retries/backoff may need conservative handling."]}}