{"id":"lordsimpson-iperf3-server","name":"iperf3-server","homepage":"https://hub.docker.com/r/lordsimpson/iperf3-server","repo_url":"https://hub.docker.com/r/lordsimpson/iperf3-server","category":"infrastructure","subcategories":[],"tags":["networking","performance-testing","throughput","bandwidth","diagnostics"],"what_it_does":"iperf3-server appears to be a server-side component for iperf3 network performance testing, typically used to run bandwidth/throughput measurements between a client and a server.","use_cases":["Measuring network throughput/latency between two hosts","Baseline network performance before/after infrastructure changes","Capacity planning and troubleshooting (bottlenecks, link saturation)","Validating performance over different paths/VLANs/peering"],"not_for":["Production traffic serving for applications","Secure remote administration of a network without network controls","Internet-facing untrusted environments without firewalling/rate controls"],"best_when":"When you control both endpoints (or can tightly firewall access) and want repeatable network performance measurements.","avoid_when":"When you need a strongly authenticated, user-facing API or when exposing it broadly to untrusted networks.","alternatives":["iperf2","nuttcp","netperf","sockperf","Mininet-based synthetic tests (for virtual environments)"],"af_score":31.0,"security_score":24.5,"reliability_score":35.0,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:54:20.183962+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":[],"oauth":false,"scopes":false,"notes":"No authentication mechanism could be determined from the provided information; iperf3-style servers commonly rely on network-layer controls (firewalls) rather than app-level auth."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"This is typically an open-source/local tool; 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":31.0,"security_score":24.5,"reliability_score":35.0,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":100.0,"rate_limit_clarity":0.0,"tls_enforcement":20.0,"auth_strength":10.0,"scope_granularity":0.0,"dependency_hygiene":40.0,"secret_handling":60.0,"security_notes":"Likely relies on network controls (firewalls, bind addresses, allowed clients) more than cryptographic transport/auth. Without explicit TLS/auth and with potentially open ports, exposure to untrusted networks increases risk. No dependency/security specifics were provided.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":40.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["This is likely a CLI-style network measurement tool rather than a request/response API; agent automation should treat it as a process invocation with structured output parsing.","Network tests can require UDP/TCP port access and sufficient privileges; failures may look like connectivity/timeouts rather than application-level errors."]}}