io.github.mrfentmen/pihole-mcp
pihole-mcp
Is the io.github.mrfentmen/pihole-mcp MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-30.
MCP server for Pi-hole: status, stats, blocking toggle. Works with any instance.
alive probed 2026-11-15 · unchanged since 2026-10-30
- Run it
- npx -y pihole-mcp@1.0.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- pihole-mcp 1.0.0
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- <0.1 % of a 1M context window
- Count
- 299 tokens in Claude Opus 5.5, exact, measured 2026-10-16. With the Claude Code prefix mcp__…__ on each tool name: 323. The o200k_base estimate is 157. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/mrfentmen/awesome-mcps
- Registry
- active, updated 2026-09-22 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.90×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| set_blocking | 196 | 103 | 66 % |
| status | 103 | 54 | 34 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.mrfentmen/phylip-mcp · alive
- io.github.mrfentmen/picolisp-mcp · alive
- io.github.mrfentmen/picsum-mcp · alive
- io.github.mrfentmen/piglatin-mcp · alive
- io.github.mrfentmen/pike-mcp · alive
- io.github.mrfentmen/pinata-mcp · alive
- io.github.mrfentmen/pingdom-mcp · alive
- io.github.mrfentmen/pinterest-mcp · alive
Servers that mention pihole.
- io.github.aplaceforallmystuff/mcp-pihole · alive
- Pi-hole MCP Server io.github.ranklancer/pihole-mcp · needs env
- Pi-hole MCP Server io.github.hexamatic/pihole-mcp · needs env
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.