{"id":"pihole-mcp-server","name":"pihole-mcp-server","af_score":53.8,"security_score":63.5,"reliability_score":26.2,"what_it_does":"Provides an MCP server (and CLI) to manage a Pi-hole DNS server from AI assistants/IDE clients, supporting both legacy Pi-hole (admin/api.php with API token) and modern Pi-hole (api/* with web interface password).","best_when":"You run Pi-hole on a trusted LAN and want an MCP client to automate administrative tasks interactively.","avoid_when":"You cannot store credentials securely on the host, or you need strict protections against an agent making destructive/unauthorized changes.","last_evaluated":"2026-04-04T21:48:34.257898+00:00","has_mcp":true,"has_api":false,"auth_methods":["Legacy Pi-hole API token (admin/api.php)","Modern Pi-hole web interface password (api/* endpoints)","Local credential storage via system keyring or encrypted file fallback"],"has_free_tier":false,"known_gotchas":["Agent may disable Pi-hole for a duration; ensure it asks for/chooses durations carefully.","Correct auth method depends on Pi-hole version; if detection fails, credentials may need to be re-entered via login/logout.","If SSL verification is disabled (no-verify-ssl), network-in-the-middle risk increases; keep verification enabled when possible.","Because credentials are stored locally, ensure the MCP server host is access-controlled to prevent other users/processes from invoking it with stored secrets."],"error_quality":0.0}