--- title: "Turbo Notify MCP server | Agent MCP Directory" description: "Turbo Notify has an open MCP server with 36 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/turbonotify-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Turbo Notify MCP server | Agent MCP Directory > Turbo Notify has an open MCP server with 36 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/turbonotify-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Turbo Notify: MCP server, CLI and agent surfaces Yes: Turbo Notify runs a public MCP server at mcp.turbonotify.com that listed 36 tools to a client with no credentials on 4 November 2026. Examples: send\_text, send\_media, send\_location. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool. ## Fact sheet | Company | Turbo Notify (registry title: Turbo Notify: WhatsApp for AI agents) | | --- | --- | | Domain | turbonotify.com | | Category | Communication & Support (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | none: Ora returned no cached score for turbonotify.com when asked on 5 November 2026 | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.turbonotify.com | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | turbo-notify 0.1.0 | | Capabilities | experimental, prompts, resources, tools | | Tools | 36 | | Resources | 0 | | Prompts | 0 | | Connected | 4 November 2026, 20:04 UTC | | Handshake time | 3,674 ms over 1 attempt | ### Tools listed 36 tools - send\_text - send\_media - send\_location - send\_contact\_card - send\_calendar\_event - send\_cta\_button - reply\_to\_message - edit\_text\_message - edit\_media\_caption - edit\_calendar\_event - cancel\_calendar\_event - delete\_message - react\_to\_message - send\_typing\_indicator - mark\_as\_read - list\_messages - get\_message - get\_message\_status - get\_message\_receipts - get\_message\_reactions - get\_message\_responses - get\_message\_quota - list\_contacts - get\_contact - get\_contact\_profile\_picture - refresh\_contact - get\_contact\_quota - list\_groups - get\_group - get\_group\_picture - list\_numbers - get\_number - connect\_number - disconnect\_number - get\_usage - list\_events ### Connector log 2 connections on 4 November 2026, read-only methods only - 20:00:05Z https://mcp.turbonotify.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3619 ms - 20:05:00Z https://mcp.turbonotify.com sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 3674 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.turbonotify.com` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Turbo Notify. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | No OpenAPI file at the root paths checked. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.turbonotify/whatsapp | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/turbonotify-com/index.md) ## Sources - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=turbonotify), read 4 November 2026 - [Turbo Notify website](https://turbonotify.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026