Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pi-hole MCP Server

OCI · GHCR.IO/HEXAMATIC/PIHOLE-MCP

Manage Pi-hole v6: DNS blocking, domains, clients, query analysis, DHCP, and multi-instance sync.

Available components

oci · ghcr.io/hexamatic/pihole-mcp 20
20 Trust /100

Last scanned (6 hours ago)

Scores higher than 33% of OCI servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to hexamatic/pihole-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Nov 26 20

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/hexamatic/pihole-mcp@0.10.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via OCI referrers API
Source repo hexamatic/pihole-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/hexamatic/pihole-mcp/.github/workflows/release.yml@refs/tags/v0.10.0
Rekor log index 3637322612
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:d6c2d764d3bfd61f30404b6cf176c9032b5afa812de52d64ac9d8dacdbfbc9c8

Background: How many MCP packages publish verified provenance →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Pi-hole MCP Server server?

Pi-hole MCP Server runs locally as a container image, launched with docker run --rm -i -e PIHOLE_URL -e PIHOLE_PASSWORD -e TZ -e PIHOLE_READ_ONLY -e PIHOLE_TLS_SKIP_VERIFY -e PIHOLE_REQUEST_TIMEOUT -e PIHOLE_MAX_RETRIES -e PIHOLE_RETRY_MAX_DELAY ghcr.io/hexamatic/pihole-mcp:0.10.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/hexamatic/pihole-mcp

# add to Claude Code
claude mcp add hexamatic-pihole-mcp -- docker run --rm -i -e PIHOLE_URL -e PIHOLE_PASSWORD -e TZ -e PIHOLE_READ_ONLY -e PIHOLE_TLS_SKIP_VERIFY -e PIHOLE_REQUEST_TIMEOUT -e PIHOLE_MAX_RETRIES -e PIHOLE_RETRY_MAX_DELAY ghcr.io/hexamatic/pihole-mcp:0.10.0

This image reads PIHOLE_URL, PIHOLE_PASSWORD, TZ, PIHOLE_READ_ONLY, PIHOLE_TLS_SKIP_VERIFY, PIHOLE_REQUEST_TIMEOUT, PIHOLE_MAX_RETRIES and PIHOLE_RETRY_MAX_DELAY. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Pi-hole MCP Server server?

Pi-hole MCP Server is listed in the public MCP registry as io.github.hexamatic/pihole-mcp. Manage Pi-hole v6: DNS blocking, domains, clients, query analysis, DHCP, and multi-instance sync. This page covers its container image (ghcr.io/hexamatic/pihole-mcp).

Is the Pi-hole MCP Server server safe to use?

Pi-hole MCP Server scores 20 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Pi-hole MCP Server server still maintained?

Pi-hole MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Pi-hole MCP Server server under?

Pi-hole MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.