ai.callmcp/server
NPM · @CALLMCP/SERVER · SCANNED SEP 20
One MCP tool contract for telephony — any call provider, hosted, local, or BYOK.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 71 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1004 tokens (~71/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 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
How do I install the ai.callmcp/server MCP server?
ai.callmcp/server runs locally as an npm package, launched with npx -y @callmcp/server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @callmcp/server
claude mcp add ai-callmcp-server -- npx -y @callmcp/server
{
"mcpServers": {
"ai-callmcp-server": {
"command": "npx",
"args": [
"-y",
"@callmcp/server"
]
}
}
} {
"servers": {
"ai-callmcp-server": {
"command": "npx",
"args": [
"-y",
"@callmcp/server"
]
}
}
} codex mcp add ai-callmcp-server -- npx -y @callmcp/server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-callmcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@callmcp/server"
],
"enabled": true
}
}
} openclaw mcp add ai-callmcp-server --command npx --arg -y --arg @callmcp/server
mcp_servers:
ai-callmcp-server:
command: "npx"
args: ["-y", "@callmcp/server"] {
"McpServers": {
"ai-callmcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@callmcp/server"
]
}
}
} assistant mcp add ai-callmcp-server -t stdio -c npx -a -y @callmcp/server
{
"mcpServers": {
"ai-callmcp-server": {
"command": "npx",
"args": [
"-y",
"@callmcp/server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 · Analysed npm/@callmcp/server@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
buy_number ~83
Purchases a phone number (SPEC §1.11). Spends money but does not contact a third party, so no human approval gate.
| Name | Type | Req | Description |
|---|---|---|---|
| compliance | object | – | – |
| driver | string | – | – |
| number | string | yes | a number returned by search_numbers |
| options | object | – | namespaced driver-specific passthrough, keyed by driver_id |
No output schema declared.
No examples provided.
configure_number ~88
Updates routing/configuration for an already-owned number (SPEC §1.12).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_config_ref | string|null | – | – |
| caller_id_name | string|null | – | – |
| driver | string | – | – |
| number | string | yes | – |
| options | object | – | namespaced driver-specific passthrough, keyed by driver_id |
| sms_webhook_url | string|null | – | – |
No output schema declared.
No examples provided.
end_call ~45
Terminates an in-progress call (SPEC §1.5). Capability-gated by supports_hangup.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
get_call_status ~36
Read-only poll fallback for clients that don't subscribe to resource updates (SPEC §1.6).
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | – |
No output schema declared.
No examples provided.
get_recording ~42
Returns a resource link to the call's audio recording (SPEC §1.8). Capability-gated by supports_recording.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | – |
No output schema declared.
No examples provided.
get_transcript ~45
Returns a call's transcript, inline or as a subscribable resource link (SPEC §1.7).
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | – |
| format | string | – | – |
No output schema declared.
No examples provided.
list_approvals ~60
Read-only. Returns pending approvals, allowlist entries, and active campaign grants (SPEC §1.3).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| driver | string | – | – |
| scope | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
list_calls ~56
Read-only call history/inventory (SPEC §1.14).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| driver | string | – | – |
| since | string | – | – |
| status | string | – | – |
| until | string | – | – |
No output schema declared.
No examples provided.
list_drivers ~30
Read-only capability introspection. Call before assuming any other tool's behavior (SPEC §1.1).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_numbers ~35
Read-only inventory of owned numbers (SPEC §1.13).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| driver | string | – | – |
No output schema declared.
No examples provided.
make_call ~159
Places an outbound call (SPEC §1.4). Requires a valid, unexpired approval_id or an allowlist match; otherwise the server elicits approval inline rather than dialing.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_config_ref | string | – | opaque reference to an already-configured agent/assistant |
| approval_id | string | – | omit only if `to` matches a standing allowlist entry |
| driver | string | – | – |
| from | string | – | E.164 caller-id number; if omitted, driver default number is used |
| max_duration_seconds | integer | – | – |
| metadata | object | – | – |
| options | object | – | namespaced driver-specific passthrough, keyed by driver_id |
| to | string | yes | E.164 destination number |
No output schema declared.
No examples provided.
request_call_approval ~146
Creates a pending human authorization for a destination, allowlist entry, or campaign batch (SPEC §1.2). Fires MCP elicitation when supported; otherwise returns an out-of-band approval URL.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_max_contacts | integer | – | required when scope=campaign_batch |
| channel | string | – | – |
| destinations | array | yes | – |
| driver | string | – | – |
| options | object | – | namespaced driver-specific passthrough, keyed by driver_id |
| purpose | string | – | human-readable reason shown in the elicitation/approval UI |
| scope | string | yes | – |
| ttl_seconds | integer | – | see SPEC §3.2 for tier defaults |
No output schema declared.
No examples provided.
search_numbers ~70
Read-only search for purchasable phone numbers (SPEC §1.10).
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | string | – | – |
| capabilities_required | array | – | – |
| country | string | yes | ISO 3166-1 alpha-2 |
| cursor | string | – | – |
| driver | string | – | – |
No output schema declared.
No examples provided.
send_sms ~109
Sends an outbound message over SMS, WhatsApp, or RCS (SPEC §1.9). Capability-gated; approval-gated like make_call.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_id | string | – | – |
| body | string | yes | – |
| channel | string | – | – |
| driver | string | – | – |
| from | string | – | – |
| media_urls | array | – | – |
| options | object | – | namespaced driver-specific passthrough, keyed by driver_id |
| to | string | yes | – |
No output schema declared.
No examples provided.
What is the ai.callmcp/server MCP server?
ai.callmcp/server is an MCP server listed in the public MCP registry as ai.callmcp/server. One MCP tool contract for telephony, any call provider, hosted, local, or BYOK. This page covers its npm package (@callmcp/server).
Is the ai.callmcp/server MCP server safe to use?
ai.callmcp/server scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 ai.callmcp/server MCP server expose?
ai.callmcp/server exposes 14 tools: list_drivers, request_call_approval, list_approvals, make_call, end_call, and 9 more. Their descriptions and schemas cost roughly 1,004 tokens of context every time the server is loaded.
Is the ai.callmcp/server MCP server still maintained?
ai.callmcp/server 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.
What licence is the ai.callmcp/server MCP server under?
ai.callmcp/server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.