Other · Remote MCP server
DialMCP
Let AI agents place real phone calls from your verified number, with transcripts and recordings.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.dialmcp/dialmcp- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-27
- Updated
- 2026-07-27
- Publisher
- com.dialmcp
- Namespace
- Namespace verified by the MCP Registry via the domain dialmcp.com · how
- Website
- dialmcp.com
- Repository
- github.com/SkillfulAgents/dialmcp-connector
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.dialmcp.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | dialmcp-connector | 0.1.0 | stdio |
How to connect DialMCP
DialMCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.dialmcp.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: dialmcp-connector version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y dialmcp-connector@0.1.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"dialmcp": {
"command": "npx",
"args": [
"-y",
"dialmcp-connector@0.1.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Diagrams MCP ServerLocal-first MCP server for PlantUML and Mermaid diagrams with drift detection. | Local · stdio |
| DiagramZuLet Claude, Cursor, or ChatGPT author Mermaid diagrams your team can read and share. | Remote · HTTPLive check: sign-in required |
| DialCommunication stack for AI agents: SMS, AI voice calls, phone numbers, and account events. | Remote · HTTPLive check: sign-in required |
| DialfetchGive your AI agent a phone: place calls, navigate IVRs, wait on hold, get structured answers. | Remote · HTTPLive check: ✗ no handshake |
| DialNexaCreate and manage DialNexa AI voice agents, campaigns, calls, phone numbers, workflows, and more. | Remote · HTTPLive check: sign-in required |
| Diamond MCPSourced diamond and gemology tools for AI assistants, with 90 encyclopedia entries. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Diaspora MCPMCP server for diaspora services coordination between East Africa and abroad. | Local · stdio |
| DiavlosSigned messages between AI agents. Dangerous actions wait for a human-signed approval. | Local · stdio |