Dns Aid
Publish and discover AI agents on your domain using DNS SVCB records so clients find the right MCP endpoint without hard-coded URLs.
Overview
dns-aid is a MCP server for the Launch phase that discovers and publishes AI agents using DNS SVCB records (RFC 9460) with optional multi-vendor DNS backends.
What is this MCP server?
- Discover and publish AI agents via DNS SVCB records (RFC 9460)
- Optional DNS_AID_BACKEND: route53, cloudflare, infoblox, nios, ns1, ddns, or mock
- Discovery-only operations work without configuring a write backend
- PyPI package dns-aid v0.17.3 with stdio MCP transport
- RFC 9460 SVCB-based discovery
- 7 named DNS_AID_BACKEND options including mock
- Package version 0.17.3
Community signal: 45 GitHub stars.
What problem does it solve?
Builders lack a standard way to advertise which host and port serve an agent, so clients rely on brittle hard-coded URLs instead of DNS-native discovery.
Who is it for?
Solo builders and small teams launching agent services on custom domains with Route53, Cloudflare, or enterprise DNS already in play.
Skip if: Products with no DNS control, teams that only need a single static MCP URL in config, or builders avoiding any DNS record management.
What do I get? / Deliverables
You can publish and resolve agent endpoints through SVCB records so compatible clients discover your MCP service from your domain.
- SVCB records that advertise agent endpoints
- DNS-backed discover/publish workflow via MCP
- Backend-selected updates for supported DNS providers
Recommended MCP Servers
Journey fit
DNS-based agent discovery is how you make agents findable and routable after the product exists—classic launch and distribution plumbing. SVCB publishing and lookup is distribution infrastructure (how agents are advertised on the internet), not app UI or unit testing.
How it compares
DNS discovery MCP for agent publishing, not a web-scraping research or finance routing tool.
Common Questions / FAQ
Who is dns-aid for?
Developers and operators who publish AI or MCP agents on their own zones and want RFC 9460 SVCB-based discovery instead of manual URL lists.
When should I use dns-aid?
Use it at Launch when you are distributing agent endpoints and need discover/publish workflows against DNS, optionally tied to Route53, Cloudflare, Infoblox, NS1, or mock backends.
How do I add dns-aid to my agent?
Install the PyPI dns-aid package, add it as a stdio MCP server in your agent, and set DNS_AID_BACKEND only when you need write access to a supported DNS provider.