📡 MCP Radar

99apps-id/doh-mcp

MCP server for DNS-over-HTTPS: resolve names and fetch URLs through DoH, keyless.

⭐ 6 stars
⑂ 1 forks
Go
momentum ▲ 14.0
created 2026-10-01
on radar since 2026-10-04
star trend 4 → 6 since 2026-10-04
View on GitHub ↗

About doh-mcp

A small Model Context Protocol server for DNS-over-HTTPS. It 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.

An ISP commonly returns NXDOMAIN for a whole domain (this is how DuckDuckGo and some developer sites are blocked in some countries) while the site is fine everywhere else. A browser escapes that by resolving over HTTPS; this server gives an MCP client the same path.

DoH is more than a way around a block. Behind an agent, the same resolver is useful for:

- Privacy and integrity. The query travels over HTTPS, so the local network and the ISP cannot read which names are looked up, and an on-path attacker cannot forge a reply. - Diagnosis. dohcompare separates "the service is down" from "your DNS is broken": when the system resolver fails but DoH answers, the problem is DNS, not the service. It also exposes a captive portal, or a split-horizon view where an internal name resolves differently than it does in public. - Debugging records that are not A/AAAA. dohresolve reads MX, TXT (SPF, DKIM, DMARC), CAA, NS, SOA, SRV and PTR, for email deliverability, domain ownership checks and reverse lookups from a log. - Policy, chosen by resolver. Cloudflare for privacy, Google for the public record, Quad9 to block malware domains, AdGuard to block ads and trackers. Picking the resolver is a policy decision made without changing the app. - Reliability. When the router resolver is slow or down, or a VPN breaks the local lookup path, DoH over port 443 still re

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/99apps-id--doh-mcp.html)

Related MCP servers

okf-memory/okf-agent-memory

Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zer

⭐ 553Go
vshulcz/deja-vu

Your agents already solved this. deja finds it — retroactive search and MCP recall over the session logs your coding agents already wrote. Cross-agent, SSH-portable, one zero-dep binary, fully local.

⭐ 391Go
olucurious/watchtower

Self-hosted error tracking. A drop-in for Sentry and AppSignal SDKs: one Go binary and Postgres, with Slack, Linear, email and an MCP server for coding agents.

⭐ 18Go
KnifeLemon/Droidline

Android automation from code. Test your apps on real phones, script the tasks you repeat, run a shelf of phones, or let an AI agent use one, from Python, Node.js, the CLI, HTTP or Appium clients. No A

⭐ 18Go
enowdev/succubus

Cross-agent coordination for AI coding agents. One daemon, one database — so multiple agents in one repo can see each other's plan, tasks, and file claims.

⭐ 15Go
AsWali/CallBoard

A shared to-do list for you and your AI coding agents

⭐ 15Go

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.