crab-hole-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRAB_HOLE_SSH_HOST | Yes | The hostname or IP address of the Crab-hole server to SSH into. | |
| CRAB_HOLE_MUTATIONS_ENABLED | No | Set to 'true' to enable mutation tools such as replace_crab_hole_config, add_custom_rule, etc. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_crab_hole_configA | Read the complete active Crab-hole TOML configuration and its SHA-256 revision. |
| validate_crab_holeA | Run Crab-hole's native configuration and list validators without changing anything. |
| validate_proposed_configA | Validate complete proposed Crab-hole TOML without installing or activating it. |
| list_config_backupsA | List configuration and custom-rule backups created by this MCP. |
| crab_hole_statusA | Inspect service health, version, current block count, rule counts, memory, and the latest blocklist refresh. |
| check_domainA | Resolve a domain through the live Crab-hole backend and report whether it is blocked. |
| list_custom_rulesA | List custom allow or block entries currently stored on the DNS server. |
| list_blocklistsA | List the live and local blocklist sources configured in Crab-hole. |
| recent_logsA | Read recent Crab-hole service logs, optionally restricted to errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: config reading, validation, backups, status, domain lookup, custom rules, blocklists, and logs. The only overlapping pair is validate_crab_hole and validate_proposed_config, but the descriptions clearly separate native validators from proposed TOML validation.
Most tools use snake_case with verb prefixes like get_, validate_, list_, and check_, but crab_hole_status and recnt_logs are noun phrases without verbs. The mixed conventions are readable but not fully consistent.
Nine tools is a well-scoped size for a DNS configuration and observability server. Each tool serves a distinct purpose without creating reduntant bloat or leaving the surface feeling too thin.
The read, validate, and inspect capabilities are well covered, but there are no tools to apply config, restore backups, add or remove custom rules/blocklists, or toggle blocking. These are notable lifecycle gaps for a tool named as a Crap-hole management server.