# @samik081/mcp-adguard-home

Manage AdGuard Home through AI assistants

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.9.0
- **Author:** io.github.Samik081
- **License:** MIT
- **npm:** @samik081/mcp-adguard-home
- **Source:** https://github.com/Samik081/mcp-adguard-home
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 9 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-19T16:44:50.839Z
- **Version scanned:** 0.9.0
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `access_get_list`
- `access_set_list`
- `blocked_services_get_all`
- `blocked_services_get`
- `blocked_services_update`
- `clients_get`
- `clients_search`
- `clients_add`
- `clients_update`
- `clients_delete`
- `dhcp_get_status`
- `dhcp_get_interfaces`
- `dhcp_find_active`
- `dhcp_set_config`
- `dhcp_add_static_lease`
- `dhcp_remove_static_lease`
- `dhcp_update_static_lease`
- `dhcp_reset`
- `dhcp_reset_leases`
- `dns_get_info`
- `dns_test_upstream`
- `dns_set_config`
- `dns_clear_cache`
- `filtering_get_status`
- `filtering_check_host`
- `filtering_set_config`
- `filtering_add_url`
- `filtering_remove_url`
- `filtering_set_url`
- `filtering_refresh`
- `filtering_set_rules`
- `global_get_status`
- `global_get_profile`
- `global_check_version`
- `global_set_protection`
- `global_update_profile`
- `global_begin_update`
- `install_get_addresses`
- `install_check_config`
- `install_apply_config`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-adguard-home\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@samik081/mcp-adguard-home\"\n      ],\n      \"env\": {\n        \"ADGUARD_USERNAME\": \"<YOUR_ADGUARD_USERNAME>\",\n        \"ADGUARD_PASSWORD\": \"<YOUR_ADGUARD_PASSWORD>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `ADGUARD_USERNAME` — Adguard Username (required)
- `ADGUARD_PASSWORD` — Adguard Password (required)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 2 credentials (2 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 59, ceiling 59 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40samik081%2Fmcp-adguard-home
- Install plan: https://forgeregistry.com/api/v1/packages/%40samik081%2Fmcp-adguard-home/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40samik081%2Fmcp-adguard-home
- HTML page: https://forgeregistry.com/registry/%40samik081%2Fmcp-adguard-home
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.