{"id":"pedroperezmsft-iperf3-server","name":"iperf3-server","homepage":"https://hub.docker.com/r/pedroperezmsft/iperf3-server","repo_url":"https://hub.docker.com/r/pedroperezmsft/iperf3-server","category":"infrastructure","subcategories":[],"tags":["networking","bandwidth-testing","throughput","tcp","udp","benchmarking","iperf3","performance-troubleshooting"],"what_it_does":"iperf3-server is intended to run an iperf3 server endpoint to measure network performance (throughput) between a server and client over TCP and/or UDP, typically used in benchmarking and troubleshooting scenarios.","use_cases":["Measure network throughput and bandwidth between two hosts","Validate network changes (routing, firewall rules, link upgrades)","Benchmark TCP/UDP performance for capacity planning","Troubleshoot latency/packet-loss/bottlenecks using iperf3 test results"],"not_for":["Production application traffic delivery","Security-sensitive multi-tenant environments without external isolation","API-based or REST-driven network measurement workflows (iperf3 is a CLI/protocol tool, not an HTTP service)"],"best_when":"You need repeatable, host-to-host network performance testing in a controlled environment where you can run iperf3 server and an iperf3 client.","avoid_when":"You cannot control firewalling/access to the iperf3 port(s), or you require a programmatic HTTP/SDK interface with authentication and rate limiting.","alternatives":["iperf2 (legacy)","netperf","sockperf","nuttcp","Cloud-based or vendor network testing tools","Prometheus/node_exporter + blackbox_exporter for continuous network monitoring (not iperf-style throughput tests)"],"af_score":25.8,"security_score":23.0,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:29:58.254506+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":"iperf3 server processes traffic directly; any authentication is typically handled externally (network isolation/firewall/VPN) rather than built into an API layer."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"As an iperf3-based server tool, pricing is generally not applicable (open-source tool)."},"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":23.0,"reliability_score":32.5,"mcp_server_quality":0.0,"documentation_accuracy":0.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":10.0,"scope_granularity":0.0,"dependency_hygiene":30.0,"secret_handling":80.0,"security_notes":"Security is primarily about network exposure control (firewall/VPN/segmentation). iperf3 traffic typically lacks application-layer encryption/auth; use transport/network isolation to prevent unauthorized testing or traffic shaping risks. Dependency hygiene and CVE status cannot be assessed from the provided information.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["iperf3-style measurement is not a request/response API; an agent must orchestrate starting the server and running a compatible client test.","Test results depend on environment and parameters (TCP/UDP, parallel streams, duration, window sizes); agents may need to tune flags to get meaningful comparisons.","Without external access controls, exposing the iperf3 server port can allow arbitrary throughput testing traffic."]}}