CallMCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Driver-neutral CallMCP telephony server core: Does the fourteen-tool contract remain compatible across drivers without borrowing provider-specific telephony guarantees?

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

Best fit

Provider-independent outbound/inbound telephony, SMS, recordings, transcripts and phone-number lifecycle under one MCP contract.

What we know

Universal telephony MCP runtime with interchangeable hosted, local/self-hosted and BYOK drivers. Tool presence is capability-gated by the configured driver; the normative contract keeps schemas/error shapes stable across providers.

Maintenance / activity evidence

@callmcp/server 0.1.5 published 2026-07-10T21:59:56.081Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Telephony/SMS/number authority according to selected driver. Writes: Place calls; Send SMS; Manage phone numbers; Potentially start/stop recordings.
Driver/provider credentials.
Sensitive access: Phone numbers, Call audio/transcripts, SMS content, Provider credentials

Can contact real people and incur charges; driver capabilities and approval controls must be reviewed.

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

All limitations / Review context

Does the fourteen-tool contract remain compatible across drivers without borrowing provider-specific telephony guarantees?

The bounded review of the publisher's documented Driver-neutral CallMCP telephony server core and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Can contact real people and incur charges; driver capabilities and approval controls must be reviewed.
Telephony/SMS/number authority according to selected driver.
Driver/provider credentials.
Call/SMS audio/transcript/phone data flows through selected provider stack.
Reviewed write actions: Place calls; Send SMS; Manage phone numbers; Potentially start/stop recordings
Sensitive access: Phone numbers, Call audio/transcripts, SMS content, Provider credentials
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Real drivers can contact people and incur telephony/provider costs.
Available tools differ by driver capability.
No driver configured means the server fails closed; sandbox mock is explicit only.
BYOK mode can combine Twilio transport and realtime-model credentials.

Original activity observations

@callmcp/server 0.1.5 published 2026-07-10T21:59:56.081Z

Technical identity

npm/@callmcp/server

Exact implementation source: https://www.npmjs.com/package/@callmcp/server ↗
Reviewed resource type: Gateway
Repository identity: CallMCP/callmcp
Package identity: npm:@callmcp/server

Evidence & Sources

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

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@callmcp/server
Recorded package identity, distribution or download evidence.
GitHub repository ↗
callmcp/callmcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Config-driven telephony orchestration MCP. `npx @callmcp/server` starts stdio; `--sandbox` is an explicit local sandbox; doctor is read-only. Provider driver config is prerequisite.
publisher install or stdio launch · Publisher instructions
npx @callmcp/server doctor
Configure / authenticate
MCP100 setup guide
Publisher: `npx @callmcp/server` starts stdio; run `npx @callmcp/server doctor` for read-only preflight. HTTP route: `npx @callmcp/server --http --port 8787`.
Check connection
Suggested check
Use `npx @callmcp/server doctor` or explicit `--sandbox`; do not call paid provider routes in smoke checks.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `callmcp-server`, run `claude mcp remove callmcp-server`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove callmcp-server

Official Documentation & Sources

What it does

Universal telephony MCP runtime with interchangeable hosted, local/self-hosted and BYOK drivers. Tool presence is capability-gated by the configured driver; the normative contract keeps schemas/error shapes stable across providers.

Capability: Communication
Resource type: Gateway
Industry: Telecommunications
Best fit: Provider-independent outbound/inbound telephony, SMS, recordings, transcripts and phone-number lifecycle under one MCP contract.

Representative uses

Place/manage calls
Send/receive SMS where driver supports it
Read recordings/transcripts
Manage phone-number lifecycle
Use local sandbox/mock for safe testing

Limitations

Real drivers can contact people and incur telephony/provider costs.
Available tools differ by driver capability.
No driver configured means the server fails closed; sandbox mock is explicit only.
BYOK mode can combine Twilio transport and realtime-model credentials.

Reviewed access

Access & risk

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

Authentication: Driver/provider credentials.
Permissions: Telephony/SMS/number authority according to selected driver.
Data handling: Call/SMS audio/transcript/phone data flows through selected provider stack.
Cost: provider_dependent
Risk and cautions: Can contact real people and incur charges; driver capabilities and approval controls must be reviewed.

Access scope and cautions

Write actions: Place calls Send SMS Manage phone numbers Potentially start/stop recordings
Sensitive access: Phone numbers Call audio/transcripts SMS content Provider credentials
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Place/manage calls; Send/receive SMS where driver supports it; Read recordings/transcripts; Manage phone-number lifecycle; Use local sandbox/mock for safe testing.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @callmcp/server. Recorded transport: stdio, driver_dependent_http. Recorded environment-variable notes: driver-specific vars. No configuration values are supplied here. Prerequisites: MCP client; configured CallMCP driver. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Driver-dependent: hosted KaiCalls, self-hosted Dograh, or BYOK credentials.

Can it modify data or perform write operations?

Documented write actions include: Place calls; Send SMS; Manage phone numbers; Potentially start/stop recordings. Recorded permission boundary: Telephony/SMS/number authority according to selected driver.

What data-handling boundary should I consider?

Call/SMS audio/transcript/phone data flows through selected provider stack. Recorded sensitive-access context: Phone numbers; Call audio/transcripts; SMS content; Provider credentials.

What limitations and risks should I check before use?

Can contact real people and incur charges; driver capabilities and approval controls must be reviewed. Real drivers can contact people and incur telephony/provider costs. Available tools differ by driver capability. No driver configured means the server fails closed; sandbox mock is explicit only. BYOK mode can combine Twilio transport and realtime-model credentials. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.