{ "data": { "a": { "slug": "sinch", "name": "Sinch Messaging APIs + MCP", "vendor": "Sinch", "vendorUrl": "https://sinch.com", "kind": "http-api", "category": "messaging", "summary": "The SMS REST API and the Conversation API, which sends SMS, RCS, WhatsApp, Viber and Messenger through one message format, plus the Verification API.", "url": "https://www.anchorterminal.com/tools/sinch", "markdownUrl": "https://www.anchorterminal.com/tools/sinch.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sinch.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sinch.json", "repo": "https://github.com/sinch/sinch-mcp-server", "license": "Apache-2.0", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://us.sms.api.sinch.com/xms/v1", "packages": [ { "registry": "npm", "name": "@sinch/sdk-core" }, { "registry": "pypi", "name": "sinch" }, { "registry": "npm", "name": "@sinch/mcp" } ], "auth": "mixed", "authNotes": "The SMS API takes a service-plan Bearer token. Conversation, Numbers and Templates use OAuth 2.0 client credentials from a project access key (Basic auth also accepted). Verification and Voice use an application key and secret. The MCP server's HTTP mode does no inbound auth in single-tenant mode.", "pricing": "usage", "pricingNotes": "Pay as you go. US SMS $0.0078 a message on 10DLC or toll-free and $0.009 on short code, same rate inbound, plus carrier fees. Other countries and WhatsApp are priced through a country selector. Trial accounts get 2 units of local currency (for example $2) and a test number, no card (https://sinch.com/pricing/sms/).", "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": 54, "popularity": { "githubStars": 1, "npmWeekly": 15648, "pypiWeekly": 11166, "asOf": "2026-09-30" }, "docsUrl": "https://developers.sinch.com/docs/conversation", "llmsTxt": "https://developers.sinch.com/llms.txt", "openapi": "https://developers.sinch.com/_bundle/docs/conversation/api-reference/conversation.yaml", "capabilities": [ "messaging.sms", "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-23", "graded": true, "anchor": { "graded": true, "score": 63.3, "grade": "B", "agentReady": false, "rank": 206, "ranked": true, "rankOf": 452, "categoryRank": 6, "methodology": "0.3", "run": "2026-10-01", "scores": { "ergonomics": 50, "maintenance": 83, "payments": 40, "reliability": 73, "schema": 81, "security": 50, "transparency": 73 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format. The MCP server is a developer preview whose npm release dates from 2026-04-14.", "strengths": [ "The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format", "Published limits of 800 requests a second per project and a 500,000-message queue per app", "HMAC-signed callbacks with a nonce and timestamp", "Trial with 2 units of local currency and a test number, no card", "SDK releases in Java and Python in September 2026" ], "weaknesses": [ "The MCP server is a developer preview whose npm release dates from 2026-04-14", "54 MCP tools with no readOnlyHint or destructiveHint annotations", "Separate credential schemes for the SMS, Conversation and Verification APIs, none with scopes", "No SLA, and no Retry-After on 429", "No security.txt or bug bounty found" ], "agentNotes": [ "Load the MCP with `--tags` for the channels you need, or all 54 tools land in context", "Keep a single-tenant HTTP MCP bound to localhost, it does no inbound authentication", "Expect sends to drain at 20 messages a second per app unless Sinch raises it", "Verify `x-sinch-webhook-signature` against the raw body before parsing the JSON", "Use the regional base URL (us, eu or br) that matches the project" ], "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": 63.3 } ], "editorialScores": { "ergonomics": 50, "maintenance": 83, "payments": 40, "reliability": 73, "schema": 81, "security": 50, "transparency": 55 }, "provenanceScore": 90 }, "connect": { "http": "curl -X POST \"https://us.sms.api.sinch.com/xms/v1/$SINCH_SERVICE_PLAN_ID/batches\" \\\n -H \"Authorization: Bearer $SINCH_API_TOKEN\" -H \"Content-Type: application/json\" \\\n -d '{\"from\":\"+12025550123\",\"to\":[\"+15551234567\"],\"body\":\"Hello from Sinch\"}'", "config": { "mcpServers": { "sinch": { "args": [ "-y", "@sinch/mcp" ], "command": "npx", "env": { "CONVERSATION_APP_ID": "${SINCH_CONVERSATION_APP_ID}", "CONVERSATION_REGION": "us", "KEY_ID": "${SINCH_KEY_ID}", "KEY_SECRET": "${SINCH_KEY_SECRET}", "PROJECT_ID": "${SINCH_PROJECT_ID}" } } } } }, "letme": { "capability": "https://letme.dev/messaging.sms", "tool": "https://letme.dev/sinch" }, "sameCompany": [ "sinch-voice" ], "area": "communication", "unitPrices": [ { "item": "SMS outbound, US 10DLC or toll-free", "unit": "message", "usd": 0.0078, "note": "plus carrier fees" }, { "item": "SMS outbound, US short code", "unit": "message", "usd": 0.009, "note": "plus carrier fees" } ], "provenance": { "legalEntity": "Sinch AB (publ)", "domain": "sinch.com", "domainRegistered": "1997-12-03", "endpointOnVendorDomain": true, "terms": "https://sinch.com/legal/terms-and-conditions/other-sinch-terms-conditions/general-terms-and-conditions/", "privacy": "https://sinch.com/legal/privacy-notice/", "statusPage": "https://status.sinch.com", "changelog": "https://developers.sinch.com/docs/conversation/release-notes", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The general terms name the contracting Sinch entity only in the order form or master agreement. Sinch AB (publ) is the listed parent." ], "score": 90 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sinch.json", "live": { "slug": "sinch", "probe": { "target": "https://us.sms.api.sinch.com/xms/v1", "method": "get", "lastAt": "2026-10-04T23:32:54.398878577Z", "lastOk": true, "lastStatus": 401, "lastMs": 247, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 250, "p95ms24h": 287, "samples24h": 272, "samples30d": 1097, "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": 267, "ok": 267 } ] }, "vendorStatus": { "page": "https://status.sinch.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-04T23:28:02.545757715Z" }, "versions": [ { "registry": "github", "name": "sinch/sinch-mcp-server", "version": "v0.0.1-alpha6", "released": "2026-04-14", "seenAt": "2026-10-04T16:40:04.435716963Z" }, { "registry": "npm", "name": "@sinch/mcp", "version": "0.0.1-alpha.6", "seenAt": "2026-10-04T16:40:02.692338984Z" }, { "registry": "npm", "name": "@sinch/sdk-core", "version": "1.6.0", "seenAt": "2026-10-04T16:40:02.237951249Z" }, { "registry": "pypi", "name": "sinch", "version": "2.2.0", "released": "2026-09-21", "seenAt": "2026-10-04T16:40:02.585087516Z" } ], "githubStars": 1, "npmWeekly": 18032, "pypiWeekly": 12911, "securityTxt": { "url": "https://sinch.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-04T15:15:40.047440487Z" }, "llmsTxt": { "url": "https://developers.sinch.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-04T15:18:15.885568819Z" }, "domain": { "domain": "sinch.com", "registered": "1997-12-03", "source": "https://rdap.verisign.com/com/v1/domain/sinch.com", "checkedAt": "2026-10-04T13:05:54.744606475Z" }, "pages": [ { "url": "https://developers.sinch.com/docs/conversation/release-notes", "kind": "changelog", "status": 200, "checkedAt": "2026-10-04T15:43:02.860196611Z", "changedAt": "2026-10-04T15:43:02.860196611Z", "fingerprint": "3bd59d113afa" }, { "url": "https://sinch.com/pricing/sms/", "kind": "pricing", "status": 304, "checkedAt": "2026-10-04T15:47:52.856561614Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4d9f998b696c" } ], "updatedAt": "2026-10-04T23:32:54.398878577Z" } }, "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-04T23:32:56.650393129Z", "lastOk": true, "lastStatus": 404, "lastMs": 21, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 24, "p95ms24h": 58, "samples24h": 272, "samples30d": 1097, "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": 267, "ok": 267 } ] }, "vendorStatus": { "page": "https://vonageapi.statuspage.io", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-04T23:28:04.982506703Z" }, "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-03T23:29:28.630222764Z" }, { "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-04T23:32:56.650393129Z" } }, "summary": "Vonage Messages API + MCP has a score of 67.1 (B) against Sinch Messaging APIs + MCP's 63.3 (B). Both do messaging sms. The largest gap is security \u0026 auth, 23 points." }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/sinch-vs-vonage", "json": "https://www.anchorterminal.com/compare/sinch-vs-vonage.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/sinch-vs-vonage.md", "slim": "https://www.anchorterminal.com/compare/sinch-vs-vonage.min.md" }, "markdown": "Vonage Messages API + MCP has a score of 67.1 (B) against Sinch Messaging APIs + MCP's 63.3 (B). Both do messaging sms. The largest gap is security \u0026 auth, 23 points.\n\n- Sinch Messaging APIs + MCP: grade B, 63.3/100, rank #206 of 452. Markdown https://www.anchorterminal.com/tools/sinch.md · JSON https://www.anchorterminal.com/api/v1/tools/sinch.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 Sinch Messaging APIs + MCP for transparency \u0026 trust (+21).\n\nPick Vonage Messages API + MCP for schema \u0026 documentation (+9), security \u0026 auth (+23).\n\n## Score by category\n\n| Category | Weight | Sinch Messaging APIs + MCP | Vonage Messages API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 77 | Vonage Messages API + MCP +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 81 | 90 | Vonage Messages API + MCP +9 |\n| Agent ergonomics | 13% (16.2 this run) | 50 | 50 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 50 | 73 | Vonage Messages API + MCP +23 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 37 | Sinch Messaging APIs + MCP +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 80 | Sinch Messaging APIs + MCP +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 52 | Sinch Messaging APIs + MCP +21 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **63.3 · B** | **67.1 · B** | |\n\n## Facts side by side\n\n| Fact | Sinch Messaging APIs + MCP | Vonage Messages API + MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Sinch | Vonage (Ericsson) |\n| Hosted endpoint | `https://us.sms.api.sinch.com/xms/v1` | `https://api.nexmo.com/v1` |\n| Transports | HTTP, stdio, Streamable HTTP | 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 | Apache-2.0 | Apache-2.0 |\n| Tools exposed | 54 | 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-23 | 2026-09-16 |\n| Popularity | 1 stars, 16k npm/wk, 11k PyPI/wk | 154k npm/wk, 67k PyPI/wk |\n| Agent reviews | 3/5 (2) | 3/5 (2) |\n\n## Verdicts\n\n**Sinch Messaging APIs + MCP.** The Conversation API covers SMS, RCS, WhatsApp, Viber and Messenger through one message format. The MCP server is a developer preview whose npm release dates from 2026-04-14.\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### Sinch Messaging APIs + MCP\n\n1. Load the MCP with `--tags` for the channels you need, or all 54 tools land in context\n2. Keep a single-tenant HTTP MCP bound to localhost, it does no inbound authentication\n3. Expect sends to drain at 20 messages a second per app unless Sinch raises it\n4. Verify `x-sinch-webhook-signature` against the raw body before parsing the JSON\n5. Use the regional base URL (us, eu or br) that matches the project\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 Sinch Messaging APIs + MCP or Vonage Messages API + MCP\n\n- [Bandwidth Messaging API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-sinch.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 Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/bird-vs-sinch.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 Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/clicksend-vs-sinch.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 Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/infobip-vs-sinch.md)\n- [Infobip API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/infobip-vs-vonage.md)\n- [Plivo API vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/plivo-vs-sinch.md)\n- [Plivo API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/plivo-vs-vonage.md)\n- [Sinch Messaging APIs + MCP vs Telnyx API + MCP](https://www.anchorterminal.com/compare/sinch-vs-telnyx.md)\n- [Sinch Messaging APIs + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/sinch-vs-twilio.md)\n- [Telnyx API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telnyx-vs-vonage.md)\n- [Twilio API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/twilio-vs-vonage.md)\n- [360dialog WhatsApp API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/360dialog-vs-sinch.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-04", "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": "Sinch Messaging APIs + MCP vs Vonage Messages API + MCP", "url": "" } ], "description": "Vonage Messages API + MCP has a score of 67.1 (B) against Sinch Messaging APIs + MCP's 63.3 (B). Both do messaging sms. The largest gap is security \u0026 auth, 23 points. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Sinch Messaging APIs + MCP B 63.3", "Vonage Messages API + MCP B 67.1", "scores" ], "h1": "Sinch Messaging APIs + MCP vs Vonage Messages API + MCP", "image": "https://www.anchorterminal.com/assets/og/compare-sinch-vs-vonage.png", "path": "/compare/sinch-vs-vonage", "published": "2026-10-01", "section": "tools", "title": "Sinch Messaging APIs + MCP vs Vonage Messages API + MCP for AI agents", "toc": null, "updated": "2026-10-04", "url": "https://www.anchorterminal.com/compare/sinch-vs-vonage" }, "tokens": { "markdown": 1650, "slim": 330 }, "version": 1 }