Agent MCP Directory

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

CompanyTurbo Notify (registry title: Turbo Notify: WhatsApp for AI agents)
Domainturbonotify.com
CategoryCommunication & Support (assigned by this directory from the registry description)
MCP serverVerified (No authentication)
Ora scorenone: Ora returned no cached score for turbonotify.com when asked on 5 November 2026
Company found throughthe GitHub MCP Registry; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://mcp.turbonotify.com
How it was foundlisted in the GitHub MCP Registry; the official MCP Registry
Transportstreamable-http
HTTP status200
Protocol version2025-11-25
Serverturbo-notify 0.1.0
Capabilitiesexperimental, prompts, resources, tools
Tools36
Resources0
Prompts0
Connected4 November 2026, 20:04 UTC
Handshake time3,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 typeNo 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 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.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot 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.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: com.turbonotify/whatsapp
GitHub MCP RegistryYes
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.