{"id":"linuxserver-duckdns","name":"duckdns","homepage":"https://hub.docker.com/r/linuxserver/duckdns","repo_url":"https://hub.docker.com/r/linuxserver/duckdns","category":"infrastructure","subcategories":[],"tags":["dynamic-dns","dns","automation","networking"],"what_it_does":"duckdns is a service/package for updating DuckDNS dynamic DNS records (mapping a domain like *.duckdns.org to an IP). It typically supports running an automated updater to keep DNS records current.","use_cases":["Dynamic DNS for home lab servers with changing public IPs","Exposing services behind consumer internet connections","Updating DNS for VPN endpoints or remote-access hosts","Lightweight automated DNS updates for small deployments"],"not_for":["Enterprise DNS hosting with advanced routing/DNS features","Use cases requiring high-assurance, audited security controls","Systems that need strict rate-limit SLAs or robust API contracts"],"best_when":"You need simple, automated dynamic DNS updates to DuckDNS for non-critical infrastructure.","avoid_when":"You require strong, well-specified API integrations, fine-grained access control, or a production-grade DNS platform.","alternatives":["Cloudflare DNS + API automation (if you own domains/records)","No-IP (dynamic DNS)","DynDNS providers with stronger APIs/SLAs","Self-hosted dynamic DNS using tools like ddclient with your own DNS"],"af_score":25.8,"security_score":36.8,"reliability_score":31.2,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:28:08.369925+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":["Typically uses DuckDNS-style authentication via a token/key included in requests (exact method depends on the implementation)"],"oauth":false,"scopes":false,"notes":"No evidence here of OAuth or fine-grained scopes; dynamic DNS updaters usually use a shared token."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"DuckDNS is commonly free; however, pricing details are not provided in the supplied content."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":25.8,"security_score":36.8,"reliability_score":31.2,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":60.0,"rate_limit_clarity":10.0,"tls_enforcement":60.0,"auth_strength":35.0,"scope_granularity":10.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"Likely uses a shared token for updates (common with DuckDNS-style services), which is weaker than scoped/rotatable OAuth credentials. Exact secret-handling practices (env vars vs logs) and dependency hygiene cannot be verified from the provided prompt.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Dynamic DNS updates are sensitive to incorrect IP detection (agents should verify WAN/public IP source).","Authentication is typically a shared token; careless logging can leak credentials.","Update frequency/rate limits may exist even if not clearly documented; aggressive retries can trigger failures."]}}