Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Voxplo

REMOTE · MCP.VOXPLO.AI · 2 COMPONENTS · SCANNED SEP 20

Give AI agents a phone: outbound AI calls that return a summary, transcript, and extracted fields.

+45 this week 81 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 850 tokens (~85/item across 10 items; 4 tools + 6 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Voxplo MCP server?

Voxplo is a hosted endpoint at https://mcp.voxplo.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.voxplo.ai

# add to Claude Code
claude mcp add --transport http ai-voxplo-voxplo 'https://mcp.voxplo.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-voxplo-voxplo": {
      "url": "https://mcp.voxplo.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-voxplo-voxplo": {
      "type": "http",
      "url": "https://mcp.voxplo.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-voxplo-voxplo]
url = "https://mcp.voxplo.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-voxplo-voxplo": {
      "type": "remote",
      "url": "https://mcp.voxplo.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-voxplo-voxplo --url 'https://mcp.voxplo.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-voxplo-voxplo:
    url: "https://mcp.voxplo.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-voxplo-voxplo": {
      "Transport": "http",
      "Url": "https://mcp.voxplo.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-voxplo-voxplo -t streamable-http -u 'https://mcp.voxplo.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-voxplo-voxplo": {
      "type": "http",
      "url": "https://mcp.voxplo.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 15 Sept 26 +43
    • Transport: unverified → pass security
    • Injection markers: unverified → pass security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → 100 functional
    • Tool coverage: unverified → 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://mcp.voxplo.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=voxplo.ai CN=WE1,O=Google Trust Services,C=US 25 Aug 2026 23 Nov 2026 ECDSA 256 ECDSA-SHA256 df2b58299ee8456e130f85a840885a45
SANs: voxplo.ai, *.voxplo.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.voxplo.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
voxplo.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.voxplo.ai/.well-known/oauth-protected-resource/mcp"

Bearer error="invalid_token", error_description="Missing Authorization header", resource_metadata="https://mcp.voxplo.ai/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://mcp.voxplo.ai/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://mcp.voxplo.ai/mcp
Authorisation server https://mcp.voxplo.ai/

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.voxplo.ai/mcp Verified 200
http (plaintext) http://mcp.voxplo.ai/mcp HTTPS enforced 308 https://mcp.voxplo.ai/mcp
MCP tools · 4 exposed · ~671 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_call ~74

Get the status and result of a call by id. status is one of queued | ringing | in_progress (still running, poll again) or completed | no_answer | voicemail | declined | failed (terminal). Returns summary, transcript, and extracted fields.

NameTypeReqDescription
callIdstringyesThe callId returned by place_call.

No output schema declared.

No examples provided.

list_calls ~39

List recent calls placed by your account (most recent first).

NameTypeReqDescription
limitintegerMax calls to return (default 20, max 100).

No output schema declared.

No examples provided.

place_call ~313

Place an outbound AI phone call toward an objective. Returns a callId immediately; the call is conducted asynchronously. Poll get_call with that callId until status is terminal (completed | no_answer | voicemail | declined | failed).

NameTypeReqDescription
accountNumberstringAccount/phone digits the enter_account_number tool keys deterministically (keypad chars only).
callbackNumberstringOur callback DID digits the enter_callback_number tool keys (callback-to-AI mode).
callerIdstringOptional caller ID; must be a number on your account.
contextstringBackground context for the assistant.
fieldsarrayStructured fields to extract from the call.
listenFirstbooleanIf true, stay silent until the callee/IVR speaks first, then respond. Recommended for any outbound call into a phone tree.
navModestringHow to navigate the far-end IVR: auto (detect keypad menu vs conversational assistant live), keypad (stay muted and press keys), or speech (talk).
objectivestringyesWhat the call should accomplish.
tostringyesDestination phone number in E.164, e.g. +14155550123.
toolAllowlistarrayTools this call may use, e.g. ["send_digits","reached_human","add_participant","enter_account_number"]. Omit for the default set.
webhookUrlstringOptional https URL to receive the signed result.

No output schema declared.

No examples provided.

set_appointment ~245

Place an outbound AI phone call to set up a meeting. The assistant calls the person, agrees a time, and the result (poll get_call) carries outcome (appointment_set | callback_requested | declined | no_answer | failed) and, when set, the appointment (startISO, timezone, durationMinutes, attendee, subject). Returns a callId immediately.

NameTypeReqDescription
autoBookbooleanAlso book the agreed time on your connected calendar.
callerIdstringOptional caller ID; must be a number on your account.
durationMinutesintegerMeeting length in minutes (default 30).
slotsarraySpecific start times to offer, ISO-8601 with offset.
subjectstringyesWhat the meeting is about.
timePreferencestringNatural-language window, e.g. "weekday mornings next week".
timezonestringIANA timezone for the appointment, e.g. Asia/Jerusalem.
tostringyesWho to call, in E.164, e.g. +14155550123.
webhookUrlstringOptional https URL to receive the signed result.

No output schema declared.

No examples provided.

Common questions

What is the Voxplo MCP server?

Voxplo is an MCP server listed in the public MCP registry as ai.voxplo/voxplo. Give AI agents a phone: outbound AI calls that return a summary, transcript, and extracted fields. This page covers its hosted endpoint (https://mcp.voxplo.ai/mcp).

Is the Voxplo MCP server safe to use?

Voxplo scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Voxplo MCP server expose?

Voxplo exposes 4 tools: place_call, set_appointment, get_call, list_calls. Their descriptions and schemas cost roughly 671 tokens of context every time the server is loaded.

Does the Voxplo MCP server require authentication?

Yes. Voxplo asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Voxplo MCP server still maintained?

Voxplo is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.