Agentreg – DNS for AI agents (self-hosted, single Go binary) Agentreg, a self-hosted registry for AI agents, lets agents discover each other by capability with built-in health checks and trust, running as a single Go binary with no cloud dependency. The open-source tool, created by developer mkk2026, addresses the gap in agent-to-agent discovery and health monitoring as the number of AI agents grows. DNS for AI agents. A self-hosted registry that lets your agents find each other by capability — with health and trust built in. Everyone is building AI agents. Nobody is building the layer that lets agents exist alongside each other — discovery, health, trust. The moment you run more than a couple of MCP servers, you're hardcoding endpoints in config files, finding out an agent is down only when something breaks, and trusting every endpoint blindly. MCP gave agents a common language. agentreg gives them a place to find each other. Consul tells youwherea service is. agentreg tells youwhatan agent can do,whetherit's healthy, and soon how much to trust it. One Go binary. Self-hosted. No cloud, no account, no cluster. Runs on your laptop at 3 agents and scales with you. Homebrew macOS / Linux brew install mkk2026/tap/agentreg or download a binary from the latest release https://github.com/mkk2026/agentreg/releases or from source Go 1.26+ go install github.com/mkk2026/agentreg@latest 1. run the registry agentctl serve & 2. register your agents agentctl register search-agent -c search -e http://localhost:3000 agentctl register db-agent -c db-read -e http://localhost:3001 agentctl register product-api -c api,email -e http://localhost:3002 3. see everything, with live health agentctl list 4. discover by capability — use this in your agent's startup instead of a hardcoded URL agentctl find search agentctl find search --format json agentctl list : NAME CAPABILITIES STATUS SOURCE LAST HEARTBEAT ENDPOINT db-agent db-read unhealthy local just now http://localhost:3001 product-api api,email healthy local just now http://localhost:3002 search-agent search healthy local just now http://localhost:3000 The daemon health-checks every registered agent on an interval, so a down agent shows up as unhealthy before it breaks something downstream. That's the difference between reading a status table and debugging a production incident backwards. Capability-first discovery. Ask for what you need find search , not where it lives. Endpoints move; capabilities don't. Health built in. Every agent is probed on a heartbeat. No separate monitoring stack to wire up. Self-hosted, zero cloud. One static binary. Your registry, your data, your network. Nothing leaves your machine. Delightful at 3 agents, load-bearing at 30. Cheap enough to adopt before you need it, so it's already there when you do. Built to grow into trust. The verification layer is pluggable from day one see Roadmap roadmap . agentctl CLI ──HTTP──▶ agentreg daemon │ ├── Store in-memory + atomic JSON persistence └── Verifier health probe, on a heartbeat loop Two design seams make the roadmap additive instead of a rewrite: - on every record Source field local today; peer: