{"id":"wuhuan123-jd-h5st-server","name":"jd_h5st_server","homepage":"https://hub.docker.com/r/wuhuan123/jd_h5st_server","repo_url":"https://hub.docker.com/r/wuhuan123/jd_h5st_server","category":"devtools","subcategories":[],"tags":["devtools","api","authentication","signature-generation","anti-bot"],"what_it_does":"jd_h5st_server appears to be a server component intended to generate or serve a specific request-signing/anti-bot header value (often seen as jd_h5st for JD/7Fresh-style APIs). Based on the package name alone, it likely exposes an HTTP service that returns the computed signature for client requests.","use_cases":["Generating request signature/header values for JD-style web/API requests","Centralizing signature computation in a backend service to simplify client integration","Automating authenticated requests to upstream endpoints that require an h5st-style signature"],"not_for":["General-purpose data APIs (its purpose is likely narrow to signature/header generation)","Use as a security boundary for protecting sensitive user data (it likely only helps with signature generation)","Requirements for official SDK-level support or long-lived public API compatibility (not enough evidence)"],"best_when":null,"avoid_when":null,"alternatives":["Implement the h5st/signature algorithm directly in your own service (if you have authoritative specs/source)","Use an official SDK or official authentication flow if available for the target service","Third-party signature services with clear contracts, documentation, and security assurances"],"af_score":25.2,"security_score":37.5,"reliability_score":20.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:26:50.765798+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 explicit authentication details were provided in the input. Many such signature services use an API key or no auth; this could not be verified here."},"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 provided."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":25.2,"security_score":37.5,"reliability_score":20.0,"mcp_server_quality":0.0,"documentation_accuracy":20.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":40.0,"scope_granularity":0.0,"dependency_hygiene":50.0,"secret_handling":40.0,"security_notes":"Insufficient package content was provided to validate TLS, authentication method, scope controls, dependency health, and secret handling. Signature services often process sensitive tokens/cookies or generate headers that can be abused; robust auth, logging hygiene, and strict input validation are important but could not be confirmed.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":30.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Signature-generation endpoints can be sensitive to input formatting (method/path/query/body canonicalization, timestamps, encoding).","If the service has anti-abuse limits, agents may trigger throttling without clear retry guidance.","If no idempotency semantics are provided, retries could generate different signatures depending on timestamp/nonce."]}}