io.github.ClawCall-Dev/clawcall
NPM · @CLAWCALL/MCP · SCANNED SEP 22
MCP server for ClawCall — AI-powered US phone calling.
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
- 31 of 96 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 106 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1095 tokens (~109/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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 io.github.ClawCall-Dev/clawcall MCP server?
io.github.ClawCall-Dev/clawcall runs locally as an npm package, launched with npx -y @clawcall/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @clawcall/mcp
claude mcp add clawcall-dev-clawcall -- npx -y @clawcall/mcp
{
"mcpServers": {
"clawcall-dev-clawcall": {
"command": "npx",
"args": [
"-y",
"@clawcall/mcp"
]
}
}
} {
"servers": {
"clawcall-dev-clawcall": {
"command": "npx",
"args": [
"-y",
"@clawcall/mcp"
]
}
}
} codex mcp add clawcall-dev-clawcall -- npx -y @clawcall/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"clawcall-dev-clawcall": {
"type": "local",
"command": [
"npx",
"-y",
"@clawcall/mcp"
],
"enabled": true
}
}
} openclaw mcp add clawcall-dev-clawcall --command npx --arg -y --arg @clawcall/mcp
mcp_servers:
clawcall-dev-clawcall:
command: "npx"
args: ["-y", "@clawcall/mcp"] {
"McpServers": {
"clawcall-dev-clawcall": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@clawcall/mcp"
]
}
}
} assistant mcp add clawcall-dev-clawcall -t stdio -c npx -a -y @clawcall/mcp
{
"mcpServers": {
"clawcall-dev-clawcall": {
"command": "npx",
"args": [
"-y",
"@clawcall/mcp"
]
}
}
} 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.
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 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.
- 19 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.
- 17 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.80 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.
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 22 Sept 2026 · Analysed npm/@clawcall/mcp@0.1.0
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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
get_account_link_url ~56
Build the browser sign-in link to attach this agent's key, calls, balance, and history to a ClawCall account. Reads the saved key; mints nothing. If no key is saved, place a call first.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_balance ~30
Cheap balance/tier status. Do NOT pre-check before every call — just place the call and handle errors.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_call ~133
Poll primitive; context-cheap. Returns lifecycle + a short transcript_tail, NOT the full transcript (use get_call_transcript for that). After placing a call, poll get_call every 3s until lifecycle === 'finalized'. The outcome field is the PHONE-NETWORK result (answered/no_answer/busy/…), NOT task success — read the transcript (get_call_transcript) and judge it against the task yourself. A call that reached voicemail still finalizes as answered or no_answer — detect it from the transcript, not the outcome.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | The call_id returned by place_call |
No output schema declared.
No examples provided.
get_call_transcript ~43
Full turn-by-turn transcript array. Split out so get_call stays cheap for frequent polling.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | The call_id returned by place_call |
No output schema declared.
No examples provided.
get_recording ~54
Durable recording access (no 10-minute window). Returns a URL, never inline audio. A 404 may be a permission denial, not absence.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | The call_id returned by place_call |
No output schema declared.
No examples provided.
hangup_call ~57
Cancel or hang up a call you initiated. Idempotent — already-finalized is a no-op success. Use for mid-call control during your own poll loop.
| Name | Type | Req | Description |
|---|---|---|---|
| call_id | string | yes | The call_id returned by place_call |
No output schema declared.
No examples provided.
list_calls ~87
List call history. Requires account linking (a proto-key with no linked user returns 401 — call get_account_link_url). Inbound history requires a reserved-number plan.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Optional: inbound or outbound |
| limit | integer | – | Max results, default 25, 1-200 |
| since | string | – | Optional ISO 8601 timestamp lower bound |
No output schema declared.
No examples provided.
place_call ~288
Place an outbound US phone call. THE canonical write; non-blocking, returns immediately. After placing a call, poll get_call every 3s until lifecycle === 'finalized'. The outcome field is the PHONE-NETWORK result (answered/no_answer/busy/…), NOT task success — read the transcript (get_call_transcript) and judge it against the task yourself. A call that reached voicemail still finalizes as answered or no_answer — detect it from the transcript, not the outcome. For 3-4 parallel interchangeable info-gathering calls, call place_call directly per number and fan-out get_call. Do NOT use place_call_and_wait for campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| bridge_number | string | – | Optional US E.164; enables mid-call loop_in_user handoff to this number |
| greeting | string | – | Optional outbound opener context. Does NOT set the agent's first spoken line — the opener is hardcoded server-side to a recording disclosure. |
| personality | string | – | Optional reusable style/tone. Do NOT put one-call facts here |
| task | string | yes | Full briefing memo — the agent's ONLY knowledge of the call's purpose and context |
| to | string | yes | US phone number in E.164, +1XXXXXXXXXX |
| voice | string | – | Optional voice: jessica (default), sarah, chris, or eric |
No output schema declared.
No examples provided.
place_call_and_wait ~284
OPTIONAL convenience for a SINGLE foreground call. Internally polls until finalized or a ~180s hard cap, then degrades to the non-blocking contract (returns call_id to keep polling). NOT for campaigns. 402 errors (trial_exhausted / plan_required / reserved_number_required) are PERMANENT gating, not retryable. Surface action.url and action.sign_in_url to the user verbatim. Do not retry. Trial limits come from the live quota object in the error envelope — never assume a fixed number.
| Name | Type | Req | Description |
|---|---|---|---|
| bridge_number | string | – | Optional US E.164; enables mid-call loop_in_user handoff to this number |
| greeting | string | – | Optional outbound opener context. Does NOT set the agent's first spoken line — the opener is hardcoded server-side to a recording disclosure. |
| max_wait_seconds | integer | – | Seconds to wait before degrading to poll. Default 180, ceiling 240. |
| personality | string | – | Optional reusable style/tone. Do NOT put one-call facts here |
| task | string | yes | Full briefing memo — the agent's ONLY knowledge of the call's purpose and context |
| to | string | yes | US phone number in E.164, +1XXXXXXXXXX |
| voice | string | – | Optional voice: jessica (default), sarah, chris, or eric |
No output schema declared.
No examples provided.
set_api_key ~63
Save a user-supplied ClawCall API key (clawcall_sk_...) to the shared config file. Overrides any saved key. Never echoes the key back.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | A ClawCall API key starting with clawcall_sk_ |
No output schema declared.
No examples provided.
What is the io.github.ClawCall-Dev/clawcall MCP server?
io.github.ClawCall-Dev/clawcall is an MCP server listed in the public MCP registry as io.github.ClawCall-Dev/clawcall. MCP server for ClawCall, AI-powered US phone calling. This page covers its npm package (@clawcall/mcp).
Is the io.github.ClawCall-Dev/clawcall MCP server safe to use?
io.github.ClawCall-Dev/clawcall scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 io.github.ClawCall-Dev/clawcall MCP server expose?
io.github.ClawCall-Dev/clawcall exposes 10 tools: place_call, place_call_and_wait, get_call, get_call_transcript, hangup_call, and 5 more. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.
Is the io.github.ClawCall-Dev/clawcall MCP server still maintained?
io.github.ClawCall-Dev/clawcall is still listed as active in the MCP registry. We last reached this channel on 22 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 io.github.ClawCall-Dev/clawcall MCP server under?
io.github.ClawCall-Dev/clawcall declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.