mcpbeat Sign in

SMS and WhatsApp Messaging MCP Server

by hatchloop Your server? Claim it
answering

SMS and WhatsApp Messaging is answering right now. Last checked 5 min ago. It exposes 10 tools. Last commit 22 Sep 2026.

Send WhatsApp, SMS, email or voice to a business with the compliance gate enforced.

Uptime history 54 days of history · worst day 35%
54 days agonow
100.0%
Uptime 24h
91 of 91 checks
10
Tools
read from the server
648 ms
Response time
average over 24h
0
Stars
last commit 22 Sep 2026

What changed 51

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 September 2026. No other catalogue keeps this.

9 Oct a tool changed version
5 Oct 2 tool descriptions were rewritten send_message, send_transactional_confirmation
5 Oct 2 tools changed the parameters they ask for check_compliance, send_message
5 Oct a tool changed version2 times that day
3 Oct 2 tool descriptions were rewritten find_business, verify_business
3 Oct a tool changed the parameters it asks for find_business
1 Oct 2 tool descriptions were rewritten3 times that day send_message, send_transactional_confirmation
30 Sep a tool description was rewritten find_business
30 Sep a tool changed the parameters it asks for find_business
27 Sep a tool description was rewritten send_message
and 37 more, back to 2 September 2026

What the code does

We read the source, 4 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command compliance/jev_advisory.py:354 
        proc = subprocess.run(
Dumps the whole environment compliance/jev_advisory.py:336 
    env = dict(os.environ)

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add sms-whatsapp-messaging --transport http https://hatchloop.dev/mcp/sms-whatsapp-messaging
Settings → Connectors → Add custom connector, then paste this address
https://hatchloop.dev/mcp/sms-whatsapp-messaging
~/.codex/config.toml
[mcp_servers.sms-whatsapp-messaging]
url = "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
.cursor/mcp.json
{
  "mcpServers": {
    "sms-whatsapp-messaging": {
      "url": "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "sms-whatsapp-messaging": {
      "type": "http",
      "url": "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

send
send_message
Send a message on behalf of an agent's user or an SMB across WhatsApp (free during launch), SMS, email, or voice, sent immediately, no scheduling. Every send passes a non-bypassable gate: TCPA, GDPR, CASL where modeled, else the service's own opt-in default (the Gulf included). Marketing on SMS, voice, WhatsApp and non-US email without recorded opt-in is rejected (compliance_violation receipt). US marketing email follows CAN-SPAM opt-out rules. [from $0.02/call, variable, not charged while no payment rail is on] [async→get_outcome] [Not available on this deployment: SMS, Voice.]
send_transactional_confirmation
Idempotent transactional messages: OTPs, booking confirmations, payment receipts, cancellation notices. Falls back across configured channels; an unconfigured channel fails honestly rather than reporting a delivery that did not happen. [$0.02/per_call, not charged while no payment rail is on] [async→get_outcome] [Not available on this deployment: SMS.]
business
find_business
Find real businesses near a place, sorted by distance (nearest of those examined; see result.search). Data: OpenStreetMap (ODbL, (c) OSM contributors); phone, website, hours only when mapped. Coverage varies; community-mapped, NOT verified by us; source=openstreetmap rows cannot be booked. Answers within about 5 s: status partial (search_in_progress) means repeat the call. If OSM is down: retriable 'temporarily unavailable', never invented rows. [free, no key] [beta]
compliance
check_compliance
Free, instant pre-flight for the compliance gate: runs the SAME TCPA/GDPR/CASL/CAN-SPAM/10DLC checks as send_message and call_business, in preview mode -- nothing is sent, nothing changes. Tells you whether a send would be permitted before you pay, and if not, names the exact rule and how to fix it. De-risks a paid send the way check_booking_link de-risks a paid booking. [free, no key]
conversation
get_conversation
Read a two-way conversation thread you started: its state, every message exchanged, and how many replies the business has sent. [free, requires key]
outcome
get_outcome
Retrieve the final OutcomeReceipt for a completed operation. [free, no key]
preview
preview_cost
Return an expected cost estimate, latency estimate, and success-probability estimate for a proposed call before execution. Returns the exact price when it is fixed, and a min/max range when the cost depends on channel or outcome. It does not promise an accuracy percentage - check cost_range. [free, no key]
self
self_test
Service health probe: runs 6 internal checks and reports how many passed. Confirms the server is up and responding - it does NOT probe each tool individually. Use to verify connectivity before production use. [free, no key]
status
get_status
Query the current state of any in-flight async operation by operation_id. [free, no key]
verify
verify_business
Look up what we know about a business in our supply network: contact channels, capabilities, last verification. A DIRECTORY LOOKUP - it does not contact the business. Supply-network ids only, not osm:... ids. [free, no key] [limited]

Endpoints

URLTransportStateLatencyChecked
https://hatchloop.dev/mcp/sms-whatsapp-messaging streamable-http answering 609 ms 5 min ago

Alternatives to SMS and WhatsApp Messaging

same job, measured the same way
Agentos
by imran-siddique

Build and manage policy-compliant AI agents with safety enforcement and compliance checking

27 installs/wk local only
Instilus compliance and business decision tools
by instilus

GPSR compliance check and small-business valuation estimate, from Instilus.

8 tools answering
Compliance Intelligence
by theartofservice

What one compliance standard already evidences of another, with the reasoning and the rejections.

33 tools answering
Africa Compliance Data
by africacompliancedata

Public holidays, business days, VAT, withholding tax and tax-ID checks for 54 African countries

answering
Engineering
by novtriq

27 engineering compliance and calculation tools for the built environment (UK, EU, UAE).

27 tools answering
Regulatory Radar
by jdhart81

California, US, and global climate compliance scans with source-linked deadlines.

5 tools answering
MCP E-Invoicing Core
by cmendezs

Base package for e-invoicing MCP servers. Compliance logic and signing keys stay with you.

770 installs/wk local only
Sentrik
by maxgerhardson

Governance runtime for AI-generated code. Enforce compliance and security standards.

12 installs/wk local only

SMS and WhatsApp Messaging — questions

Answers built from our own checks of this server.

What can SMS and WhatsApp Messaging do?
It exposes 10 tools, read directly from the server on our last check. Among them: check_compliance, find_business, get_conversation, get_outcome, get_status, preview_cost and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is SMS and WhatsApp Messaging working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 648 ms. The bar chart above shows every period we have measured.
How do I connect SMS and WhatsApp Messaging?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SMS and WhatsApp Messaging need an API key?
No. SMS and WhatsApp Messaging completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SMS and WhatsApp Messaging?
It answers our handshake in 648 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is SMS and WhatsApp Messaging open source?
The code is open source: it is published under the MIT licence, written in Python, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at hatchloop.dev, which runs on its operator's own terms.