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/linkscribe

NPM · @RENETURCIOS/LINKSCRIBE · 2 COMPONENTS

Transcribe links with a txscribe account; read transcripts, summaries and search back.

67 Trust /100

Last scanned (15 hours ago)

Scores higher than 35% of npm servers

Category Documents and Files

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 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
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 531 tokens (~66/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_transcription" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 8 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 52

    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/linkscribe@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 →

MCP tools · 8 exposed · ~531 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
delete_transcription ~36

Delete a transcription and everything made from it. Cannot be undone.

NameTypeReqDescription
idstringyesIdentifier of the record to operate on.

No output schema declared.

No examples provided.

get_summary ~28

The summary and its status.

NameTypeReqDescription
idstringyesIdentifier of the record to operate on.

No output schema declared.

No examples provided.

get_transcript ~120

The finished transcript as json (segments, word timings, speakers), txt, srt or vtt; from and to (seconds) for only the paragraphs around a moment.

NameTypeReqDescription
formatstring–Output format (optional).
fromnumber–Seconds into the recording.
idstringyesIdentifier of the record to operate on.
speakersboolean–Include speaker names.
timestampsboolean–txt and docx: include times.
tonumber–Seconds into the recording; must be after from.

No output schema declared.

No examples provided.

get_transcription ~30

Status and metadata of one transcription.

NameTypeReqDescription
idstringyesIdentifier of the record to operate on.

No output schema declared.

No examples provided.

list_transcriptions ~61

Your transcriptions, newest first, with paging.

NameTypeReqDescription
cursorstring–Pagination cursor from a previous response (optional).
limitinteger–Maximum number of results to return (optional).
statusstring–Status filter for this call.

No output schema declared.

No examples provided.

request_summary ~78

Ask for a summary, or a new one, in a language and for a kind of recording.

NameTypeReqDescription
idstringyesIdentifier of the record to operate on.
languagestring–Output language; defaults to the transcript's.
scenestring–meeting, interview, lecture, … Omit to let the model choose.

No output schema declared.

No examples provided.

search_transcriptions ~55

Which recordings said a word or phrase, and when: up to five matches each, with the second they start at. Searches what was said, not titles.

NameTypeReqDescription
qstringyesThe word or phrase to search for.

No output schema declared.

No examples provided.

transcribe_link ~123

Create a transcription from a link (YouTube, Google Drive, Dropbox …). The recording is transcribed, never downloaded. Uses your minutes.

NameTypeReqDescription
captionsboolean–YouTube only: use the video's own captions when they fit.
diarizationboolean–The diarization for this call.
languagestring–"auto", or a language code such as en-US
urlstringyesA link to a video or recording on YouTube, TikTok, Instagram, X (Twitter), Facebook, Vimeo, Loom, Dropbox.

No output schema declared.

No examples provided.

Install

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

io.github.CloudCorpRecords/linkscribe runs locally as an npm package, launched with npx -y @reneturcios/linkscribe 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 · @reneturcios/linkscribe

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

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

io.github.CloudCorpRecords/linkscribe is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/linkscribe. Transcribe links with a txscribe account; read transcripts, summaries and search back. This page covers its npm package (@reneturcios/linkscribe).

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

io.github.CloudCorpRecords/linkscribe scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting 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/linkscribe MCP server expose?

io.github.CloudCorpRecords/linkscribe exposes 8 tools: list_transcriptions, search_transcriptions, transcribe_link, get_transcription, get_transcript, and 3 more. Their descriptions and schemas cost roughly 531 tokens of context every time the server is loaded.

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

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

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

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/linkscribe, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/linkscribe: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.