Adding full form of CIMD with link to specification

Author: KarimTantawy5

auth4genai/mcp/guides/registering-your-mcp-client-application.mdx

@@ -8,7 +8,7 @@ Before your MCP client application can interact with a protected MCP server, it
 
 You can register your client in two ways: statically or dynamically. For most scenarios, especially in production, we strongly recommend static client registration for its superior security and control.
 
-<Note>In the upcoming authorization specification from MCP, CIMD will be introduced as the recommended method for client registration. Support for this new approach in Auth0 is planned and will be available soon.</Note>
+<Note>In the upcoming authorization specification from MCP, [Client ID Metadata Documents (CIMD)](https://modelcontextprotocol.io/specification/draft/basic/authorization#client-id-metadata-documents) will be introduced as the recommended method for client registration. Support for this new approach in Auth0 is planned and will be available soon.</Note>
 
 ## Static client registration (recommended for production)