What problem does it solve? Third-party AI agents cannot find or connect to an MCP server you operate unless it is listed in registries, exposes a working OAuth discovery chain, serves a capability manifest, and publishes DNS-AID records. This Skill walks through publishing and verifying all four surfaces so agents can resolve a domain to a working MCP session. ## Core Features & Use Cases - Registry Listing: Claim a reverse-DNS namespace, prove domain ownership via DNS TXT, publish a server.json to registry.modelcontextprotocol.io, and mirror to mcp.so, Smithery, Glama, and PulseMCP. - OAuth Discovery Chain Repair: Diagnose and fix the 401 + WWW-Authenticate to /.well-known/oauth-protected-resource (RFC 9728) to /.well-known/oauth-authorization-server (RFC 8414) chain, the most common cause of remote MCP connection failures. - Capability Manifest & DNS-AID: Serve /.well-known/agent/mcp.json and publish SVCB, TXT, _index._agents, and TLSA/DANE records under DNSSEC, verified with dns-aid verify. - Use Case: Your team ships an MCP endpoint at app.example.com/mcp but Claude Code clients report "cannot connect." Use this Skill to test the three OAuth hops with curl, fix the missing resource_metadata header, list the server in the official registry, and confirm a real client completes auth and lists tools. ## Quick Start Ask the agent to make your MCP server at your domain discoverable by listing it in the official MCP registry, fixing the OAuth discovery chain, serving a capability manifest, and publishing DNS-AID records, then verify end to end with a real client connection.
