DNS-based Agent Identification and Discovery - MCP server for publishing and discovering agents via DNS using the DNS-AID protocol
DNS-AID MCP server demonstrates solid tool design with complete schemas, clear descriptions, and proper risk classification. All 6 tools have descriptions (avg 120 chars), input schemas with typed parameters, and enum constraints where appropriate. Tool names follow verb_noun pattern (publish_agent, discover_agents, verify_agent, list_agents, delete_agent, get_server_info). However, output schemas are not documented in the provided source, parameter descriptions lack format/constraint details (e.g., domain format, port range), and error handling guidance is absent. No evidence of idempotency markers or confirmation patterns for destructive operations (delete_agent). Composition is clean, each tool has single responsibility and clear chaining via domain/name/protocol parameters.
Delete an agent from DNS. Removes SVCB and TXT records for the agent.
Discover agents published at a domain using DNS-AID protocol. Returns list of agents with their endpoints and capabilities.
Get information about the DNS-AID MCP server, including version and capabilities.
List all agents published at a domain by reading the agent index record.
Publish an agent to DNS using DNS-AID protocol. Creates SVCB and TXT records that allow other agents to discover this agent.
Verify that an agent's DNS records are properly configured. Checks SVCB and TXT records for validity.
Output schemas not documented. LLMs cannot plan downstream calls or extract required fields (e.g., agent endpoint, capabilities returned by discover_agents). Agents may fail to chain tools or misinterpret responses.
Parameter descriptions lack format constraints. 'domain' parameter has no format spec (FQDN? wildcard allowed?). 'port' has no range (1-65535?). 'ttl' has no bounds. LLMs may pass invalid values.
Destructive operation (delete_agent) lacks confirmation or dry-run pattern. No evidence of idempotency markers or recovery guidance. Agents may accidentally delete agents without safeguards.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2026-07-28+ | v2 |
No error handling guidance in tool descriptions. What happens if domain is invalid? If backend is unreachable? If agent already exists? LLMs have no recovery path.
discover_agents and list_agents lack pagination parameters (limit, offset, next_cursor). Large agent lists could exhaust context window. No indication of result limits.