{"id":"liaad-yake-server","name":"yake-server","homepage":"https://hub.docker.com/r/liaad/yake-server","repo_url":"https://hub.docker.com/r/liaad/yake-server","category":"ai-ml","subcategories":[],"tags":["nlp","keyword-extraction","yake","server","http","api"],"what_it_does":"yake-server provides a server wrapper around the YAKE (Yet Another Keyword Extractor) algorithm, exposing keyword extraction via an HTTP service (typically to extract keywords/keyphrases from text).","use_cases":["Extracting keywords/keyphrases from user-provided text","Building lightweight NLP features without heavy ML model dependencies","Document classification support via keyword features","Search indexing/ranking enrichment using extracted keywords"],"not_for":["Production deployment requiring strict enterprise-grade API governance (unless the server adds those features)","Use as a source of truth for semantic understanding beyond keyword extraction","Handling very large documents without considering server performance/memory limits"],"best_when":"You need quick keyword extraction and want to call a reusable HTTP service rather than embedding YAKE in every app.","avoid_when":"You require advanced access control, tenant isolation, or clearly documented SLAs/error semantics from the server implementation.","alternatives":["Direct use of a YAKE library in-process","KeyBERT or other transformer-based keyword extraction (more semantic, heavier)","TextRank/RAKE-based extractors","spaCy + noun-chunk heuristics (lighter but less extractive)"],"af_score":29.8,"security_score":38.5,"reliability_score":10.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:31:30.167472+00:00","interface":{"has_rest_api":true,"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 authentication details were provided in the prompt content. Server likely runs without auth unless configured externally (not verifiable here)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":null},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":29.8,"security_score":38.5,"reliability_score":10.0,"mcp_server_quality":0.0,"documentation_accuracy":25.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":0.0,"tls_enforcement":50.0,"auth_strength":20.0,"scope_granularity":20.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Security posture is unknown from the provided prompt content. Since this is a generic server wrapper, security depends on the implementation (TLS termination, auth/rate limiting, input size validation, and whether logs accidentally capture full input text). Keyword extraction often processes user text, so careful logging/redaction is important to avoid leaking sensitive text.","uptime_documented":0.0,"version_stability":0.0,"breaking_changes_history":0.0,"error_recovery":40.0,"idempotency_support":"true","idempotency_notes":"Keyword extraction is typically a pure function of input text; if implemented as a POST with no side effects, it should be idempotent, but this is not confirmed by provided content.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Potential absence of explicit request/response schema (harder for agents to build correct calls).","If the server accepts free-form text without limits, agents may accidentally send very large payloads causing timeouts.","If no auth/rate limits are documented, agents may overload the service during retries or parallel calls."]}}