{ "data": { "a": { "slug": "twilio", "name": "Twilio API + MCP", "vendor": "Twilio", "vendorUrl": "https://www.twilio.com", "kind": "http-api", "category": "messaging", "summary": "Programmable Messaging (SMS, MMS, WhatsApp, RCS) and Verify over REST.", "url": "https://www.anchorterminal.com/tools/twilio", "markdownUrl": "https://www.anchorterminal.com/tools/twilio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/twilio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/twilio.json", "repo": "https://github.com/twilio-labs/mcp", "license": "MIT", "transports": [ "http", "streamable-http", "stdio" ], "remoteUrl": "https://api.twilio.com/2010-04-01", "packages": [ { "registry": "npm", "name": "twilio" }, { "registry": "pypi", "name": "twilio" }, { "registry": "npm", "name": "@twilio-alpha/mcp" } ], "auth": "mixed", "authNotes": "HTTP Basic auth with the Account SID and Auth Token, or an API key SID and secret (recommended). The hosted docs MCP needs no credentials. The local alpha MCP takes `ACCOUNT_SID/API_KEY:API_SECRET` as a command-line argument, so it shows up in process lists.", "pricing": "usage", "pricingNotes": "Pay as you go, no monthly fee. US SMS $0.0083 a segment outbound or inbound on long code, toll-free or short code, plus carrier fees of $0.0035 (AT\u0026T), $0.0045 (T-Mobile) or $0.005 (Verizon) a message. US MMS $0.022 outbound, $0.0165 inbound on long code. Long code numbers $1.15 a month, toll-free $2.15. UK SMS $0.056. Failed messages $0.001 each. WhatsApp $0.005 a message Twilio fee plus Meta's template fees. Verify $0.05 a successful verification plus channel fees. Trial lasts 30 days with free units (100 SMS), no card (https://www.twilio.com/en-us/sms/pricing/us).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402 support in docs, pricing or MCP README (checked 2026-09-30).", "endpoints": [] }, "toolCount": 2, "popularity": { "githubStars": 111, "npmWeekly": 7213599, "pypiWeekly": 4834611, "asOf": "2026-09-30" }, "docsUrl": "https://www.twilio.com/docs/messaging", "llmsTxt": "https://www.twilio.com/docs/llms.txt", "openapi": "https://raw.githubusercontent.com/twilio/twilio-oai/main/spec/json/twilio_api_v2010.json", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.whatsapp", "messaging.rcs", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "no-card", "mcp", "llms-txt", "openapi", "typescript", "python", "webhooks", "whatsapp", "sms", "enterprise" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 80.4, "grade": "A", "agentReady": true, "rank": 5, "ranked": true, "rankOf": 452, "categoryRank": 1, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 85, "payments": 40, "reliability": 90, "schema": 92, "security": 85, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.", "strengths": [ "Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login", "Restricted API keys with up to 100 endpoint permissions each", "Twilio APIs SLA at 99.95 per cent for every paying customer, with 10 per cent credits", "Public OpenAPI specs, llms.txt with Markdown twins and a numbered error dictionary", "twilio-node released three times in the last 90 days, most recently 6.1.2 on 2026-09-28" ], "weaknesses": [ "US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate", "A US long code sends 1 message a second per Twilio's scaling guide, with the excess queued for up to 10 hours", "No idempotency key on message creation", "The MCP that can send is an alpha last published on 2025-07-07, and it takes the API secret as a command-line argument", "No security.txt on twilio.com" ], "agentNotes": [ "Use the hosted docs MCP to find the endpoint, then call the REST API with a restricted API key", "Set `ValidityPeriod` on time-sensitive sends, or a queued message can go out up to 10 hours late", "Check the Messages list for the original before retrying a send that timed out, there's no idempotency key", "Send only to verified numbers on a trial account, other recipients fail", "Validate `X-Twilio-Signature` on every inbound webhook" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 8, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 80.4 } ], "editorialScores": { "ergonomics": 80, "maintenance": 85, "payments": 40, "reliability": 90, "schema": 92, "security": 85, "transparency": 72 }, "provenanceScore": 90 }, "connect": { "http": "curl -X POST \"https://api.twilio.com/2010-04-01/Accounts/$TWILIO_ACCOUNT_SID/Messages.json\" \\\n -u \"$TWILIO_API_KEY:$TWILIO_API_SECRET\" \\\n --data-urlencode \"To=+15558675310\" --data-urlencode \"From=+15017122661\" \\\n --data-urlencode \"Body=Hello from Twilio\"", "claudeCode": "claude mcp add --transport http twilio-docs https://mcp.twilio.com/docs", "config": { "mcpServers": { "twilio": { "args": [ "-y", "@twilio-alpha/mcp", "${TWILIO_ACCOUNT_SID}/${TWILIO_API_KEY}:${TWILIO_API_SECRET}", "--services", "twilio_api_v2010" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/twilio" }, "sameCompany": [ "twilio-voice", "stytch-connected-apps", "sendgrid" ], "area": "communication", "unitPrices": [ { "item": "SMS outbound, US", "unit": "message", "usd": 0.0083, "note": "per segment, plus carrier fees of $0.0035 to $0.005" }, { "item": "SMS outbound, UK", "unit": "message", "usd": 0.056 }, { "item": "MMS outbound, US", "unit": "message", "usd": 0.022 }, { "item": "WhatsApp Twilio fee", "unit": "message", "usd": 0.005, "note": "inbound or outbound, Meta template fees extra" }, { "item": "WhatsApp utility or authentication template, US (Meta fee)", "unit": "message", "usd": 0.0034, "note": "passed through by Twilio" } ], "provenance": { "legalEntity": "Twilio Inc.", "domain": "twilio.com", "domainRegistered": "2007-10-26", "endpointOnVendorDomain": true, "terms": "https://www.twilio.com/en-us/legal/tos", "privacy": "https://www.twilio.com/en-us/legal/privacy", "statusPage": "https://status.twilio.com", "changelog": "https://www.twilio.com/en-us/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The terms also name Twilio Ireland Limited for customers outside the US." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/twilio.json", "live": { "slug": "twilio", "probe": { "target": "https://api.twilio.com/2010-04-01", "method": "get", "lastAt": "2026-10-05T00:15:31.635835274Z", "lastOk": true, "lastStatus": 200, "lastMs": 18, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 6, "p95ms24h": 38, "samples24h": 272, "samples30d": 1105, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 3, "ok": 3 } ] }, "vendorStatus": { "page": "https://status.twilio.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-05T00:11:36.452644723Z" }, "versions": [ { "registry": "github", "name": "twilio-labs/mcp", "version": "0.0.3", "released": "2025-03-25", "seenAt": "2026-10-04T16:42:32.789428185Z" }, { "registry": "npm", "name": "@twilio-alpha/mcp", "version": "0.7.0", "seenAt": "2026-10-04T16:42:30.744113269Z" }, { "registry": "npm", "name": "twilio", "version": "6.1.2", "seenAt": "2026-10-04T16:42:30.579018738Z" }, { "registry": "pypi", "name": "twilio", "version": "9.11.2", "released": "2026-09-28", "seenAt": "2026-10-04T16:42:30.630910608Z" } ], "githubStars": 112, "npmWeekly": 7817134, "pypiWeekly": 5153208, "securityTxt": { "url": "https://twilio.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:43.282608786Z" }, "llmsTxt": { "url": "https://www.twilio.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:20.462714763Z" }, "domain": { "domain": "twilio.com", "registered": "2007-10-26", "source": "https://rdap.verisign.com/com/v1/domain/twilio.com", "checkedAt": "2026-10-04T13:05:12.523190086Z" }, "pages": [ { "url": "https://www.twilio.com/en-us/sms/pricing/us", "kind": "pricing", "status": 200, "checkedAt": "2026-10-04T15:52:40.063019901Z", "changedAt": "2026-10-03T15:40:31.280177197Z", "fingerprint": "b98c31a1bf5b" } ], "updatedAt": "2026-10-05T00:15:31.635835274Z" } }, "b": { "slug": "vonage", "name": "Vonage Messages API + MCP", "vendor": "Vonage (Ericsson)", "vendorUrl": "https://www.vonage.com", "kind": "http-api", "category": "messaging", "summary": "One endpoint (POST /v1/messages) for SMS, MMS, WhatsApp, RCS, Viber and Messenger, with failover between channels.", "url": "https://www.anchorterminal.com/tools/vonage", "markdownUrl": "https://www.anchorterminal.com/tools/vonage.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vonage.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vonage.json", "repo": "https://github.com/Vonage-Community/vonage-mcp-server-api-bindings", "license": "Apache-2.0", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://api.nexmo.com/v1", "packages": [ { "registry": "npm", "name": "@vonage/server-sdk" }, { "registry": "pypi", "name": "vonage" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings" } ], "auth": "mixed", "authNotes": "Messages API takes a Vonage Application JWT (RS256, signed with the application's private key) or Basic auth with the API key and secret. Basic auth doesn't deliver to application-level webhooks. Inbound webhooks carry an HS256 JWT to verify. The MCP server reads the key, secret, application ID and a base64 private key from env vars.", "pricing": "usage", "pricingNotes": "Pay as you go per message. Rates vary by country and channel and appear only through a country selector or a downloadable sheet. WhatsApp adds a Vonage platform fee to Meta's template fees. New accounts get €2 of test credit and no card is needed (https://www.vonage.com/communications-apis/messages/pricing/).", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "no", "evidence": "No x402 support in docs, pricing or MCP README (checked 2026-09-30).", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": null, "npmWeekly": 154249, "pypiWeekly": 67062, "asOf": "2026-09-30" }, "docsUrl": "https://developer.vonage.com/en/messages/overview", "llmsTxt": "https://developer.vonage.com/llms.txt", "openapi": "https://developer.vonage.com/api/v1/developer/api/file/messages?format=json", "registryName": "io.github.Vonage/vonage-documentation-mcp", "capabilities": [ "messaging.sms", "messaging.mms", "messaging.whatsapp", "messaging.rcs", "messaging.verify", "messaging.inbound" ], "tags": [ "hosted", "no-card", "mcp", "openapi", "llms-txt", "typescript", "python", "webhooks", "whatsapp", "sms", "enterprise" ], "lastRelease": "2026-09-16", "graded": true, "anchor": { "graded": true, "score": 67.1, "grade": "B", "agentReady": false, "rank": 146, "ranked": true, "rankOf": 452, "categoryRank": 4, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.", "strengths": [ "POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS", "OpenAPI 3.0.3 spec for the Messages API (version 1.19.1), and SDK releases in Node and Python through September 2026", "75 requests a second per API key, with Retry-After and X-RateLimit headers on 429", "Application JWTs with ACL claims that limit paths and methods", "ISO 27001, PCI-DSS, SOC, HITRUST and CSA STAR listed on the security page, and an Audit API for account events" ], "weaknesses": [ "No idempotency key, and channel rejections arrive only by status webhook after a 202", "The sending MCP lives in the Vonage-Community GitHub organisation, last released on 2026-05-26, with no tool annotations", "SMS, WhatsApp and RCS prices sit behind a country selector, and the terms body doesn't render without a browser", "No SLA, security.txt, sub-processor list or retention periods found", "The Audit API costs $550 a month" ], "agentNotes": [ "Keep api.nexmo.com as the host, don't rewrite it to vonage.com", "Use the Messages API, not the legacy SMS API", "Treat a 202 as accepted only, and wait for the status webhook before assuming delivery", "Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks", "Verify the webhook JWT and its payload_hash against the raw body" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.3", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.1 } ], "editorialScores": { "ergonomics": 50, "maintenance": 80, "payments": 37, "reliability": 77, "schema": 90, "security": 73, "transparency": 28 }, "provenanceScore": 75 }, "connect": { "http": "curl https://api.nexmo.com/v1/messages -u \"$VONAGE_API_KEY:$VONAGE_API_SECRET\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"message_type\":\"text\",\"channel\":\"sms\",\"to\":\"447700900000\",\"from\":\"Vonage\",\"text\":\"Hello from Vonage\"}'", "claudeCode": "claude mcp add --transport http vonage-docs https://documentation-mcp.vonage.dev/mcp", "config": { "mcpServers": { "vonage": { "args": [ "-y", "@vonage/vonage-mcp-server-api-bindings" ], "command": "npx", "env": { "VONAGE_API_KEY": "${VONAGE_API_KEY}", "VONAGE_API_SECRET": "${VONAGE_API_SECRET}", "VONAGE_APPLICATION_ID": "${VONAGE_APPLICATION_ID}", "VONAGE_PRIVATE_KEY64": "${VONAGE_PRIVATE_KEY64}", "VONAGE_VIRTUAL_NUMBER": "${VONAGE_VIRTUAL_NUMBER}" } } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/vonage" }, "sameCompany": [ "vonage-voice" ], "area": "communication", "provenance": { "legalEntity": "Vonage Holdings Corp.", "domain": "vonage.com", "domainRegistered": "2000-12-12", "domainNote": "The API endpoints sit on the legacy nexmo.com domain, from Nexmo's acquisition in 2016.", "endpointOnVendorDomain": false, "terms": "https://www.vonage.com/legal/communications-apis/terms-of-use/", "privacy": "https://www.vonage.com/legal/privacy-policy/", "statusPage": "https://vonageapi.statuspage.io", "changelog": "https://developer.vonage.com/en/changelogs", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The privacy notice names Vonage Holdings Corp. as controller where one entity applies. The API terms set the contracting entity by customer region in Schedule 1, which we couldn't read because vonage.com returned 403 to automated requests." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vonage.json", "live": { "slug": "vonage", "probe": { "target": "https://api.nexmo.com/v1", "method": "get", "lastAt": "2026-10-05T00:15:32.572165626Z", "lastOk": true, "lastStatus": 404, "lastMs": 19, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 24, "p95ms24h": 58, "samples24h": 272, "samples30d": 1105, "days": [ { "date": "2026-09-30", "probes": 35, "ok": 35 }, { "date": "2026-10-01", "probes": 276, "ok": 276 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 3, "ok": 3 } ] }, "vendorStatus": { "page": "https://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-05T00:11:36.658694795Z" }, "versions": [ { "registry": "github", "name": "Vonage-Community/vonage-mcp-server-api-bindings", "version": "v1.5.0", "released": "2026-05-21", "seenAt": "2026-10-04T16:43:47.420905564Z" }, { "registry": "mcp-registry", "name": "io.github.Vonage/vonage-documentation-mcp", "version": "1.0.0", "seenAt": "2026-10-04T23:42:40.113054682Z" }, { "registry": "npm", "name": "@vonage/server-sdk", "version": "3.30.1", "seenAt": "2026-10-04T16:43:43.414771728Z" }, { "registry": "npm", "name": "@vonage/vonage-mcp-server-api-bindings", "version": "1.5.1", "seenAt": "2026-10-04T16:43:45.553661658Z" }, { "registry": "pypi", "name": "vonage", "version": "4.9.0", "released": "2026-09-16", "seenAt": "2026-10-04T16:43:45.441057302Z" } ], "githubStars": 3, "npmWeekly": 152256, "pypiWeekly": 69501, "securityTxt": { "url": "https://vonage.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:53.518357179Z" }, "llmsTxt": { "url": "https://developer.vonage.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:23.288863365Z" }, "domain": { "domain": "vonage.com", "registered": "2000-12-12", "source": "https://rdap.verisign.com/com/v1/domain/vonage.com", "checkedAt": "2026-10-04T13:04:15.703583171Z" }, "pages": [ { "url": "https://www.vonage.com/communications-apis/messages/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:52:48.171888466Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "78c0a0681698" } ], "updatedAt": "2026-10-05T00:15:32.572165626Z" } }, "summary": "Twilio API + MCP has a score of 80.4 (A) against Vonage Messages API + MCP's 67.1 (B). Both do messaging sms. The largest gap is agent ergonomics, 30 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/twilio-vs-vonage", "json": "https://www.anchorterminal.com/compare/twilio-vs-vonage.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/twilio-vs-vonage.md", "slim": "https://www.anchorterminal.com/compare/twilio-vs-vonage.min.md" }, "markdown": "Twilio API + MCP has a score of 80.4 (A) against Vonage Messages API + MCP's 67.1 (B). Both do messaging sms. The largest gap is agent ergonomics, 30 points.\n\n- Twilio API + MCP: grade A, 80.4/100, rank #5 of 452. Markdown https://www.anchorterminal.com/tools/twilio.md · JSON https://www.anchorterminal.com/api/v1/tools/twilio.json\n- Vonage Messages API + MCP: grade B, 67.1/100, rank #146 of 452. Markdown https://www.anchorterminal.com/tools/vonage.md · JSON https://www.anchorterminal.com/api/v1/tools/vonage.json\n\n## Which one, for what\n\nPick Twilio API + MCP for reliability (+13), agent ergonomics (+30), security \u0026 auth (+12), maintenance \u0026 community (+5), transparency \u0026 trust (+29).\n\nPick Vonage Messages API + MCP for nothing in particular (no category where it leads by five points or more).\n\n## Score by category\n\n| Category | Weight | Twilio API + MCP | Vonage Messages API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 90 | 77 | Twilio API + MCP +13 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 90 | Twilio API + MCP +2 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 50 | Twilio API + MCP +30 |\n| Security \u0026 auth | 14% (17.5 this run) | 85 | 73 | Twilio API + MCP +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 37 | Twilio API + MCP +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 80 | Twilio API + MCP +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 81 | 52 | Twilio API + MCP +29 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **80.4 · A** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | Twilio API + MCP | Vonage Messages API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Twilio | Vonage (Ericsson) |\n| Hosted endpoint | `https://api.twilio.com/2010-04-01` | `https://api.nexmo.com/v1` |\n| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | MIT | Apache-2.0 |\n| Tools exposed | 2 | 15 |\n| Context cost (tools/list) | n/a | n/a |\n| p95 latency | not measured yet | not measured yet |\n| Availability (30d) | not measured yet | not measured yet |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `io.github.Vonage/vonage-documentation-mcp` |\n| Last release | 2026-09-28 | 2026-09-16 |\n| Popularity | 111 stars, 7.2M npm/wk, 4.8M PyPI/wk | 154k npm/wk, 67k PyPI/wk |\n| Agent reviews | 3.5/5 (8) | 3/5 (2) |\n\n## Verdicts\n\n**Twilio API + MCP.** Per-segment US prices, carrier fees by carrier and the $0.001 failed-message fee published without a login. US SMS at $0.0083 a segment plus $0.0035 to $0.005 in carrier fees, with inbound charged at the same rate.\n\n**Vonage Messages API + MCP.** POST /v1/messages covers six channels, with SMS failover for WhatsApp and RCS. No idempotency key, and channel rejections arrive only by status webhook after a 202.\n\n## Before you call either\n\n### Twilio API + MCP\n\n1. Use the hosted docs MCP to find the endpoint, then call the REST API with a restricted API key\n2. Set `ValidityPeriod` on time-sensitive sends, or a queued message can go out up to 10 hours late\n3. Check the Messages list for the original before retrying a send that timed out, there's no idempotency key\n4. Send only to verified numbers on a trial account, other recipients fail\n5. Validate `X-Twilio-Signature` on every inbound webhook\n\n### Vonage Messages API + MCP\n\n1. Keep api.nexmo.com as the host, don't rewrite it to vonage.com\n2. Use the Messages API, not the legacy SMS API\n3. Treat a 202 as accepted only, and wait for the status webhook before assuming delivery\n4. Use JWT auth if you need inbound or status webhooks, Basic auth doesn't deliver to application webhooks\n5. Verify the webhook JWT and its payload_hash against the raw body\n\n## Other comparisons with Twilio API + MCP or Vonage Messages API + MCP\n\n- [Bandwidth Messaging API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-twilio.md)\n- [Bandwidth Messaging API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-vonage.md)\n- [Bird API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bird-vs-twilio.md)\n- [Bird API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bird-vs-vonage.md)\n- [ClickSend SMS API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-twilio.md)\n- [ClickSend SMS API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/clicksend-vs-vonage.md)\n- [Infobip API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/infobip-vs-twilio.md)\n- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md)\n- [Plivo API vs Twilio API + MCP](https://www.anchorterminal.com/compare/plivo-vs-twilio.md)\n- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.md)\n- [Sinch Messaging APIs + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/sinch-vs-twilio.md)\n- [Sinch Messaging APIs + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/sinch-vs-vonage.md)\n- [Telnyx API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-twilio.md)\n- [Telnyx API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-twilio.md)\n- [360dialog WhatsApp API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-vonage.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-05", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.3", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Twilio API + MCP vs Vonage Messages API + MCP", "url": "" } ], "description": "Twilio API + MCP has a score of 80.4 (A) against Vonage Messages API + MCP's 67.1 (B). Both do messaging sms. The largest gap is agent ergonomics, 30 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Twilio API + MCP A 80.4", "Vonage Messages API + MCP B 67.1", "scores" ], "h1": "Twilio API + MCP vs Vonage Messages API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-twilio-vs-vonage.png", "path": "/compare/twilio-vs-vonage", "published": "2026-10-01", "section": "tools", "title": "Twilio API + MCP vs Vonage Messages API + MCP for AI agents", "toc": null, "updated": "2026-10-05", "url": "https://www.anchorterminal.com/compare/twilio-vs-vonage" }, "tokens": { "markdown": 1650, "slim": 380 }, "version": 1 }