adguardhome-mcp

MCPcommunity

v1.0.0io.github.mrfentmenMITUpdated 11d agonpm GitHub

Query your AdGuard Home: status, stats, query log. Endpoints per official docs.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

547Downloads/wk

11d agoLast update

Package

Authorio.github.mrfentmen

LicenseMIT

Version1.0.0

Sourcenpm+mcp-registry

npmadguardhome-mcp

GitHubmrfentmen/premium-mcps

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface6 tools · none privileged

Security scan✓ Cleanv1.0.2 · 10d agoHow well does this scan work?

EvalsNone

IndexedOct 3, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged

Statically extracted from the published packagev1.0.2 · 10d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_statusDNS protection state: enabled, filters and upstreams.

DNS protection state: enabled, filters and upstreams.

No input schema was published for this tool.

get_statsQuery and blocked-request counters, total and average.

Query and blocked-request counters, total and average.

No input schema was published for this tool.

get_query_logRecent DNS queries with client, domain and action.

Recent DNS queries with client, domain and action.

No input schema was published for this tool.

filter_rule_auditWhat a published AdGuard filter list actually contains, read straight from the list with no AdGuard Home instance: its title, version and last-modified, the rule count against the comment count, a breakdown by AdGuard syntax (||domain^, hosts-file, regular expression, cosmetic ##selector, plain sub…

What a published AdGuard filter list actually contains, read straight from the list with no AdGuard Home instance: its title, version and last-modified, the rule count against the comment count, a breakdown by AdGuard syntax (||domain^, hosts-file, regular expression, cosmetic ##selector, plain sub…

No input schema was published for this tool.

domain_coverageWhether one domain is genuinely covered by a published AdGuard list, which is not the same as finding the string in the file: it checks the domain exactly, then every parent up to the registrable domain, because a rule for a parent also covers all subdomains, and it reports any @@ exception that wo…

Whether one domain is genuinely covered by a published AdGuard list, which is not the same as finding the string in the file: it checks the domain exactly, then every parent up to the registrable domain, because a rule for a parent also covers all subdomains, and it reports any @@ exception that wo…

No input schema was published for this tool.

filter_catalogDiscover published AdGuard DNS filter lists by name or description, with registry versions, update dates and download URLs.

Discover published AdGuard DNS filter lists by name or description, with registry versions, update dates and download URLs.

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Query your AdGuard Home: status, stats, query log. Endpoints per official docs.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

6 tools · none privileged · observed 2026-10-03 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

get_status
get_stats
get_query_log
filter_rule_audit
domain_coverage
filter_catalog

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-03 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
@modelcontextprotocol/sdk1.32.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.8
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.6.5
- cors2.8.6+1 not drawn1 dependency
  - object-assign4.1.1
- hono4.13.12
- jose6.2.12
- express5.2.1+27 not drawn1 dependency
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.3
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 49
below the depth cap: 5

wrappy 1 — required by once@1.4.0package cap reached
http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.