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.

mediasense

PYPI · MEDIASENSE

Let Claude listen to audio and watch video: transcribe, summarize and edit recordings and links.

Available components

+3 this week 69 Trust /100

Last scanned (13 hours ago)

Scores higher than 62% of PyPI 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 Security49
  • Malware scan not yet available for this package.Unverified
  • 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
  • 10 of 79 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to joaoestella/mediasense). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1834 tokens (~152/item across 12 items; 12 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 Management47
  • Stability observed for 14 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 (67% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 19 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 15 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 12 Nov 26 +1

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

  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
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 21 Nov 2026 · Analysed pypi/mediasense@0.5.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo joaoestella/mediasense
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/joaoestella/mediasense/.github/workflows/release.yml@refs/tags/v0.5.2
Rekor log index 3790224740
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:a3859b8f89e85256cf781b463b909fe9ab8133fdd3186e8268b33d41ed8e8b6f

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 79 packages
Packages resolved 79
Stale 7
No linked repository 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~1,475 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
check_job ~78

Get the result of a long-running mediasense job (understand_media, transcribe, render_edit, watch_video). Waits up to ~30s; returns the finished result, or the progress so far plus the same job_id to check again. Without job_id, lists jobs that are still running.

NameTypeReqDescription
job_idstring––

No output schema declared.

No examples provided.

export_transcript ~73

Write the transcript as files next to the media. formats: srt, vtt, txt, csv, json. words_per_cue (e.g. 2) makes short captions for vertical video.

NameTypeReqDescription
formatsarrayyes–
pathstringyes–
words_per_cue–––
NameTypeReqDescription
resultstringyes–

No examples provided.

get_frame ~56

Return the video frame at `time` (e.g. "1:23.4") to look at a moment in detail.

NameTypeReqDescription
pathstringyes–
timestringyes–
widthinteger––

No output schema declared.

No examples provided.

media_info ~31

Duration, resolution, fps and which streams (audio/video) a file has.

NameTypeReqDescription
pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

place_audio ~132

Put an audio clip (or a slice of it) into a video/audio starting at `at`. mode: mix (both play) | duck (original lowered by duck_db) | replace (original muted meanwhile). Video is copied without re-encoding. Writes <base>.placed.<ext> unless output is given.

NameTypeReqDescription
atstringyes–
basestringyes–
duck_dbnumber––
insertstringyes–
insert_from–––
insert_to–––
modestring––
output–––
volumenumber––
NameTypeReqDescription
resultstringyes–

No examples provided.

plan_edit ~297

Preview an edit without writing anything. Same arguments as render_edit. cut_phrases: remove these phrases (all occurrences, or only `occurrence`, 1-based). cut_between: [["from phrase", "to phrase"], ...] removes everything from one to the other, inclusive. cut_ranges: ["1:02-1:05.5", "90-95"]. keep_only: "0:30-2:00". fillers: remove um/uh/éé/hum/euh/äh…; filler_words adds more ("tipo", "you know"). silences: shorten pauses longer than N seconds, leaving silence_keep seconds. silence_source: "audio" (level based) or "transcript" (gaps between words; better with background music). Word timestamps are approximate, so every cut point is moved to the nearest real pause in the audio (marked "moved to the pause") and no word gets clipped. exact_cuts=true cuts at the exact times instead.

NameTypeReqDescription
cut_between–––
cut_phrases–––
cut_ranges–––
exact_cutsboolean––
filler_words–––
fillersboolean––
keep_only–––
occurrence–––
pathstringyes–
silence_keepnumber––
silence_sourcestring––
silences–––
NameTypeReqDescription
resultstringyes–

No examples provided.

read_transcript ~65

Read a transcript (pass the media path or the .transcript.json). start/end limit the time range. words=true shows each word as word@seconds.

NameTypeReqDescription
end–––
pathstringyes–
start–––
wordsboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

render_edit ~190

Apply an edit (see plan_edit for the cut arguments). Never touches the original. Writes <file>.edited.<ext> unless media=false or output is given. edl → Premiere/Resolve/Avid, fcpxml → Final Cut/Resolve, srt → subtitles re-timed to the edited version.

NameTypeReqDescription
cut_between–––
cut_phrases–––
cut_ranges–––
edlboolean––
exact_cutsboolean––
fcpxmlboolean––
filler_words–––
fillersboolean––
keep_only–––
mediaboolean––
occurrence–––
output–––
pathstringyes–
silence_keepnumber––
silence_sourcestring––
silences–––
srtboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

search_transcript ~40

Find every time a word/phrase is said (case, accent and punctuation insensitive).

NameTypeReqDescription
pathstringyes–
phrasestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

transcribe ~234

Transcribe audio/video (file path or link) with word-level timestamps; auto-detects language. vocabulary: names/jargon likely in the audio (["Cloudflare", "Claude", "Next.js"]) so they are spelled right. Pass them whenever you know them (from the user, the title or the screen). model: tiny | base | small | medium | large-v3 | turbo (bigger = slower, more accurate). backend: faster-whisper (default, local) | whisperx (local, tighter word times, speakers) | openai (API). verbatim: keep hesitations (um, éé, hum) so they can be removed later. diarize: label speakers (whisperx backend + HF_TOKEN env var). Reuses an existing <file>.transcript.json unless force=true.

NameTypeReqDescription
backendstring––
diarizeboolean––
forceboolean––
language–––
modelstring––
pathstringyes–
verbatimboolean––
vocabulary–––
NameTypeReqDescription
resultstringyes–

No examples provided.

understand_media ~189

Watch and listen to a video or audio – a TikTok, YouTube, Instagram, X or Vimeo link, or a file – to summarize it, explain it or answer questions about it. Use this instead of opening the link in a browser or fetching the page (those sites block that). One call downloads the link, transcribes the speech with timestamps and returns key-frame contact sheets with what is said in each shot, plus the post's title/description. Long videos reply "STILL WORKING" – then call check_job. vocabulary: brand names / jargon to spell right. language: ISO code if known (pt, en…).

NameTypeReqDescription
forceboolean––
include_imagesboolean––
language–––
max_framesinteger––
modelstring––
sourcestringyes–
vocabulary–––

No output schema declared.

No examples provided.

watch_video ~90

Understand a video: key frames at scene changes + what is said during each shot. Returns a shot list (time, speech) and contact-sheet images labelled with shot number and time. Transcribe first to get the speech column. Lower threshold = more sensitive scene detection.

NameTypeReqDescription
include_imagesboolean––
max_framesinteger––
pathstringyes–
threshold–––

No output schema declared.

No examples provided.

Install

How do I install the mediasense MCP server?

mediasense runs locally as a PyPI package, launched with uvx mediasense 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 · mediasense

# add to Claude Code
claude mcp add joaoestella-mediasense -- uvx mediasense mcp
Common questions

What is the mediasense MCP server?

mediasense is an MCP server listed in the public MCP registry as io.github.joaoestella/mediasense. Let Claude listen to audio and watch video: transcribe, summarize and edit recordings and links. This page covers its PyPI package (mediasense).

Is the mediasense MCP server safe to use?

mediasense scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 mediasense MCP server expose?

mediasense exposes 12 tools: check_job, media_info, transcribe, read_transcript, search_transcript, and 7 more. Their descriptions and schemas cost roughly 1,475 tokens of context every time the server is loaded.

Is the mediasense MCP server still maintained?

mediasense is still listed as active in the MCP registry. We last reached this channel on 21 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 mediasense MCP server under?

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

What did VerifyMCP test on the mediasense MCP server?

VerifyMCP ran 15 checks on mediasense, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about mediasense: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.