lgbt.dns/dns-lgbt
dns.lgbt
Is the dns.lgbt MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Manage the DNS records, DNSSEC and nameserver delegation of your dns.lgbt domains.
needs auth probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"type":"https://dns.lgbt/docs/api#errors-unauthorized","title":"Missing or invalid token","status":401,"detai- Endpoint
- https://dns.lgbt/api/mcp (streamable-http)
- Host
- dns.lgbt
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://dns.lgbt/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server dns.lgbt, PKCE S256, grants authorization_code, refresh_token.
Scopes domains:read delegation:read records:read records:write dnssec:read dnssec:write.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://dns.lgbt/docs/mcp
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention delegation or nameserver.
- Helixar Security ai.helixar/mcp · needs auth
- Tanjiren MCP Server app.tanjiren/tanjiren-mcp · no DNS
- GateCore Marketplace com.gatecoreai/marketplace · alive
- Proof Holdings holdings.proof/mcp-server · alive
- Agent-Native Dispatch io.github.BuilderIO/agent-native-dispatch · needs auth
- io.github.CSOAI-ORG/agent-delegation-mcp · not found
- Agent Passport System — Cryptographic Identity for AI Agents io.github.agent-passport-system/agent-passport-mcp · needs auth
- io.github.craigmbrown/blindoracle · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.