HTTP vs Pi-hole MCP Server
HTTP is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 1 (Official MCP Registry). Pi-hole MCP Server is an MCP server published by hexamatic. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  HTTP |   Pi-hole MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (npm): 108 Downloads/week (npm): 15 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.9.0 Forks (GitHub): 2 Stars (GitHub): 8 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | HTTP | Pi-hole MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 8 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@abhishekmcp/http) | On your machine (ghcr.io/hexamatic/pihole-mcp:0.9.0) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 8, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/abhishekkumar2021/mcp-suite | github.com/hexamatic/pihole-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
HTTP
HTTP/REST client with saved collections, env secrets, and SSRF-safe host allowlisting.
Pi-hole MCP Server
Manage Pi-hole v6: DNS blocking, domains, clients, query analysis, DHCP, and multi-instance sync.
How to run each
HTTP As a local MCP server: npm package
claude mcp add --env "HTTP_ALLOW_HOSTS=<YOUR_HTTP_ALLOW_HOSTS>" --transport stdio http -- npx -y @abhishekmcp/httpRequires: HTTP_ALLOW_HOSTS
Pi-hole MCP Server As a local MCP server: Docker image
claude mcp add --env "PIHOLE_PASSWORD=<YOUR_PIHOLE_PASSWORD>" --env "PIHOLE_URL=<YOUR_PIHOLE_URL>" --transport stdio pihole-mcp -- docker run -i --rm -e PIHOLE_PASSWORD -e PIHOLE_URL ghcr.io/hexamatic/pihole-mcp:0.9.0Requires: PIHOLE_PASSWORD (secret), PIHOLE_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only HTTP asks for
HTTP_ALLOW_HOSTSHTTP_WRITABLE
Only Pi-hole MCP Server asks for
PIHOLE_MAX_RETRIESPIHOLE_PASSWORD (secret)PIHOLE_READ_ONLYPIHOLE_REQUEST_TIMEOUTPIHOLE_RETRY_MAX_DELAYPIHOLE_TLS_SKIP_VERIFYPIHOLE_URLTZ
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HTTP · What it can do: Pi-hole MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.