# SMS and WhatsApp Messaging (remote · hatchloop.dev)

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

- Trust score: 74/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `hatchloop.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/dev-hatchloop-sms-whatsapp-messaging/mcp-sms-whatsapp-messaging.md), [page](https://verifymcp.io/servers/dev-hatchloop-sms-whatsapp-messaging/mcp-sms-whatsapp-messaging)

## Channel facts

- Endpoint: `https://hatchloop.dev/mcp/sms-whatsapp-messaging`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.13`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_message).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1554 tokens (~103/item across 15 items; 10 tools + 5 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SMS and WhatsApp Messaging MCP server?

SMS and WhatsApp Messaging is a hosted endpoint at https://hatchloop.dev/mcp/sms-whatsapp-messaging, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-hatchloop-sms-whatsapp-messaging 'https://hatchloop.dev/mcp/sms-whatsapp-messaging'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-hatchloop-sms-whatsapp-messaging": {
      "url": "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-hatchloop-sms-whatsapp-messaging": {
      "type": "http",
      "url": "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-hatchloop-sms-whatsapp-messaging]
url = "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-hatchloop-sms-whatsapp-messaging": {
      "type": "remote",
      "url": "https://hatchloop.dev/mcp/sms-whatsapp-messaging",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-hatchloop-sms-whatsapp-messaging --url 'https://hatchloop.dev/mcp/sms-whatsapp-messaging' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-hatchloop-sms-whatsapp-messaging:
    url: "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-hatchloop-sms-whatsapp-messaging": {
      "Transport": "http",
      "Url": "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-hatchloop-sms-whatsapp-messaging -t streamable-http -u 'https://hatchloop.dev/mcp/sms-whatsapp-messaging'
```

### Other

```json
{
  "mcpServers": {
    "dev-hatchloop-sms-whatsapp-messaging": {
      "type": "http",
      "url": "https://hatchloop.dev/mcp/sms-whatsapp-messaging"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 69, +2)

- [security] Tool “check_compliance” rewrote its description, which is the text the model reads
- [security] Tool “find_business” rewrote its description, which is the text the model reads
- [security] Tool “get_conversation” rewrote its description, which is the text the model reads
- [security] Tool “get_outcome” rewrote its description, which is the text the model reads
- [security] Tool “get_status” rewrote its description, which is the text the model reads
- [security] Tool “preview_cost” rewrote its description, which is the text the model reads
- [security] Tool “self_test” rewrote its description, which is the text the model reads
- [security] Tool “send_message” rewrote its description, which is the text the model reads
- [security] Tool “send_transactional_confirmation” rewrote its description, which is the text the model reads
- [security] Tool “verify_business” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: fail → pass
- [cosmetic] “check_compliance” reworded the description of “channel”
- [cosmetic] “check_compliance” reworded the description of “content”
- [cosmetic] “check_compliance” reworded the description of “country_code”
- [cosmetic] “check_compliance” reworded the description of “message_type”
- [cosmetic] “find_business” reworded the description of “availability_window”
- [cosmetic] “find_business” reworded the description of “capability”
- [cosmetic] “send_message” reworded the description of “business_id”
- [cosmetic] “send_message” reworded the description of “message_type”
- [cosmetic] “send_message” reworded the description of “on_behalf_of”
- [cosmetic] “send_message” reworded the description of “send_at_iso”
- [cosmetic] “send_transactional_confirmation” reworded the description of “data”

### 2026-09-10 (score 67, −2)

- [security regression] HSTS header: pass → fail

### 2026-09-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1.

## MCP tools (10)

### `find_business` (~157 tokens)

Given criteria (vertical, location, capability, price band, availability window), return ranked candidate businesses from our supply network. THE NETWORK IS SMALL AND STILL MOSTLY SAMPLE DATA: entries that are not real are named [DEMO] and flagged is_demo - check that field before acting on a result. [free, no key]

Input parameters:

- `availability_window` (object): Accepted but NOT APPLIED - it does not narrow results. We do not hold live…
- `capability` (string): Specific service capability required, e.g. 'haircut', 'plumbing',…
- `location` (object, required)
- `max_results` (integer)
- `price_band` (object)
- `vertical` (string, required): Service vertical to search within

### `verify_business` (~72 tokens)

Look up what we know about a business in our supply network: its contact channels, capabilities, and when the record was last verified. This is a DIRECTORY LOOKUP - it does not contact the business. [free, no key]

Input parameters:

- `capability_to_verify` (string)
- `smb_id` (string, required)

### `send_message` (~293 tokens)

Send a message on behalf of an agent's user or an SMB across WhatsApp (free during launch), SMS, email, or voice. Five message types: transactional, reminder, follow_up, notification, marketing. Every send routes through a non-bypassable compliance gate (TCPA, GDPR, CASL, PDPL across 26 jurisdictions) that enforces opt-in consent for marketing/promotional content — marketing without recorded consent is rejected at runtime with a structured… [from $0.02/call, variable] [async→get_outcome]

Input parameters:

- `business_id` (string): Optional stable id for the recipient business. Enables global demand shaping…
- `content` (object, required)
- `idempotency_key` (string): Optional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged.
- `message_type` (string, required): Intent tag for the message. Five permitted types. 'marketing' is allowed only…
- `on_behalf_of` (string): Who this message is FOR (your end-user's name/label). On WhatsApp this opens a…
- `preferred_channel` (string)
- `recipient` (object, required)
- `send_at_iso` (string): NOT SUPPORTED YET. We do not schedule messages. Supplying a time more than 2…

### `send_transactional_confirmation` (~163 tokens)

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] [async→get_outcome]

Input parameters:

- `confirmation_type` (string, required)
- `data` (object, required): Type-specific payload; e.g., {otp_code} for otp, {appointment_time, smb_name}…
- `idempotency_key` (string): Optional client-supplied key for safe retries. Replaying the same key within 24h returns the original receipt - the operation is NOT re-executed and NOT re-charged.
- `preferred_channel` (string)
- `recipient` (object, required)

### `get_status` (~36 tokens)

Query the current state of any in-flight async operation by operation_id. [free, no key]

Input parameters:

- `operation_id` (string, required)

### `get_outcome` (~33 tokens)

Retrieve the final OutcomeReceipt for a completed operation. [free, no key]

Input parameters:

- `operation_id` (string, required)

### `preview_cost` (~95 tokens)

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]

Input parameters:

- `operation` (string, required)
- `params` (object, required): The same request body you would pass to the operation

### `self_test` (~54 tokens)

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]

### `check_compliance` (~283 tokens)

Free, instant pre-flight for the compliance gate. Runs the SAME TCPA / GDPR / CASL / CAN-SPAM / 10DLC gate that send_message and call_business run — but in preview mode, so NO message is sent and NO state changes. Tells you whether a (recipient, channel, message_type, content) send would be permitted BEFORE you pay for it, and if not, names the exact rule and how to remediate. Use it to de-risk a paid send the same way check_booking_link… [free, no key]

Input parameters:

- `channel` (string): Delivery channel. Omit to auto-infer sms/email from recipient_id; set 'voice'…
- `content` (string, required): The actual message body you intend to send. The gate classifies the real text,…
- `country_code` (string): ISO 3166-1 alpha-2 (e.g. 'US', 'DE', 'CA'). Auto-inferred from phone if…
- `message_type` (string): Intent tag: transactional, marketing, reminder, follow_up, notification.…
- `recipient_id` (string, required): Phone in E.164 (e.g. '+14045550100') or email address the message would go to.
- `state_code` (string): US state code (e.g. 'CA') for state-specific rules.

### `get_conversation` (~102 tokens)

Read a two-way conversation thread you started: its state, every message exchanged, and how many replies the business has sent. [free, no key]

Input parameters:

- `business_number` (string): Scopes a `reference` to one business (references are reused across businesses).
- `conversation_id` (string): From the send_message receipt (preferred).
- `reference` (string): The 4-digit request reference, e.g. '4821'. Requires business_number.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-hatchloop-sms-whatsapp-messaging/mcp-sms-whatsapp-messaging#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 69
- 2026-09-10: 67
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 65
- 2026-09-06: 64
- 2026-09-05: 64
- 2026-09-04: 63
- 2026-09-03: 63
- 2026-09-02: 62
- 2026-09-01: 62

## Common questions

### What is the SMS and WhatsApp Messaging MCP server?

SMS and WhatsApp Messaging is an MCP server listed in the public MCP registry as dev.hatchloop/sms-whatsapp-messaging. Send WhatsApp, SMS, email or voice to a business with the compliance gate enforced. This page covers its hosted endpoint (https://hatchloop.dev/mcp/sms-whatsapp-messaging).

### Is the SMS and WhatsApp Messaging MCP server safe to use?

SMS and WhatsApp Messaging scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SMS and WhatsApp Messaging MCP server expose?

SMS and WhatsApp Messaging exposes 10 tools: find_business, verify_business, send_message, send_transactional_confirmation, get_status, and 5 more. Their descriptions and schemas cost roughly 1,288 tokens of context every time the server is loaded.

### Does the SMS and WhatsApp Messaging MCP server require authentication?

No. We connected to SMS and WhatsApp Messaging without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SMS and WhatsApp Messaging MCP server still maintained?

SMS and WhatsApp Messaging is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://hatchloop.dev/mcp/sms-whatsapp-messaging
- Repository: https://github.com/basilalshukaili/agentbroker
- Website: https://hatchloop.dev/agent-broker/
- Changelog RSS feed: https://verifymcp.io/servers/dev-hatchloop-sms-whatsapp-messaging/mcp-sms-whatsapp-messaging.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-hatchloop-sms-whatsapp-messaging/mcp-sms-whatsapp-messaging.json
- HTML version of this page: https://verifymcp.io/servers/dev-hatchloop-sms-whatsapp-messaging/mcp-sms-whatsapp-messaging