whatsappwebhookshealth-checksmessaging
Checks Wapiworld sender and webhook health, then sends one explicitly confirmed WhatsApp text.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON â–¾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for wapiworld, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Overview
Use cases
Check Wapiworld sender health before messaging
Inspect webhook health during troubleshooting
Send one confirmed WhatsApp text
Add a confirmation-gated message step to an agent workflow
Key features
Sender health inspection
Webhook health inspection
Explicitly confirmed WhatsApp text sending
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Wapiworld.
Extracted Tool Capabilities
Sender health inspection
Webhook health inspection
Explicitly confirmed WhatsApp text sending
How Wapiworld works
What the wapiworld MCP server does
The wapiworld MCP server exposes a focused set of operations for Wapiworld messaging infrastructure. It can inspect the health of a sender and the health of webhooks, giving an agent a way to check whether those parts of the system are functioning. It can also send a WhatsApp text, but the action is explicitly confirmed rather than treated as an unrestricted send operation.
This makes the server relevant to workflows that need a health check before messaging or that require a deliberate confirmation step before a WhatsApp message is sent. The available description does not identify additional messaging channels, contact-management functions, message-history queries, or administrative operations.
Tools and capabilities
The documented capabilities are:
- Inspect Wapiworld sender health.
- Inspect Wapiworld webhook health.
- Send one WhatsApp text after explicit confirmation.
The material does not provide formal tool names, argument schemas, response formats, or details about how confirmation is represented. Developers should consult the Wapiworld developer page for those implementation details before building an automation around the server.
Setup and configuration
The supplied material does not include installation commands, transport details, configuration examples, authentication requirements, environment variables, or client-specific setup instructions. The source is Wapiworld’s developer page at https://app.wapiworld.com/developers#mcp.
Because the setup contract is not available here, do not assume a package name, command, credential variable, or connection mode. Use the developer documentation to determine how an MCP client should launch or connect to the wapiworld MCP server and how Wapiworld access is authorized.
Limitations and notes
The wapiworld MCP server is described as a narrow interface rather than a general WhatsApp automation layer. Its documented sending capability covers one explicitly confirmed WhatsApp text. The available information does not establish support for bulk delivery, scheduled messages, media, templates, replies, conversation retrieval, or recipient lookup.
Health inspection is specified for the Wapiworld sender and webhooks. No other components or external services are identified. Client compatibility is also not stated in the supplied material, so verify support in the target MCP client and follow Wapiworld’s current developer instructions.
The explicit-confirmation requirement matters for unattended workflows: an agent should not be assumed to have permission to send merely because it can call the server. Confirm the action according to the server’s documented protocol before relying on it in production.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Wapiworld
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/wapiworld)HTML Embed
<a href="https://allmcps.com/mcp/wapiworld"><img src="https://allmcps.com/api/badge/wapiworld?style=directory" alt="Wapiworld on AllMCPs" /></a>Technical Specs & Signals
CategoryCommunication
5/5 checks healthy over the last 42d
39Quality signal: Fair · 39/100How this signal is calculated ▾
Server availability25/25
Verified ownership0/20
Documentation & tools11/30
Adoption & activity3/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.