Voxplo — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Outbound AI calls through Voxplo

What we know

Place and manage outbound phone calls with resulting transcripts and structured summaries. Give AI agents a phone: outbound AI calls that return a summary, transcript, and extracted fields.

Maintenance / activity evidence

115 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data. Reported action classes: Retrieve call results. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Sensitive access: Account or infrastructure data accessible with supplied credentials

Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 115 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package voxplo-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have voxplo-mcp permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.

Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Reviewed write actions: Retrieve call results
Sensitive access: Account or infrastructure data accessible with supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
runtime_installer_exact
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

115 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/voxplo-mcp

Exact implementation source: https://www.npmjs.com/package/voxplo-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:voxplo-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
voxplo-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npx -y voxplo-mcp
Configure / authenticate
MCP100 setup guide
Hosted endpoint https://mcp.voxplo.ai/mcp with OAuth; local stdio uses VOXPLO_API_KEY. Calling a phone number is a real paid external action.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Environment settings: VOXPLO_API_KEY
Check connection
Suggested check
Use read-only get_call/list_calls for account status; do not place real phone call for smoke test.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `voxplo-mcp` in Claude Code, remove its exact client entry with `claude mcp remove voxplo-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove voxplo-mcp

Official Documentation & Sources

What it does

Place and manage outbound phone calls with resulting transcripts and structured summaries. Give AI agents a phone: outbound AI calls that return a summary, transcript, and extracted fields.

Capability: Communication
Resource type: MCP Server
Best fit: Outbound AI calls through Voxplo

Representative uses

Place an appointment call
Retrieve call results

Limitations

Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.
Data handling: Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.
Cost: Not verified; check vendor terms
Risk and cautions: Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.

Access scope and cautions

Write actions: Not verified Retrieve call results
Sensitive access: Account or infrastructure data accessible with supplied credentials
Risk level: high
Security notes: Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Place an appointment call; Retrieve call results.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Retrieve call results. Recorded permission context: Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data.

What data-handling boundary should I consider?

Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data. Recorded sensitive-access context: Account or infrastructure data accessible with supplied credentials.

What limitations and risks should I check before use?

Real-world calling requires consent and anti-spam/telephony compliance; transcripts may contain personal data. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.