{"id":"tyrell-omdb-mcp-server","name":"omdb-mcp-server","homepage":"https://tyrell.co","repo_url":"https://github.com/tyrell/omdb-mcp-server","category":"ai-ml","subcategories":[],"tags":["mcp","modelcontextprotocol","omdb","spring-boot","java","spring-ai","webflux","sse","caching","json-rpc","openapi"],"what_it_does":"Provides a Model Context Protocol (MCP) server exposing OMDB (Open Movie Database) search and movie-details retrieval. Implements MCP tools (search_movies, get_movie_details, get_movie_by_imdb_id) over HTTP JSON-RPC and/or SSE transport, with automatic caching and Swagger/OpenAPI documentation for REST-style endpoints (including cache management).","use_cases":["Letting AI assistants query OMDB for movie search and metadata","Tool-based retrieval of movie details (by title/year/type or by IMDb ID) via MCP clients (e.g., Claude Desktop)","Reducing OMDB API calls via server-side caching and cache management endpoints","Building reactive web services or agents that can call MCP tools over SSE/HTTP JSON-RPC"],"not_for":["Use as a general-purpose OMDB proxy without considering OMDB API rate limits/terms","Handling sensitive personal data (it primarily serves public movie metadata)","Scenarios requiring strong first-party authentication/authorization for end users (the server mainly forwards OMDB API key usage)"],"best_when":"You want an MCP-compatible integration to fetch OMDB movie metadata with caching and a documented interface for agent tool calling.","avoid_when":"You need robust tenant isolation, per-user authorization, or strict reliability guarantees without validating upstream OMDB behavior and your deployment configuration.","alternatives":["Direct OMDB API calls from your application","A generic MCP wrapper for third-party APIs (if you already have one)","Different OMDB-to-tool wrappers that provide REST/GraphQL endpoints with stronger auth controls"],"af_score":68.5,"security_score":49.5,"reliability_score":33.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T20:01:43.832834+00:00","interface":{"has_rest_api":true,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"http://localhost:8081/sse","has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["OMDB_API_KEY (server-side configuration for upstream OMDB access)"],"oauth":false,"scopes":false,"notes":"No user-facing auth is described for the MCP/HTTP endpoints; authentication appears to be limited to the upstream OMDB API key used by the server."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Uses OMDB API (which may have its own plan/limits). The MCP server itself is MIT-licensed (self-host)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":68.5,"security_score":49.5,"reliability_score":33.8,"mcp_server_quality":85.0,"documentation_accuracy":75.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":90.0,"rate_limit_clarity":40.0,"tls_enforcement":80.0,"auth_strength":35.0,"scope_granularity":20.0,"dependency_hygiene":45.0,"secret_handling":70.0,"security_notes":"Mentions non-root Docker user, vulnerability scanning, and 'no sensitive data in images' plus HTTPS support for external APIs. However, no clear inbound authentication/authorization for the server endpoints is described; upstream access relies on an OMDB API key, and the server exposes cache management endpoints that could be abused if network-access is not restricted.","uptime_documented":20.0,"version_stability":30.0,"breaking_changes_history":30.0,"error_recovery":55.0,"idempotency_support":"true","idempotency_notes":"Tool calls are reads (search/details); repeated calls should be safe. Cache clear endpoints are destructive and not idempotent-safe across concurrent agents without coordination.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["OMDB responses/limits are ultimately upstream-dependent; tool calls may fail due to OMDB key/rate limiting.","Search results may vary by OMDB availability/fields; agents should not assume deterministic ordering or completeness.","Cache management endpoints (/cache/clear*) are potentially disruptive if multiple agents share the same server instance."]}}