io.importly/importly-mcp
NPM · IMPORTLY-MCP
Download, transcribe, and get metadata for any video/audio URL. Managed yt-dlp + speech-to-text.
Available components
Last scanned (21 hours ago)
Scores higher than 87% of npm servers
Category Design and Media
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
- 30 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 107 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 775 tokens (~86/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 4 Nov 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.
- 2 Nov 26 −1
- Stability: pass → 0.90 functional
- 24 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 23 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 20 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.83 → pass security
- 15 Oct 26 −2
- 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 4 Nov 2026 · Analysed npm/importly-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 | 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 →
check_balance ~44
Check the remaining Importly credit balance for the configured API key. Use this to diagnose failed jobs (insufficient credits) or as a pre-flight check before large imports/transcriptions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_basic_metadata ~44
Check the status of a get_basic_metadata job. Returns title, duration, and thumbnail once completed.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id returned by get_basic_metadata |
No output schema declared.
No examples provided.
check_import ~48
Check the status of an import_media job. Returns the media download URL (and transcript, if requested) once the job completes.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id returned by import_media |
No output schema declared.
No examples provided.
check_metadata ~39
Check the status of a get_metadata job. Returns the full metadata object once completed.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id returned by get_metadata |
No output schema declared.
No examples provided.
check_transcription ~45
Check the status of a transcribe_media job. Returns the transcript text and timestamped segments once completed.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id returned by transcribe_media |
No output schema declared.
No examples provided.
get_basic_metadata ~84
Fast-path metadata for a video/audio URL: title, duration, and thumbnail only. Cheaper and quicker than get_metadata — use this to identify or validate a media URL before importing or transcribing it. Async: poll check_basic_metadata with the returned jobId.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Media page URL, e.g. https://www.youtube.com/watch?v=... |
No output schema declared.
No examples provided.
get_metadata ~110
Extract full metadata for a video/audio URL (title, description, duration, uploader, formats, thumbnails, view counts) without downloading the media. Works on YouTube, TikTok, X, and 1000+ sites — no yt-dlp to run yourself. Async: poll check_metadata with the returned jobId. For just title/duration/thumbnail, prefer the faster get_basic_metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Media page URL, e.g. https://www.youtube.com/watch?v=... |
No output schema declared.
No examples provided.
import_media ~202
Download the video/audio at any URL (YouTube, TikTok, X, and 1000+ sites) to hosted storage and get back a direct download link. Importly runs yt-dlp, rotating residential proxies, and ffmpeg server-side — no local tooling needed. Async: returns a jobId immediately; poll check_import for the result. Optionally also produce a transcript in the same job with includeTranscript.
| Name | Type | Req | Description |
|---|---|---|---|
| audioQuality | string | – | Default medium |
| includeAudio | boolean | – | Include audio stream (default true) |
| includeTranscript | boolean | – | Also transcribe the audio in the same job |
| includeVideo | boolean | – | Include video stream (default true) |
| transcriptLanguage | string | – | ISO language hint for the transcript, e.g. "en" |
| url | string | yes | Media page URL, e.g. https://www.youtube.com/watch?v=... |
| videoQuality | string | – | Default 720p |
No output schema declared.
No examples provided.
transcribe_media ~159
Transcribe the audio of any video/audio URL (YouTube, TikTok, podcasts, and 1000+ sites) to text with timestamped segments. Importly handles the download, audio extraction, and speech-to-text server-side — no yt-dlp or ffmpeg needed. Async: returns a jobId immediately; poll check_transcription for the transcript. Costs scale with media length; set maxCostDollars to cap spend on long media.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | ISO language hint, e.g. "en" |
| maxCostDollars | number | – | Abort with a quote if the estimated cost exceeds this cap |
| url | string | yes | Media page URL, e.g. https://www.youtube.com/watch?v=... |
No output schema declared.
No examples provided.
How do I install the io.importly/importly-mcp server?
io.importly/importly-mcp runs locally as an npm package, launched with npx -y importly-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 · importly-mcp
claude mcp add io-importly-importly-mcp -- npx -y importly-mcp
What is the io.importly/importly-mcp server?
io.importly/importly-mcp is listed in the public MCP registry as io.importly/importly-mcp. Download, transcribe, and get metadata for any video/audio URL. Managed yt-dlp + speech-to-text. This page covers its npm package (importly-mcp).
Is the io.importly/importly-mcp server safe to use?
io.importly/importly-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 io.importly/importly-mcp server expose?
io.importly/importly-mcp exposes 9 tools: import_media, check_import, get_metadata, check_metadata, get_basic_metadata, and 4 more. Their descriptions and schemas cost roughly 775 tokens of context every time the server is loaded.
Is the io.importly/importly-mcp server still maintained?
io.importly/importly-mcp is still listed as active in the MCP registry. We last reached this channel on 4 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 io.importly/importly-mcp server under?
io.importly/importly-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.