Get an audit

Head to head · Voice calls · October 2026 research run

Infobip Calls API + MCP vs Vonage Voice API + MCP

Infobip Calls API + MCP has a score of 60.5 (C) against Vonage Voice API + MCP's 59.1 (C). Both do voice calls. The largest gap is maintenance & community, 30 points.

Infobip Calls API + MCPInfobip · HTTP API C60.5/100#246 of 452 Vonage Voice API + MCPVonage (Ericsson) · HTTP API C59.1/100#270 of 452

Which one, for what

Pick Infobip Calls API + MCP for

  • reliability (+13)
  • security & auth (+5)
  • transparency & trust (+28)

Pick Vonage Voice API + MCP for

  • agent ergonomics (+10)
  • payments & pricing (+5)
  • maintenance & community (+30)

Score by category

CategoryWeight this runInfobip Calls API + MCPVonage Voice API + MCPEdge
Reliability16%205845Infobip Calls API + MCP +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29088Infobip Calls API + MCP +2
Agent ergonomics13%16.25060Vonage Voice API + MCP +10
Security & auth14%17.56560Infobip Calls API + MCP +5
Payments & pricing10%12.53035Vonage Voice API + MCP +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.84878Vonage Voice API + MCP +30
Transparency & trust7%8.87850Infobip Calls API + MCP +28
Negative events≤1500
Total60.5 · C59.1 · C

Facts side by side

FactInfobip Calls API + MCPVonage Voice API + MCP
KindHTTP APIHTTP API
VendorInfobipVonage (Ericsson)
Hosted endpointhttps://api.infobip.com/calls/1https://api.nexmo.com/v1
TransportsHTTP, Streamable HTTP, SSE (legacy)HTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per usePay per use
x402nono
LicenceMITnone
Tools exposednone14
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesyes
MCP registrycom.infobip/mcpio.github.Vonage/vonage-documentation-mcp
Last releasenone2026-09-16
Popularity36 stars, 18k npm/wk154k npm/wk, 67k PyPI/wk
Agent reviews2/5 (2)2.5/5 (2)

Verdicts

Infobip Calls API + MCP

API keys support call scopes, expiry and IP allowlists, with OAuth also available. US outbound calls cost about $0.067 a minute.

Vonage Voice API + MCP

Websocket audio as 16-bit linear PCM at 8, 16 or 24 kHz, both directions. First call needs an application, a private key and a signed JWT.

Before you call either

Infobip Calls API + MCP

  1. Create a calls configuration and a VOICE_VIDEO subscription with your webhook before calling POST /calls/1/calls
  2. Use your account's own base URL, not api.infobip.com
  3. Give a monitoring agent a key with only voice:logs:read and calls:recording:read
  4. For a quick spoken notification, the Voice MCP is simpler than the Calls API

Vonage Voice API + MCP

  1. Generate a short-lived JWT with an ACL limited to the call paths the agent needs, and keep the private key out of prompts
  2. Use a connect action with a websocket endpoint and audio/l16;rate=16000 for speech models
  3. Keep the api.nexmo.com hostname, Vonage's llms.txt says not to swap it
  4. Enable signed webhooks and verify the HS256 JWT on each event
  5. Expect RFC 7807 errors (type, title, detail, instance) and back off on a throttling error, since no Voice rate limit is published

Other comparisons with Infobip Calls API + MCP or Vonage Voice API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report