Spec Driven Development
de formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar
DNSFilter MCP
Resumen
Descripción del creador (original en inglés)
DNSFilter for MSPs: why a site is blocked, preview-first allows, unblock requests, agent drift.
Los tres pilares de PopNx MCP
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
- Opinión de usuariosiAún no hay reseñasLas reseñas se abrirán junto con las cuentas en una etapa posterior
- Nuestras revisiones básicasi1 de 1 superadasRevisado con información pública; el código aún no se ha escaneado
- UsoiAún sin medir★ –
Qué puedes hacer con él
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
- Conexión: Se ejecuta en tu computadora
- Transporte: stdio
- Categoría: Otros
- Debes completar: DNSFILTER_API_KEY, DNSFILTER_MCP_HTTP_TOKEN
Instalación
Elige la app de IA que usas y copia la configuración.
Antes de instalar
- Revisiones básicas: 1 de 1 superadas
- Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
- Debes completar tú:
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
Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Descargar el archivo .mcpb del creador
El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.
Ejecuta esto en tu terminal
Completa los valores vacíos antes de ejecutarlo.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Valores que debes completar
DNSFILTER_BASE_URLenvOptional: DNSFilter API base URL (default https://api.dnsfilter.com).- DNSFilter API token (bare token, no Bearer prefix), from Account Settings, API Tokens.
DNSFILTER_USER_AGENTenvOptional: override the User-Agent the CLI sends.DNSFILTER_MCP_READ_ONLYenvOptional: set to 1 so the MCP server offers DNSFilter reads only, without secret-bearing reads.DNSFILTER_NO_LOCAL_DATAenvOptional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.- Bearer token callers must present when the server runs with --transport http; not used by stdio.
PRINTING_PRESS_CLIENT_PROFILEenvNot enforced by this connector (no tenant-gated profiles); leave unset. It does not limit access.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Qué puede hacer
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisiones básicasi
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
- ✓ Superada
El creador coincide con el repo
El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo
- … Aún sin revisar
Sigue en mantenimiento
Todavía no hemos leído este repo en GitHub
- … Aún sin revisar
Tiene licencia
Todavía no hemos leído este repo en GitHub
- – No aplica
El endpoint responde
Este se ejecuta en tu computadora; no hay endpoint en internet
- – No aplica
Inicio de sesión con OAuth
Se ejecuta en tu computadora y usa ajustes locales en su lugar
- … Aún sin revisar
Sin instrucciones ocultas en las descripciones de herramientas
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con otros en Otrosi
- Más estrellas que el 0% de los otros 32505 servidores de esta categoría
- Publicado en el registro más recientemente que el 96% de los otros 32505 servidores de esta categoría
- Revisiones básicas iguales o mejores que el 100% de los otros 32505 servidores de esta categoría
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Preguntas frecuentes
¿Es seguro DNSFilter MCP?
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
¿Qué claves o códigos necesita?
Debes completar: DNSFILTER_API_KEY, DNSFILTER_MCP_HTTP_TOKEN
¿Se ejecuta en mi computadora o en la nube?
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
¿Sigue en mantenimiento?
El repo de GitHub cambió por última vez –, y la última versión (0.1.1) llegó al registro ayer.
¿Qué apps pueden usarlo?
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
¿Qué puedo usar en su lugar?
En la misma categoría: Spec Driven Development, Remote Desktop Commander, topo^alpin
Alternativas
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Remote Desktop Commander
de desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Se ejecuta en la nube★ 211Actualizado ayer
Instalar
topo^alpin
de topoalpin.app
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Se ejecuta en la nubeActualizado hoy
Instalar
README del creador
Abrir el README
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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 agent | How to install the DNSFilter skill |
|---|---|
| Claude Desktop | Run 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 CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste 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.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not 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 Gemini | Gemini 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.mddirectly *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, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/dnsfilter/install.ps1 | iex. Then authenticate per the README and rundnsfilter-cli --helpto 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 | iexmacOS / 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 --versionUpgrade 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 | iexClaude 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 --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/dnsfilter --forceHermes 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 theopenclaw: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 doctorOn 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-tokenOn Windows (PowerShell):
$env:DNSFILTER_API_KEY | dnsfilter-cli auth set-tokendoctor 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 asking | Command |
|---|---|
| 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
Solo se muestra el principio; lee el resto en el repo