com.turbonotify/turbo-notify
Turbo Notify: WhatsApp for AI agents
Is the Turbo Notify MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-13.
Send, receive, edit and react to WhatsApp messages from your own number. OAuth or API key sign-in.
alive probed 2026-11-15 · unchanged since 2026-11-13 · HTTP 200
- Endpoint
- https://mcp.turbonotify.com (streamable-http)
- Host
- mcp.turbonotify.com
- Protocol
- 2025-11-25
- Reports itself as
- turbo-notify 1.5.13
- Capabilities
- experimental, prompts, resources, tools
- Instructions
- 2 226 characters
- Of a 1M window
- 3.1 % of a 1M context window
- Count
- 31k tokens in Claude Opus 5.5, exact, measured 2026-11-07. With the Claude Code prefix mcp__…__ on each tool name: 32k. The o200k_base estimate is 20k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/turbo-notify/agent-skills
- Website
- https://docs.turbonotify.com/en/agents/mcp-server/
- Registry
- active, updated 2026-11-13 · registry entry
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.58×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| send_calendar_event | 2 415 | 1 527 | 8 % |
| list_events | 2 192 | 1 386 | 7 % |
| cancel_calendar_event | 1 985 | 1 255 | 6 % |
| edit_calendar_event | 1 955 | 1 236 | 6 % |
| send_media | 1 696 | 1 072 | 5 % |
Compare this server with others, or with the servers that share its tool set.
Same tool set as 1 other server
These registry entries have the same tool names and the same schema sizes.
- com.turbonotify/whatsapp mcp.turbonotify.com
More servers
Other registry entries on mcp.turbonotify.com.
- Turbo Notify: WhatsApp for AI agents com.turbonotify/whatsapp · alive
Servers that mention notify.
- AgentPing io.github.Noriget/agentping · needs auth
- notifyd io.github.rmzlb/notifyd · needs your URL
- Open Notify io.github.pipeworx-io/open-notify · alive
- Data Breach Notification Deadlines io.github.Nero-Engine/breach-notification-deadlines · alive
- Notifyre MCP by usefulapi io.usefulapi/notifyre · timeout
- NOTIFY io.github.n0t1fy/notify-sms-georgia · alive
- io.github.sathergate/notifykit · crashed on start
- Notify MCP Server io.github.aahl/mcp-notify · needs env
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Its 5 most expensive tools are 33 % of the cost. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.