# io.github.CloudCorpRecords/linkscribe (npm · @reneturcios/linkscribe)

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

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/linkscribe`: 67/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-linkscribe/reneturcios-linkscribe.md), [page](https://verifymcp.io/servers/cloudcorprecords-linkscribe/reneturcios-linkscribe)
- oci · `ghcr.io/cloudcorprecords/linkscribe`: 39/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-linkscribe/ghcr-io-cloudcorprecords-linkscribe.md), [page](https://verifymcp.io/servers/cloudcorprecords-linkscribe/ghcr-io-cloudcorprecords-linkscribe)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/linkscribe`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 531 tokens (~66/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## 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.

### Claude

```bash
claude mcp add cloudcorprecords-linkscribe -- npx -y @reneturcios/linkscribe mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-linkscribe": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/linkscribe",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-linkscribe": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/linkscribe",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-linkscribe -- npx -y @reneturcios/linkscribe mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-linkscribe": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/linkscribe",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-linkscribe --command npx --arg -y --arg @reneturcios/linkscribe --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-linkscribe:
    command: "npx"
    args: ["-y", "@reneturcios/linkscribe", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-linkscribe": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/linkscribe",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-linkscribe -t stdio -c npx -a -y @reneturcios/linkscribe mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-linkscribe": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/linkscribe",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 52)

First indexed and scored.

## MCP tools (8)

### `list_transcriptions` (~61 tokens)

Your transcriptions, newest first, with paging.

Input parameters:

- `cursor` (string): Pagination cursor from a previous response (optional).
- `limit` (integer): Maximum number of results to return (optional).
- `status` (string): Status filter for this call.

### `search_transcriptions` (~55 tokens)

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.

Input parameters:

- `q` (string, required): The word or phrase to search for.

### `transcribe_link` (~123 tokens)

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

Input parameters:

- `captions` (boolean): YouTube only: use the video's own captions when they fit.
- `diarization` (boolean): The diarization for this call.
- `language` (string): "auto", or a language code such as en-US
- `url` (string, required): A link to a video or recording on YouTube, TikTok, Instagram, X (Twitter), Facebook, Vimeo, Loom, Dropbox.

### `get_transcription` (~30 tokens)

Status and metadata of one transcription.

Input parameters:

- `id` (string, required): Identifier of the record to operate on.

### `get_transcript` (~120 tokens)

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

Input parameters:

- `format` (string): Output format (optional).
- `from` (number): Seconds into the recording.
- `id` (string, required): Identifier of the record to operate on.
- `speakers` (boolean): Include speaker names.
- `timestamps` (boolean): txt and docx: include times.
- `to` (number): Seconds into the recording; must be after from.

### `get_summary` (~28 tokens)

The summary and its status.

Input parameters:

- `id` (string, required): Identifier of the record to operate on.

### `request_summary` (~78 tokens)

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

Input parameters:

- `id` (string, required): Identifier of the record to operate on.
- `language` (string): Output language; defaults to the transcript's.
- `scene` (string): meeting, interview, lecture, … Omit to let the model choose.

### `delete_transcription` (~36 tokens)

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

Input parameters:

- `id` (string, required): Identifier of the record to operate on.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-linkscribe/reneturcios-linkscribe#diagnostics

## Score history

- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 52

## 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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/linkscribe
- Socket report: https://socket.dev/npm/package/@reneturcios/linkscribe
- Repository: https://github.com/CloudCorpRecords/linkscribe
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-linkscribe/reneturcios-linkscribe.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-linkscribe/reneturcios-linkscribe/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-linkscribe/reneturcios-linkscribe.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-linkscribe/reneturcios-linkscribe