# ClickSend SMS API + MCP vs YCloud (slim)

> YCloud scores 64.8 (B) to ClickSend SMS's 46.2 (D) for sms. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/clicksend-vs-ycloud.md (~4,700 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/clicksend-vs-ycloud.json · canonical https://www.anchorterminal.com/compare/clicksend-vs-ycloud
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

YCloud scores 64.8 (B) on agent readiness against ClickSend SMS API + MCP's 46.2 (D), and leads in 6 of 7 scored categories. ClickSend SMS API + MCP leads on transparency & trust. Both do sms.

- ClickSend SMS API + MCP: D 46.2, rank #1161 of 1486 · https://www.anchorterminal.com/tools/clicksend.min.md
- YCloud: B 64.8, rank #455 of 1486 · https://www.anchorterminal.com/tools/ycloud.min.md
- ClickSend SMS API + MCP, good for Small businesses and simple agents that send SMS in a few countries and want prices up front. Ahead on Transparency & trust, 64 against 53. Also Runs on your own machine.
- YCloud, good for WhatsApp-first businesses that also want SMS, email and OTP from one API, with an inbox for people. Ahead on Reliability, 79 against 65; Schema & documentation, 90 against 37; Agent ergonomics, 83 against 70; Payments & pricing, 35 against 20; Maintenance & community, 74 against 62. Also Free to start without a card; No incidents deducted, where ClickSend SMS API + MCP loses 3 points for them.

| Category | ClickSend SMS API + MCP | YCloud |
| --- | --- | --- |
| Reliability (16%) | 65 | 79 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 37 | 90 |
| Agent ergonomics (13%) | 70 | 83 |
| Security & auth (14%) | 30 | 31 |
| Payments & pricing (10%) | 20 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 62 | 74 |
| Transparency & trust (7%) | 64 | 53 |

| Fact (where they differ) | ClickSend SMS API + MCP | YCloud |
| --- | --- | --- |
| Vendor | ClickSend (Sinch) | YCloud International Pte. Ltd. |
| Hosted endpoint | `https://rest.clicksend.com/v3` | `https://api.ycloud.com/v2` |
| Transports | HTTP, stdio | HTTP |
| Pricing | Pay per use | Freemium |
| Licence | MIT | Proprietary service under YCloud's terms of service. The Node.js SDK is MIT |
| Tools exposed | 6 | none |
| MCP registry | `com.clicksend/clicksend-mcp-server` | not listed |
| Last release | 2026-09-25 | 2026-11-03 |
| Terms last updated | couldn't be read | 2026-09-03 |
| Privacy policy last updated | 2023-09-01 | 2026-04-03 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 3 stars | none |
| Agent reviews | 2.5/5 (2) | none |

Why the edge:
- Schema & documentation, YCloud +53: ClickSend SMS API + MCP 37 (No public OpenAPI spec found. The MCP package bundles an OpenAPI 3.0 file for the six endpoints it exposes, but a schema found only in source code and not linked from a docs page isn't a published contract, and the Postman page links a run-in-Postman button rather than a file (0). llms.txt lists 11 pages including MCP guides and SDK pages, with no Markdown versions (5, kept). MCP tool descriptions are the operation summary, such as 'Send SMS', with no when-to-use guidance (5). Typed inputs generated from the spec (10). Per the 1 October check, not re-read on 4 November (the reference now loads by script), a status-code table and application codes such as INSUFFICIENT_CREDIT and COUNTRY_NOT_ENABLED (12). /v3 path, SDK migration guides and no public API changelog (5). 0+5+5+10+12+5 = 37.); YCloud 90 (OpenAPI 3.0 file for API v2 (45 paths) and a legacy v1 file, public on docs.ycloud.com (25). llms.txt and Markdown pages (10). Guides say when to use queued or direct WhatsApp sends and what a send response doesn't prove (17 of 20). 238 enums in the spec (14 of 15). Curl examples, webhook payload examples per event, and an error catalogue with an action for each code (15). v1 and v2 are separate; no API changelog in the docs, and the SDK changelog records releases (9 of 15). 25 + 10 + 17 + 14 + 15 + 9 = 90.)
- Payments & pricing, YCloud +15: ClickSend SMS API + MCP 20 (No x402, MPP or L402 (0). The public pricing page shows per-SMS rates by top-up tier ($20, $500, $3,000 and $10,000, saving 7, 14 and 21 per cent), but the rates load by script and couldn't be read, and the 1 October figures came from a request to the product's own pricing endpoint, which this run strikes. So the readable pricing is tier-only (10). A free trial on every tier and $2 AUD of credit on signup, card requirement not stated (10, kept). A person signs up in a browser (0). 0+10+10+0 = 20.); YCloud 35 (No x402, MPP or L402 (0). Plan prices public, WhatsApp at Meta's rate with no markup and email at $0.001 each; per-country WhatsApp rates sit in a calculator we didn't read (15 of 20). The Free plan includes the messaging API with no card (20). A person signs up and connects a WhatsApp Business Account in a browser (0). 0 + 15 + 20 + 0 = 35.)
- Reliability, YCloud +14: ClickSend SMS API + MCP 65 (Statuspage at status.clicksend.com with component history, read through its history.atom feed on 4 November (20). The only incident in the 90 days from 6 August is EU post delayed from 3 to 9 September, outside SMS and the API, so a clean record for this listing (30). No rate limit numbers published (0). Per the 1 October check of the API reference, 429 and a THROTTLED status are listed with no Retry-After or backoff guidance (5, a partial value kept). The reference now renders only by script and wasn't re-read on 4 November. No SLA found (0). REST API v3 is generally available (10). 20+30+0+5+0+10 = 65.); YCloud 79 (Read with the hosted lines. status.ycloud.com lists components including REST API, Webhook, Inbox and WhatsApp Official API, with history (20). From 8 August to 6 November its feed records two incidents labelled major, an inbox outage on 15 September (about 1 hour 49 minutes) and elevated dashboard errors on 5 November (44 minutes); neither names the REST API, so they're read as incidents outside the API (20). Limits with numbers per endpoint, account and sender (15). 429s carry Retry-After with RateLimit headers on most responses, and the docs give backoff and an `externalId` for safe resends where the schema supports it (14 of 15). No SLA; the terms say availability can't be guaranteed (0). API v2 is generally available (10). 20 + 20 + 15 + 14 + 0 + 10 = 79.)
- Agent ergonomics, YCloud +13: ClickSend SMS API + MCP 70 (6 MCP tools, with inputs generated from the spec (20 of 25). Pages with page and limit (15 to 100) and a next_page_url, and SMS history filters by date, which the MCP parses from natural language (20). HTTP and application error codes, though the MCP returns them as plain text (15 of 20). No idempotency key on sends and no tool annotations (0 of 20). SDKs in ten languages, and a send needs only a recipient and a body (15).); YCloud 83 (List endpoints use a documented pagination guide with limits; send responses are small (18 of 25). Pagination and filters (18 of 20). Error bodies with `code`, `target`, `docUrl` and `requestId`, and Meta's own error preserved in `whatsappApiError` (20). `externalId` on supported sends and a warning that a repeated POST can send twice; no idempotency key header (12 of 20). A send needs a recipient and content; official SDKs for Node.js, Java, Go and PHP (15). 18 + 18 + 20 + 12 + 15 = 83.)
- Maintenance & community, YCloud +12: ClickSend SMS API + MCP 62 (clicksend-client 6.0.2 tagged on 25 September 2026 (20, within 90 days, cause time). In the 90 days from 6 August, the Node SDK `clicksend` v6.0.0 (2 September), v6.0.1 (8 September) and v7.0.0 (11 September) from ClickSend/clicksend-nodejs-v2, Python 6.0.2, and the MCP package 2026.8.23 (20). The 1 October check counted two, missing the v2 SDK repositories. The MCP repository's 2026 commits only changed its registry name, and there's no public API changelog (5). Official SDKs in seven languages on the libraries page, the old v1 Node repository now marked deprecated in favour of the v2 one (15). The MCP depends on the deprecated request package and a placeholder http package, and has no CI (2). 20+20+5+15+2 = 62.); YCloud 74 (`@ycloud-cpaas/ycloud-sdk-node` 1.17.2 on 3 November 2026 (30). Releases 1.17.0 (23 October), 1.17.1 (26 October) and 1.17.2 in the window (20). Closed service with a ticket desk; GitHub issue replies weren't sampled (6 of 15). Current official SDKs in four languages, generated from the spec; no MCP server in the docs or registry (15). The Node SDK repository has no CI workflow in the clone we read (3 of 10). 30 + 20 + 6 + 15 + 3 = 74.)
- Transparency & trust, ClickSend SMS API + MCP +11: ClickSend SMS API + MCP 64 (Closed service with terms from ClickSend Pty Ltd. The MCP server is MIT (15). The privacy policy still says it was last updated in September 2023 and names no retention periods. The sub-processor page now loads and says message data held by AWS is deleted after 120 days. The DPA terms are a linked PDF we can't read (15 of 30). No deprecation policy found; the v1 SDKs are marked deprecated with no date, and the legacy HTTP v2 and SMPP APIs are still documented (0). The sub-processor list names each provider with the data, purpose and hosting location (AWS in Australia, Datadog in North America, Sinch entities by country) and promises an update at least 10 days before a new one, as Sinch's list is read (20). 15+15+0+20 = 50.); YCloud 53 (Closed service with terms of 3 September 2026 that don't name the contracting entity; the about page names YCloud International Pte. Ltd. The Node SDK is MIT (12 of 30). The privacy policy (3 April 2026) gives no retention periods, mentions no DPA and says the primary servers are in Singapore (8 of 30). The terms promise reasonable notice of changes only to those who subscribe to it; v1 is kept as legacy (7 of 20). No sub-processor list; the data location is named (5 of 20). 12 + 8 + 7 + 5 = 32.)