Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

DNSFilter MCP

by servosityversion 0.1.1i★ –iRuns on your computer
Registry nameio.github.Servosity/dnsfilter-mcp

Install

Overview

Description from the maker (original English)

DNSFilter for MSPs: why a site is blocked, preview-first allows, unblock requests, agent drift.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: DNSFILTER_API_KEY, DNSFILTER_MCP_HTTP_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: DNSFILTER_BASE_URL, DNSFILTER_API_KEY, DNSFILTER_USER_AGENT, DNSFILTER_MCP_READ_ONLY, DNSFILTER_NO_LOCAL_DATA, DNSFILTER_MCP_HTTP_TOKEN, PRINTING_PRESS_CLIENT_PROFILE

Values marked secret are keys to your account. Never share them or paste them into a chat.

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

Fill in the empty values before running it.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • DNSFILTER_BASE_URL env
    Optional: DNSFilter API base URL (default https://api.dnsfilter.com).
  • DNSFILTER_API_KEY secret required env
    DNSFilter API token (bare token, no Bearer prefix), from Account Settings, API Tokens.
  • DNSFILTER_USER_AGENT env
    Optional: override the User-Agent the CLI sends.
  • DNSFILTER_MCP_READ_ONLY env
    Optional: set to 1 so the MCP server offers DNSFilter reads only, without secret-bearing reads.
  • DNSFILTER_NO_LOCAL_DATA env
    Optional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.
  • DNSFILTER_MCP_HTTP_TOKEN secret env
    Bearer token callers must present when the server runs with --transport http; not used by stdio.
  • PRINTING_PRESS_CLIENT_PROFILE env
    Not enforced by this connector (no tenant-gated profiles); leave unset. It does not limit access.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account servosity, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32476 servers in this category
  • Published to the registry more recently than 97% of the other 32476 servers in this category
  • Basic checks equal to or better than 100% of the other 32476 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is DNSFilter MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: DNSFILTER_API_KEY, DNSFILTER_MCP_HTTP_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, zanadir

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

zanadir

by MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

DNSFilter + AI - for ChatGPT, Claude, GitHub Copilot, Microsoft 365 Copilot, Gemini, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the DNSFilter

API. Not affiliated with, endorsed by, or sponsored by DNSFilter, Inc.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

Every DNSFilter API operation, plus one-command answers to 'why is this site blocked for this client' and 'which clients are behind on the roaming agent'. Works with the AI you already use - ChatGPT (Plus/Pro+), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Microsoft 365 Copilot / Copilot Studio and Google Gemini via the remote path. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

Your AI agentHow to install the DNSFilter skill
Claude DesktopRun installer, then Settings > Extensions to register dnsfilter-mcp (no JSON editing).
ChatGPT (paid plans)Run installer, host dnsfilter-mcp over HTTPS with DNSFILTER_MCP_HTTP_TOKEN set, then register it as a Developer Mode connector if your connector settings can send the bearer token.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add dnsfilter-mcp to mcp.json under the servers key, then pick Agent mode.

For ChatGPT, run dnsfilter-mcp --transport http with DNSFILTER_MCP_HTTP_TOKEN set, on an HTTPS host; every request sends that token. See mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: these are the remote / enterprise path, not the local binary you just installed.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot self-serve. Host dnsfilter-mcp over HTTPS with DNSFILTER_MCP_HTTP_TOKEN set, then wire it into Copilot Studio (Tools > Add a tool > Model Context Protocol > Server URL) or a declarative agent, if it can send the bearer token. Needs a Copilot Studio license + tenant admin. See mcp-install.md.
Google GeminiGemini CLI is local - same as Claude Code. The Gemini app is remote - same HTTPS path as ChatGPT. See mcp-install.md.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download DNSFilter MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every DNSFilter release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install dnsfilter@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the DNSFilter Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/dnsfilter/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/dnsfilter/install.ps1 | iex. Then authenticate per the README and run dnsfilter-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/dnsfilter/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/dnsfilter/install.sh)

The installer drops both dnsfilter-cli (the CLI) and dnsfilter-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

dnsfilter-cli --version
Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/dnsfilter/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/dnsfilter/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update dnsfilter@msp-skills.

Add to Claude Desktop, GitHub Copilot, Gemini CLI, Microsoft 365 Copilot, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the remote Microsoft 365 Copilot / Copilot Studio path. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/dnsfilter --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/dnsfilter --force

Hermes speaks MCP natively, so it can also use the dnsfilter-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the dnsfilter skill from https://github.com/servosity/msp-skills/tree/main/skills/dnsfilter. The skill defines how its required CLI (dnsfilter-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Create an API token in the DNSFilter dashboard (in your MSP organization, so the cross-client commands see your client orgs) and set it as DNSFILTER_API_KEY. Use the token itself: DNSFilter expects the bare token in the Authorization header, with no Bearer prefix.

macOS / Linux:

DNSFILTER_API_KEY=<value> dnsfilter-cli doctor

On Windows (PowerShell):

$env:DNSFILTER_API_KEY = "<value>"

dnsfilter-cli doctor

To save the token instead of setting it each session, pipe it to dnsfilter-cli auth set-token (it reads stdin, so the token never lands in your shell history as an argument):

printf '%s\n' "$DNSFILTER_API_KEY" | dnsfilter-cli auth set-token

On Windows (PowerShell):

$env:DNSFILTER_API_KEY | dnsfilter-cli auth set-token

doctor checks config, paths and API reachability, and sends the token to DNSFilter's GET /v1/current_user, so a rejected token shows up as a Credentials: invalid row, a token that lacks access (HTTP 403) as WARN scope-limited, and a wrong base URL as an API: ERROR row. An answer that was redirected away from the DNSFilter API, or that is not a current-user record, never counts as proof (WARN not verified), and a cache whose last sync was incomplete is not fresh. It exits 0 even then, so scripts should add --fail-on error (or --fail-on warn, which also fails on a 403, an unverified probe or an incomplete sync). It also warns when a stored token starts with Bearer or Token .

What this skill does

Question your MSP keeps askingCommand
Why is this domain blocked for this client, and which policy and rule did it?dnsfilter-cli why-blocked "example.com" --org "Acme Dental"
Allow it on the policies that actually blocked it (preview first)dnsfilter-cli allow "example.com" --org "Acme Dental" --note "TKT-4821"
What unblock requests are waiting across every client, grouped by domain?dnsfilter-cli unblocks triage
Which clients have roaming clients behind the latest agent release?dnsfilter-cli agents drift
Who is still on the roaming client build that got pulled?dnsfilter-cli agents drift --bad-version 1.7.15 --agent-type windows
Which roaming clients stopped checking in, or are unprotected or bypassed?dnsfilter-cli agents stale --older-than 7d
Which client policies already allow or block this domain or a parent domain?dnsfilter-cli lists where "example.com"
Which allow-listed domains are now categorized as threats, and which policies leave security categories unblocked?dnsfilter-cli policy-audit

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most DNSFilter integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which of my 60 client orgs still have Windows roaming clients on the build DNSFilter just pulled" or "why is this site blocked for this one client right now".

This skill syncs DNSFilter into a local SQLite mirror with full-text search, so agents drift, agents stale and lists where answer one local query across every client org, joining roaming clients to their sites, sites to their organizations and policies. agents drift reads DNSFilter's release feed live on every run, so a pulled release does not linger in a stale copy. why-blocked and allow work live: they resolve the client's current policy (scheduled-policy slot included), walk DNSFilter's documented rule order, read the Query Log, and say which rule types the API does not expose, which is the chain a stateless API wrapper leaves the AI to assemble call by call.

It complements the DNSFilter dashboard rather than replacing it: policies, deployments, reporting and the Query Log stay there.

The pain this closes

A blocked-site ticket is a chain, not a lookup: which policy the client's site or roaming client is using right now (scheduled policies switch by the quarter hour), that policy's allow list, block list and categories, and what the Query Log recorded. Then the fix has to land on the policy that actually blocked it, not a shared global one. A DNSFilter Community post, "Policy enforcement & reporting discrepancies with Roaming Client", describes a roaming client on a second site ign

Only the beginning is shown; read the rest in the repo

Ask PopNx