ToolsMCP
adguardhome-mcp
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- mrfentmen (GitHub)
- Prerequisites
- Install adguardhome-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.0.0 · updated
- Official links
Publisher’s description
Query your AdGuard Home: status, stats, query log. Endpoints per official docs.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.0, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- mrfentmen (GitHub)
- Version observed
- 1.0.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.mrfentmen%2Fadguardhome-mcp/versions/1.0.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Search official technical documentation | Publisher description mentions “query log. endpoints per official docs”, “docs”. | No connection check or task run. Capability is as described by the publisher. | Rule documentation-search matched: “query log. endpoints per official docs”, “docs”. Rule documentation-search. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
adguardhome-mcp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.mrfentmen/adguardhome-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.