Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/audioport

NPM · @RENETURCIOS/AUDIOPORT · 2 COMPONENTS

Audio metadata, conversion, trimming, normalization, and transcription via ffmpeg.

67 Trust /100

Last scanned (4 hours ago)

Scores higher than 34% of npm servers

Category Design and Media

Trust breakdown (7 categories)

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 zod 3.25.76, 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 & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 423 tokens (~84/item across 5 items; 5 tools + 0 resources), lean.Pass
  • 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 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Changelog

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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 65

    First indexed and scored.

Diagnostics

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/@reneturcios/audioport@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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 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 →

MCP tools · 5 exposed · ~423 tokens

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 →

Tool Tokens
convert_audio ~139

Convert an audio file to another format (mp3, wav, ogg, flac, aac, m4a), optionally at the given bit rate such as 192k.

NameTypeReqDescription
bitratestring–Optional bit rate for the output audio, such as 192k.
formatstringyesTarget audio format: one of mp3, wav, ogg, flac, aac, or m4a.
inputstringyesPath to the input audio file to convert.
outputstringyesPath to write the converted audio file to; its extension is replaced with the target format if it differs.

No output schema declared.

No examples provided.

get_audio_metadata ~48

Read metadata for an audio file: format, duration in seconds, bit rate, sample rate, and channels.

NameTypeReqDescription
inputstringyesPath to the input audio file to read metadata from.

No output schema declared.

No examples provided.

normalize_audio ~61

Normalize an audio file's loudness with the loudnorm filter and write it to the output path.

NameTypeReqDescription
inputstringyesPath to the input audio file to normalize.
outputstringyesPath to write the loudness-normalized audio file to.

No output schema declared.

No examples provided.

transcribe_audio ~73

Transcribe an audio file with the configured transcription engine, optionally hinting the language. Returns an error when no engine is configured.

NameTypeReqDescription
inputstringyesPath to the input audio file to transcribe.
languagestring–Optional language hint for the transcription engine, such as a language code or name.

No output schema declared.

No examples provided.

trim_audio ~102

Trim an audio file starting at the given second, optionally for the given duration in seconds.

NameTypeReqDescription
durationnumber–Optional length in seconds of the trimmed output; when omitted, audio runs from start to the end of the file.
inputstringyesPath to the input audio file to trim.
outputstringyesPath to write the trimmed audio file to.
startnumberyesStart time in seconds from which to trim the audio.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/audioport MCP server?

io.github.CloudCorpRecords/audioport runs locally as an npm package, launched with npx -y @reneturcios/audioport. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/audioport

# add to Claude Code
claude mcp add cloudcorprecords-audioport -- npx -y @reneturcios/audioport
Common questions

What is the io.github.CloudCorpRecords/audioport MCP server?

io.github.CloudCorpRecords/audioport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/audioport. Audio metadata, conversion, trimming, normalization, and transcription via ffmpeg. This page covers its npm package (@reneturcios/audioport).

Is the io.github.CloudCorpRecords/audioport MCP server safe to use?

io.github.CloudCorpRecords/audioport scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory 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 io.github.CloudCorpRecords/audioport MCP server expose?

io.github.CloudCorpRecords/audioport exposes 5 tools: get_audio_metadata, convert_audio, trim_audio, normalize_audio, transcribe_audio. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/audioport MCP server still maintained?

io.github.CloudCorpRecords/audioport 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 io.github.CloudCorpRecords/audioport MCP server under?

io.github.CloudCorpRecords/audioport declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.