doh-mcp
MCP server for DNS-over-HTTPS (DoH). Resolves names and fetches URLs through a DoH resolver so an agent keeps working behind an ISP DNS block or a poisoned resolver. No API key. A single Go binary, CGO-free.
License: Apache-2.0
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
MCP server for DNS-over-HTTPS (DoH). Resolves names and fetches URLs through a DoH resolver so an agent keeps working behind an ISP DNS block or a poisoned resolver. No API key. A single Go binary, CGO-free.
License: Apache-2.0
MCP server for DNS-over-HTTPS: resolve names and fetch URLs through DoH, keyless.
git clone https://github.com/99apps-id/doh-mcp.git
cd doh-mcp
go build -o doh-mcp .
Pre-built binaries are available for Linux, macOS, and Windows on the GitHub Releases page.
The server accepts a -resolver flag:
doh-mcp -resolver cloudflare
# or
doh-mcp -resolver google
# or
doh-mcp -resolver quad9
# or
doh-mcp -resolver adguard
# or
doh-mcp -resolver https://your-doh-server/dns-query
Available built-in resolver aliases:
cloudflare (default)googlequad9adguardOr pass any DoH endpoint URL that answers the JSON API
(Accept: application/dns-json).
This MCP server is designed to work with any MCP client, including:
~/.termigo/mcp.json~/.termixgo/config.json or mcpServers sectionAll MCP clients that support stdio servers can use this format:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
Replace doh-mcp with the full path to the binary on your system:
/usr/local/bin/doh-mcp or $HOME/.local/bin/doh-mcp/usr/local/bin/doh-mcp or $HOME/.local/bin/doh-mcpC:\\Users\\<USER>\\bin\\doh-mcp.exe or C:\\Program Files\\doh-mcp\\doh-mcp.exemcpServers in ~/.termigo/mcp.json:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
Tools appear as mcp_doh__doh_resolve, mcp_doh__doh_compare, mcp_doh__doh_fetch.
mcpServers in ~/.termixgo/config.json:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
Or use the built-in MCP commands:
termixgo mcp add doh --command doh-mcp --arg -resolver --arg cloudflare
termixgo mcp list
VS Code uses mcpServers in .vscode/mcp.json (workspace) or user settings:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
Claude Desktop uses mcpServers in claude_desktop_config.json:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
Claude Code reads from ~/.claude.json:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
Cursor uses mcpServers in ~/.cursor/settings.json or workspace .cursor/settings.json:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
OpenCode uses .opencode/mcp.json:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
openclaw mcp add doh --command doh-mcp --arg -resolver --arg cloudflare
openclaw mcp doctor doh --probe
Hermes uses mcp_servers in ~/.hermes/config.yaml:
mcp_servers:
doh:
command: doh-mcp
args:
- "-resolver"
- "cloudflare"
9router uses the MCP Marketplace UI or managedMcpServers in the workspace config:
{
"managedMcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
Or use the Dashboard UI: Plugins -> Add Custom MCP -> paste the command above.
Codex CLI reads from OPENAI_MCP_SERVERS environment variable:
export OPENAI_MCP_SERVERS='{"doh":{"command":"doh-mcp","args":["-resolver","cloudflare"]}}'
Or in .codex/config.json:
{
"mcpServers": {
"doh": {
"command": "doh-mcp",
"args": ["-resolver", "cloudflare"]
}
}
}
docker build -t doh-mcp .
# point the client at: docker run -i --rm doh-mcp
Dockerfile:
FROM golang:1.26-alpine AS build
WORKDIR /app
COPY . .
RUN go build -o doh-mcp .
FROM alpine:latest
RUN apk add --no-cache ca-certificates
COPY --from=build /app/doh-mcp /usr/local/bin/doh-mcp
ENTRYPOINT ["doh-mcp"]
// doh_resolve
{ "name": "example.com", "type": "A", "resolver": "cloudflare" }
// doh_compare
{ "name": "duckduckgo.com" }
// doh_fetch
{ "url": "https://example.com", "max_chars": 20000 }
doh_compare is the diagnostic: on a blocked network it reports
the system resolver failed but DoH resolved the name; DNS is blocked or poisoned.
doh_fetch refuses cloud metadata (169.254.169.254,
metadata.google.internal) and link-local addresses, re-checks on every
redirect, and pins the connection to the address it resolved, which also
defeats DNS rebinding. Loopback and private addresses are allowed, so a local
documentation server can be read.
gofmt -s -l .
go vet ./...
go test ./...
Apache-2.0. See LICENSE.
MCP server for DNS-over-HTTPS: resolve names and fetch URLs through DoH, keyless.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Doh roda localmente via stdio.
Última verificação: 2026-10-26. MCP server for DNS-over-HTTPS: resolve names and fetch URLs through DoH, keyless.