Svara
NPM · SVARA-MCP
Send native LinkedIn voice notes from your AI assistant via the Svara API.
Available components
Last scanned (1 hour ago)
Scores higher than 62% of npm servers
Category Communication
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 92 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 17 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 467 tokens (~116/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_send_status" implies "send" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 4 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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +6
- Stability: unverified → 0.40 ▲ functional
- 30 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Sept 26 55
First indexed and scored.
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 17 Oct 2026 · Analysed npm/svara-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 92 packages
| Packages resolved | 92 |
|---|---|
| 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_send_status Get send status ~50
Get the delivery status (queued, sent, failed or expired) of a voice note sent with send_linkedin_voice_note.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id returned by send_linkedin_voice_note. |
No output schema declared.
No examples provided.
get_usage Get usage ~22
Get the current Svara plan usage and limits for this API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_linkedin_voice_note Send LinkedIn voice note ~317
Send a native LinkedIn voice note to a person via Svara. WARNING: when dry_run is false this sends a REAL LinkedIn voice message to a real person, from the user's own LinkedIn account. It cannot be unsent. Only call with dry_run=false when the user has explicitly asked you to send this voice note to this recipient. dry_run defaults to true, which validates the request without sending anything. The recipient must be someone the user can already message on LinkedIn (for example a 1st-degree connection); pass their LinkedIn profile URL (preferred) or the name part after /in/ (not their display name). Provide exactly one of audio_url (from upload_audio) or file_path (a local audio file, uploaded first). Delivery requires the Svara Chrome extension to be installed and the user to be signed in to LinkedIn in Chrome. Returns a message id; check delivery with get_send_status.
| Name | Type | Req | Description |
|---|---|---|---|
| audio_url | string | – | audio_url returned by upload_audio. Provide this OR file_path. |
| dry_run | boolean | – | Defaults to true (validate only, nothing is sent). Set false ONLY when the user explicitly asked to send. |
| file_path | string | – | Local audio file to upload and send. Provide this OR audio_url. |
| recipient | string | yes | LinkedIn profile URL (preferred), e.g. https://www.linkedin.com/in/jane-doe, or just the name part after /in/. Must be someone the user can already message on LinkedIn. |
No output schema declared.
No examples provided.
upload_audio Upload audio ~78
Upload a local audio file (MP3, M4A/AAC, OGG/Opus, WAV or WebM, max 4 MB) to Svara. Returns an audio_url to pass to send_linkedin_voice_note. Uploading does not send anything.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Absolute path to a local audio file. |
No output schema declared.
No examples provided.
How do I install the Svara MCP server?
Svara runs locally as an npm package, launched with npx -y svara-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 · svara-mcp
claude mcp add io-svarapi-mcp -- npx -y svara-mcp
What is the Svara MCP server?
Svara is an MCP server listed in the public MCP registry as io.svarapi/mcp. Send native LinkedIn voice notes from your AI assistant via the Svara API. This page covers its npm package (svara-mcp).
Is the Svara MCP server safe to use?
Svara scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Svara MCP server expose?
Svara exposes 4 tools: upload_audio, send_linkedin_voice_note, get_send_status, get_usage. Their descriptions and schemas cost roughly 467 tokens of context every time the server is loaded.
Is the Svara MCP server still maintained?
Svara is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Svara MCP server under?
Svara declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.