DialMCP — remote phone-call MCP server onboarding

Interested in onboarding **DialMCP** to the Azure MCP Center discovery page.

🔧 **MCP Type:** remote
📛 **MCP Server Name:** DialMCP
📄 **Brief Description:** Hosted remote MCP server that lets AI agents place real phone calls from the user's own SMS-verified number. Returns transcript, recording, and a structured outcome. Streamable HTTP + OAuth 2.1. US & Canada only, 8:00–21:00 local. Free during pilot.
🔐 **OAuth 2.1 Support:** Yes — Streamable HTTP with OAuth 2.1 (phone-number sign-in via SMS; no API keys). Dynamic client registration (RFC 7591).
🐙 **GitHub Repository:** https://github.com/SkillfulAgents/dialmcp-connector
🌐 **Website / endpoint:** https://dialmcp.com · MCP: https://mcp.dialmcp.com/mcp
🎨 **Icon URL:** https://raw.githubusercontent.com/SkillfulAgents/dialmcp-connector/main/assets/logo.png
📂 **Category:** Business Services (also fits Developer Tools / Productivity)
📦 **Official MCP Registry:** `com.dialmcp/dialmcp` v0.1.0
📧 **Contact:** support@dialmcp.com

Happy to complete any partner paperwork needed for onboarding.

Start by locating the Azure MCP Center discovery-page data and its onboarding checks; use the supplied DialMCP details, registry identifier, endpoint, icon URL, and repository to validate the listing. Done means the remote server is represented on the discovery page with the required metadata and passes the repository's checks.

Written by the indexing model from the issue text.