PyAI Voice AI
NPM · @PYAI/MCP · 2 COMPONENTS
User-approved phone calls, speech, transcription and voice agents with PyAI OAuth.
Available components
Last scanned (10 hours ago)
Scores higher than 42% of npm servers
Category AI and Machine Learning
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 23 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3763 tokens (~63/item across 59 items; 57 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% 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
- We read all 57 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 59 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
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.
- 5 Nov 26 −2
- Stability: pass → 0.87 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 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.
- 28 Oct 26 −1
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- Stability: pass → 0.93 functional
- 25 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Schema quality: 2744 → 3763 ▼ functional
- Package version: 0.3.3 → 0.5.1 functional
- 21 Oct 26 0
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111771 affects this package: high ▼ security
- 16 Oct 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/@pyai/mcp@0.5.1
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 →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
telephony_buy_number Telephony Buy Number ~123
Purchase a managed number. Requires explicit user approval (confirm=true) and a stable idempotency_key. May incur recurring charges; regulatory or billing setup may require Console.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| confirm | boolean | – | Set true only after the user authorizes this exact purchase or destination. |
| idempotency_key | string | yes | Required safe retry key. Reusing the key with an identical body replays the original 201 response (no second number purchase); reusing it with a different body returns 409 `idempotency_conflict`. |
No output schema declared.
No examples provided.
telephony_create_call Telephony Create Call ~111
Place a real outbound call only to a user-authorized destination. Requires confirm=true and a stable idempotency_key. This is not a sandbox simulation. Preserve the returned ID; never redial after an uncertain timeout.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | – |
| confirm | boolean | – | Set true only after the user authorizes this exact purchase or destination. |
| idempotency_key | string | yes | Required safe-retry key. Identical retries return the original call; a different body returns 409. |
No output schema declared.
No examples provided.
telephony_list_numbers Telephony List Numbers ~31
List owned numbers and current Agent bindings before changing inbound routing.
| Name | Type | Req | Description |
|---|---|---|---|
| include_released | boolean | – | – |
No output schema declared.
No examples provided.
telephony_search_numbers Telephony Search Numbers ~74
Search available managed numbers and inspect provisioning requirements before purchase.
| Name | Type | Req | Description |
|---|---|---|---|
| area_code | string | – | 3-digit US or Canada area code (NPA). |
| contains | string | – | Digit pattern the number should contain. |
| country | string | – | ISO-2 country to search in. |
| limit | integer | – | – |
No output schema declared.
No examples provided.
transcribe_audio Transcribe Audio ~79
Transcribe a small audio attachment supplied as base64 (up to 8 MiB decoded). For large or hosted recordings, use create_transcription_job. Consumes usage.
| Name | Type | Req | Description |
|---|---|---|---|
| audio_base64 | string | yes | Base64-encoded audio bytes, without a data: prefix. |
| filename | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
update_agent Update Agent ~60
Update a voice Agent profile. Read it first and change only user-requested fields.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Writable agent fields. On update, present fields are set, `null` clears, absent fields are untouched. |
| id | string | yes | – |
No output schema declared.
No examples provided.
whoami Who Am I ~89
Introspect the active key (GET /v1/me): org, environment (test/live), granted scopes, and rate-limit/credit posture. Text is concise; authorized IDs remain in structuredContent. Use verbose=true for identity details. Use it to self-diagnose a 401/403/402.
| Name | Type | Req | Description |
|---|---|---|---|
| verbose | boolean | – | Include authorized identity details in text. Credentials are always omitted. |
No output schema declared.
No examples provided.
How do I install the PyAI Voice AI MCP server?
PyAI Voice AI runs locally as an npm package, launched with npx -y @pyai/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 · @pyai/mcp
claude mcp add atomsai-pyai -- npx -y @pyai/mcp
What is the PyAI Voice AI MCP server?
PyAI Voice AI is an MCP server listed in the public MCP registry as io.github.atomsai/pyai. User-approved phone calls, speech, transcription and voice agents with PyAI OAuth. This page covers its npm package (@pyai/mcp).
Is the PyAI Voice AI MCP server safe to use?
PyAI Voice AI scores 72 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 5 November 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 PyAI Voice AI MCP server expose?
PyAI Voice AI exposes 57 tools: openapi_get, create_sandbox_key, get_started, whoami, list_models, and 52 more. Their descriptions and schemas cost roughly 3,551 tokens of context every time the server is loaded.
Is the PyAI Voice AI MCP server still maintained?
PyAI Voice AI is still listed as active in the MCP registry. We last reached this channel on 5 November 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 PyAI Voice AI MCP server under?
PyAI Voice AI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.