{"id":"dimensiondataresearch-mcp2-dhcp-server","name":"mcp2-dhcp-server","homepage":null,"repo_url":"https://github.com/DimensionDataResearch/mcp2-dhcp-server","category":"infrastructure","subcategories":[],"tags":["dhcp","dns","pxe","ipxe","tftp","boot-provisioning","cloudcontrol","mcp2","go"],"what_it_does":"Runs a DHCP server with optional DNS and optional PXE/iPXE boot support. DHCP/DNS records are driven by MCP 2.0 server metadata from Dimension Data CloudControl; DNS can serve a pseudo-zone for A/AAAA/PTR records and forward other queries to a fallback resolver. PXE/iPXE clients get boot configuration/scripts (with optional overrides via server tags).","use_cases":["Network boot (PXE/iPXE) of cloud-init-capable OSes (e.g., CoreOS/Container Linux, RancherOS)","Dynamic DHCP assignment tied to CloudControl/MCP metadata","Providing DNS answers for a pseudo-zone derived from MCP server metadata","Boot-time customization using CloudControl server tags (pxe_boot_image, ipxe_profile, ipxe_boot_script)"],"not_for":["Internet-facing DNS/DHCP without network controls (it’s a LAN boot/infrastructure component)","General-purpose DNS hosting for real domains beyond the pseudo-zone","Agent workflows needing an HTTP API/SDK for querying/updating configuration"],"best_when":"You need centralized, metadata-driven netboot provisioning within a controlled network and can integrate with Dimension Data CloudControl MCP 2.0 metadata.","avoid_when":"You require a standard REST/GraphQL API, public exposure, or strong, well-documented operational controls (rate limiting, observability, explicit error codes) beyond what’s described.","alternatives":["ISC DHCP","dnsmasq (DHCP+DNS on the same host)","Kea DHCP","CoreOS/iPXE tooling such as coreos-ipxe-server (mentioned in README)","Dedicated PXE/iPXE servers with separate config management (TFTP/HTTP boot infrastructure)"],"af_score":19.2,"security_score":32.2,"reliability_score":17.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:45:52.819641+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":["MCP username/password configured in mcp2-dhcp-server.yml"],"oauth":false,"scopes":false,"notes":"No standard API auth described; MCP access appears to be via static credentials in config."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted open-source component; costs are infrastructure/runtime plus any upstream CloudControl/MCP service costs."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":19.2,"security_score":32.2,"reliability_score":17.5,"mcp_server_quality":0.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":35.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":45.0,"scope_granularity":10.0,"dependency_hygiene":40.0,"secret_handling":25.0,"security_notes":"Communications security is not described (no TLS mention for MCP or DNS). MCP credentials are provided in a YAML config, and the README does not describe secret-storage hygiene (env vars/vault) or logging redaction. Service expands attack surface via DHCP/DNS/PXE; strong network isolation and access controls are implied but not documented.","uptime_documented":0.0,"version_stability":20.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":["Not an agent-facing API package: it is a network service (DHCP/DNS/PXE/iPXE).","Authentication is via configuration credentials (MCP user/password) rather than an API flow.","Operational/agent concerns like rate limits, structured error codes, and retry guidance are not described in the provided README."]}}