# Bandwidth Messaging API + MCP vs Kudosity (slim)

> Bandwidth Messaging scores 70.6 (BB) to Kudosity's 63.7 (B) for sms. Bandwidth Messaging is cheaper for sms, $0.004 against $0.055 per message. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bandwidth-vs-kudosity.md (~5,050 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/bandwidth-vs-kudosity.json · canonical https://www.anchorterminal.com/compare/bandwidth-vs-kudosity
- 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)

Bandwidth Messaging API + MCP scores 70.6 (BB) on agent readiness against Kudosity's 63.7 (B), and leads in 4 of 7 scored categories. Kudosity leads on reliability. Both do sms. Bandwidth Messaging API + MCP is cheaper for sms, $0.004 against $0.055 per message.

- Bandwidth Messaging API + MCP: BB 70.6, rank #194 of 1486 · https://www.anchorterminal.com/tools/bandwidth.min.md
- Kudosity: B 63.7, rank #503 of 1486 · https://www.anchorterminal.com/tools/kudosity.min.md
- Bandwidth Messaging API + MCP, good for US and Canada senders at volume who want carrier-owned routes and will talk to sales, and developers who want to test sends on a no-card trial first. Ahead on Security & auth, 65 against 37; Payments & pricing, 40 against 32; Maintenance & community, 78 against 57; Transparency & trust, 75 against 62. Also Cheaper for sms, $0.004 against $0.055 per message; Agent-ready, a grade of BB or better.
- Kudosity, good for Agents sending SMS in Australia, New Zealand and the UK, and WhatsApp templates, from one account. Ahead on Reliability, 85 against 75. Also Free to start without a card.

| Category | Bandwidth Messaging API + MCP | Kudosity |
| --- | --- | --- |
| Reliability (16%) | 75 | 85 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 86 |
| Agent ergonomics (13%) | 73 | 73 |
| Security & auth (14%) | 65 | 37 |
| Payments & pricing (10%) | 40 | 32 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 57 |
| Transparency & trust (7%) | 75 | 62 |

| Fact (where they differ) | Bandwidth Messaging API + MCP | Kudosity |
| --- | --- | --- |
| Vendor | Bandwidth | Known Pty Ltd (Kudosity) |
| Hosted endpoint | `https://messaging.bandwidth.com/api/v2` | `https://api.transmitmessage.com` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, stdio |
| Auth | OAuth | API key |
| Pricing | Paid | Pay per use |
| Price for sms | $0.004 per message | $0.055 per message |
| Licence | none | Proprietary service under Known Pty Ltd's terms and conditions. The `kudosity-mcp` server is MIT |
| Tools exposed | none | 19 |
| MCP registry | not listed | `com.kudosity/mcp` |
| Last release | 2026-10-16 | 2026-07-27 |
| Terms last updated | 2025-09-11 | 2026-09-23 |
| Privacy policy last updated | 2026-08-25 | 2024-08-08 |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | 2 stars, 13k npm/wk, 39k PyPI/wk | 40 npm/wk |
| Agent reviews | 3.5/5 (2) | none |

Why the edge:
- Security & auth, Bandwidth Messaging API + MCP +28: Bandwidth Messaging API + MCP 65 (OAuth 2.0 client credentials exchanged for Bearer tokens that expire after 1 hour. Credentials carry roles and a basic or admin account scope, and secrets rotate with two active at once, per the 1 October check (30). Roles limit what a credential reaches, but we found no read-only messaging role and no confirmation step before sends. The MCP can be cut to the messaging profile or an explicit tool list (10 of 20). Inbound messages are untrusted text. Callbacks go to the application URL, and we found no callback signing or injection guidance (0 of 15). Message records by API through listMessages (10 of 15). The security page lists ISO 27001:2022, ISO 42001:2023 and SOC 2 Type II, says Bandwidth runs a public bug bounty, and links a vulnerability reporting page with scope and rules. No reward terms were found on that page, no security.txt (404 on 2 November) and no advisories for bandwidth-sdk in OSV. Read as modal-sandboxes' programme line (SOC 2, a bounty and a reporting route, no security.txt) (15 of 20). 30 + 10 + 0 + 10 + 15 = 65.); Kudosity 37 (One account-wide API key on V2 and Basic auth with the key and a secret the user types in on V1, both in headers. No scopes, read-only keys or rotation steps were found (12 of 30). No least-privilege mode. The MCP server works without the V1 secret, which leaves out the contact and balance tools, and marks its three delete tools destructive, with no confirmation step (4 of 20). Inbound SMS, WhatsApp and RCS text reaches the agent through webhooks and `list_messages`, and no prompt-injection guidance was found (0 of 15). Message reports and activity reports by API; the trust centre lists audit logging policies, with no operator log of API calls found (6 of 15). ISO/IEC 27001:2022 and SOC 2 Type 2 stated on kudosity.com/security and the trust centre, a pentest report on request, and a disclosure route by support ticket with acknowledgement in about 5 business days; no security.txt or bug bounty (15 of 20). 12 + 4 + 0 + 6 + 15 = 37.)
- Maintenance & community, Bandwidth Messaging API + MCP +21: Bandwidth Messaging API + MCP 78 (Dated release notes, the latest on 16 October 2026 (30). Release notes from 6 August to 16 October, among them 10DLC messaging and SMS on Build (13 October, two entries) and 10DLC registration in the App (31 August), well over three (20). Closed service with release notes and account management. The MCP repository's last commit is still 21 July 2026 and v0.3.0 (11 June) its newest tag (8 of 15). Official SDKs in six languages, node-sdk v8.3.1 and python-sdk v23.3.1 on 13 October 2026 (15). SDKs are generated from the spec, CI not checked (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.); Kudosity 57 (`kudosity-mcp` 0.5.0, its only release, is dated 27 July 2026, 102 days ago; the API reference pages for WhatsApp templates and the error registry were updated on 6 November 2026, read as the last published API change (20). The changelog's six newest entries carry no dates. Within 90 days the dated changes we found are docs page updates (13 August, 16 and 18 September, 6 November), not changelog entries, so half (10 of 20). Closed service with a support portal and help centre; GitHub issues on kudosity/mcp couldn't be read because the GitHub API refused our requests (6 of 15). `com.kudosity/mcp` is in the official MCP registry under a DNS-verified namespace (15). The MCP repository runs CI with mock integration tests and a live spec test, on three commits (6 of 10). 20 + 10 + 6 + 15 + 6 = 57.)
- Transparency & trust, Bandwidth Messaging API + MCP +13: Bandwidth Messaging API + MCP 75 (Closed service with clear terms (communications services agreement). The MCP server repository still has no licence file (15). Privacy notice, a global DPA with Standard Contractual Clauses, a transfer impact assessment FAQ and a sub-processor list that agree. No retention periods found (20 of 30). The legacy credential migration is documented, with no dated deprecation policy found (5 of 20). The sub-processor list (last updated 31 March 2026) names each provider with the product it supports and the location of processing, such as AWS for hosting in the USA and EU (20). 15 + 20 + 5 + 20 = 60.); Kudosity 62 (Closed service with clear terms from Known Pty Ltd (23 September 2026); the MCP server is MIT (17 of 30). The privacy policy says personal data is deleted within 12 months of account closure and refers to a DPA that isn't linked; its dates disagree (8 August 2024 against 25 May 2018), and the trust centre says customer data is stored on AWS and GCP in Sydney (14 of 30). The terms promise at least 30 days' notice of a materially adverse change; V1 is kept with no retirement date and RCS is marked beta (10 of 20). Data locations are named; the sub-processor list is given on request only (8 of 20). 17 + 14 + 10 + 8 = 49.)
- Reliability, Kudosity +10: Bandwidth Messaging API + MCP 75 (Statuspage at status.bandwidth.com with datacentre, market and messaging components (20). Read from its own history pages on 2 November (the 1 October count from IsDown, a third-party copy of the page, is struck). From 4 August to 2 November the messaging incidents each name one carrier, one country or provisioning only, among them AT&T 10DLC spam rejections on 7 October (20 minutes, AT&T destinations), AT&T, Verizon and T-Mobile MMS delays, Australia SMS on 20 October, a Symbio-only incident on 18 August and messaging provisioning delays on 1 and 2 October that Bandwidth called limited in scope. The majors on the page are single voice markets, port orders and the portal. Partial incidents read as minor, so minor only (20). Default limits are published with numbers in the help centre (1 message a second per account and per number for new accounts, A2P up to the account limit, T-Mobile's 300 unique recipients a day for P2P), and a full queue returns 429 with the allowed rate (15). The page recommends exponential back-off, throttling and an external queue, with no Retry-After or idempotency key (10 of 15). No SLA found (0). The Messaging API is generally available. The MCP server is beta (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.); Kudosity 85 (Read with the hosted lines. status.transmitsms.com is a Statuspage page with components for both API hosts, webhooks, campaigns and each country (20). Its history pages show no incident in August, September, October or November 2026; the newest before that is a minor UI disruption on 28 July (30). 15 calls a second per account, documented (15). A 429 carries OVER_LIMIT and the docs say the dropped message isn't retried; the error registry says to wait and retry, and the V2 spec defines an Idempotency-Key with a replay header and Retry-After, though no V2 operation lists the header as a parameter (10 of 15). The terms refer to a separate service level agreement that isn't published (0). SMS, MMS and WhatsApp on V2 are generally available; RCS is marked beta (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.)
- Payments & pricing, Bandwidth Messaging API + MCP +8: Bandwidth Messaging API + MCP 40 (No x402, MPP or L402 (0). US per-message rates for 10DLC, toll-free and short code are published, re-read on 2 November (20). Since 13 October 2026 the Bandwidth Build trial (3,000 credits, no credit card) includes 30 days of 10DLC SMS through the Messaging API, limited to texts between the Build number and the verified mobile number, watermarked, SMS only and US and Canada only (20). An agent can start a Build registration with the Bandwidth CLI, but a person verifies a phone code, sets a password from an emailed link and creates API credentials in the Bandwidth App, and sending to customers needs a full account through the account team (0). 0 + 20 + 20 + 0 = 40.); Kudosity 32 (No x402, MPP or L402 (0). SMS is priced per part without login, 8.0 cents AUD ex GST pay as you go; MMS, RCS and WhatsApp are on request (12 of 20). A 14-day developer trial whose form asks for no card (20). A person signs up in a browser and verifies by email (0). 0 + 12 + 20 + 0 = 32.)