{"id":"linuxserver-netbootxyz","name":"netbootxyz","homepage":"https://hub.docker.com/r/linuxserver/netbootxyz","repo_url":"https://hub.docker.com/r/linuxserver/netbootxyz","category":"infrastructure","subcategories":[],"tags":["netboot","pxe","ipxe","provisioning","bare-metal","bootloader","infrastructure"],"what_it_does":"netbootxyz is an open-source netboot/iPXE environment for deploying operating systems over the network. It provides boot images, configuration, and discovery to serve installers/kernels and chainload boot targets for bare-metal provisioning.","use_cases":["Provisioning bare-metal servers and workstations with OS installers over the network","Building lightweight PXE/iPXE boot menus for lab or enterprise imaging workflows","Running automated deployments for multiple OS versions and hardware configurations","Homelab/server rack deployments where physical media is inconvenient"],"not_for":["Use as a general-purpose API service","Workloads requiring fine-grained tenant authorization/authz (multi-tenant SaaS model)","Environments that cannot accept running network boot services (DHCP/TFTP/HTTP) on the network"],"best_when":"You have a controlled LAN (or properly firewalled environment) and want repeatable network OS installs via PXE/iPXE/HTTP boot with a flexible boot menu.","avoid_when":"You need a cloud-hosted managed service with strict compliance guarantees out-of-the-box or you cannot manage boot service security and network exposure.","alternatives":["iPXE + custom scripts/menus","Foreman + TFTP/PXE/boot discovery","SUSE/Ubuntu/Debian installer netboot tooling (customized)","Rancher Fleet/Rolling imaging systems (for container/host provisioning workflows)","U-Boot/iPXE-based custom boot infrastructure"],"af_score":15.0,"security_score":21.2,"reliability_score":26.2,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:43:41.046992+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":"Network boot infrastructure typically relies on network-level controls (e.g., segmentation/firewalls) rather than application-layer authentication; no API-style auth mechanism is evident from the provided package name/description."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Open-source software; costs are primarily operational (hosting, bandwidth, admin time). No usage-based pricing is indicated."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":15.0,"security_score":21.2,"reliability_score":26.2,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":20.0,"rate_limit_clarity":0.0,"tls_enforcement":10.0,"auth_strength":15.0,"scope_granularity":0.0,"dependency_hygiene":50.0,"secret_handling":40.0,"security_notes":"Security is primarily network/service exposure: ensure boot services are isolated (VLAN/firewall) because PXE/iPXE can be abused if accessible. Application-layer auth is likely minimal/absent. TLS/encryption is generally not central to TFTP/PXE flows; HTTP-based asset fetching may use plain HTTP unless separately configured.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":40.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Not an API product: an agent cannot 'call' it; it requires infrastructure deployment and configuration (DHCP/TFTP/HTTP and boot menu assets).","Network boot environments are sensitive to LAN topology, firewall rules, and address/DNS/DHCP configuration.","Boot-time failures often require inspecting iPXE/PXE logs and served assets rather than handling structured API errors.","If the project updates boot menus/images, configuration drift may occur and may require careful version control."]}}