Saidwire Speech-to-Text
PYPI · SAIDWIRE-MCP
Transcribe local audio files and public audio URLs to text, SRT/VTT or word timestamps.
Available components
Last scanned (1 hour ago)
Scores higher than 59% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 31 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 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 451 tokens (~225/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +10
- Source repository: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 67
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 5 Nov 2026 · Analysed pypi/saidwire-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 | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 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 →
transcribe_file ~181
Transcribe a local audio file (WAV, MP3, FLAC, Ogg/Opus, WebM, M4A/MP4, AAC) to text. Args: path: Absolute path to the audio file on this computer (up to 100 MB / 60 minutes). format: "text" (plain transcript), "json" (transcript, utterances and word timestamps), "srt" or "vtt" (subtitles with timestamps). include_words: Add per-word start/end times (for "text" and "json"). output_path: Optional absolute path to also save the result to, e.g. /path/talk.srt.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| include_words | boolean | – | – |
| output_path | – | – | – |
| path | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
transcribe_url ~171
Download a public audio file from an http(s) URL and transcribe it to text. The file is downloaded by this server (default limit 100 MB, set SAIDWIRE_MAX_DOWNLOAD_MB to change it) and sent to Saidwire. Use a direct link to the audio, not a web page. Args: url: Direct http(s) link to an audio file. format: "text", "json" (with word timestamps), "srt" or "vtt". include_words: Add per-word start/end times (for "text" and "json"). output_path: Optional absolute path to also save the result to.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| include_words | boolean | – | – |
| output_path | – | – | – |
| url | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Saidwire Speech-to-Text MCP server?
Saidwire Speech-to-Text runs locally as a PyPI package, launched with uvx saidwire-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · saidwire-mcp
claude mcp add saidwire-saidwire-mcp -- uvx saidwire-mcp
What is the Saidwire Speech-to-Text MCP server?
Saidwire Speech-to-Text is an MCP server listed in the public MCP registry as io.github.Saidwire/saidwire-mcp. Transcribe local audio files and public audio URLs to text, SRT/VTT or word timestamps. This page covers its PyPI package (saidwire-mcp).
Is the Saidwire Speech-to-Text MCP server safe to use?
Saidwire Speech-to-Text scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 Saidwire Speech-to-Text MCP server expose?
Saidwire Speech-to-Text exposes 2 tools: transcribe_file, transcribe_url. Their descriptions and schemas cost roughly 352 tokens of context every time the server is loaded.
Is the Saidwire Speech-to-Text MCP server still maintained?
Saidwire Speech-to-Text 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 Saidwire Speech-to-Text MCP server under?
Saidwire Speech-to-Text declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.