# Content (pypi · content-mcp)

Turn URLs, files and text into media, transcripts, summaries, translations and PDF.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `content-mcp`: 78/100 (this document), [markdown](https://verifymcp.io/servers/latentnoise-content/content-mcp.md), [page](https://verifymcp.io/servers/latentnoise-content/content-mcp)

## Channel facts

- Registry: `pypi`
- Package: `content-mcp`
- Version: `0.8.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-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 7 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1296 tokens (~117/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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_upload" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Content MCP server?

Content runs locally as a PyPI package, launched with uvx content-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 latentnoise-content -- uvx content-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "latentnoise-content": {
      "command": "uvx",
      "args": [
        "content-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "latentnoise-content": {
      "command": "uvx",
      "args": [
        "content-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add latentnoise-content -- uvx content-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "latentnoise-content": {
      "type": "local",
      "command": [
        "uvx",
        "content-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add latentnoise-content --command uvx --arg content-mcp
```

### Hermes

```yaml
mcp_servers:
  latentnoise-content:
    command: "uvx"
    args: ["content-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "latentnoise-content": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "content-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add latentnoise-content -t stdio -c uvx -a content-mcp
```

### Other

```json
{
  "mcpServers": {
    "latentnoise-content": {
      "command": "uvx",
      "args": [
        "content-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-09-20 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 78, +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.

### 2026-09-17 (score 77, +1)

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

### 2026-09-15 (score 76, +1)

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

### 2026-09-13 (score 75, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-12 (score 59, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.7.1 → 0.8.0

### 2026-09-10 (score 74, +1)

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

### 2026-09-08 (score 73, +1)

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

## MCP tools (11)

### `analyze_source` (~150 tokens)

Analyze a source and report what can be produced from it.

Accepts a URL, or **a path to a file on this machine** — the one this
MCP server runs on. A local file is read and uploaded to the engine,
which is the only way a file here becomes usable by an engine running
elsewhere; the path is never assumed to exist on the engine's side.
Over a network transport (streamable-http) local paths are refused
outright rather than resolved: "this machine" would be the server's
host, not the caller's, which is not what a path in a request means.

Input parameters:

- `credential`
- `url` (string, required)

### `list_capabilities` (~27 tokens)

Resolve the public capabilities available for an analyzed source.

Input parameters:

- `analysis_id` (string, required)

### `generate` (~166 tokens)

Start a job producing the requested outputs from an analyzed source.

Each output is either a type string — ["video", "subtitles"] — or an
object. Per-output settings go under "options", never beside "type":

    {"type": "subtitles", "options": {"languages": ["es"]}}
    {"type": "video", "options": {"selection": {"max_height": 1080}},
     "delivery": {"mode": "deliver", "folder": "Talks"}}

Other keys of an output object: id, from_sources, from_outputs, scope
("single" or "each_item" for a collection), required. An unknown key
is refused rather than ignored.

Input parameters:

- `analysis_id` (string, required)
- `outputs` (array, required)

### `get_job` (~79 tokens)

Get a job's status and, once terminal, its produced artifacts.

Carries `poll_after`: seconds to wait before calling this again — a
heuristic (grows with elapsed time and the kind of work the job is
doing), not a promise, and `null` once the job is terminal.

Input parameters:

- `job_id` (string, required)

### `cancel_job` (~24 tokens)

Request cooperative cancellation of a running job.

Input parameters:

- `job_id` (string, required)

### `list_jobs` (~23 tokens)

List recent jobs (most recent first).

Input parameters:

- `limit` (integer)

### `get_artifact` (~43 tokens)

Artifact metadata; small text artifacts are inlined, larger/binary
ones return a download reference (never raw bytes over MCP).

Input parameters:

- `artifact_id` (string, required)

### `download_artifact` (~106 tokens)

Save an artifact onto the machine running this MCP server.

Use this when the user wants the file *here* rather than only in the
engine's library — typically when the engine runs on another machine.
\`destination` is optional: omitted, the artifact keeps its own name in
the server's download directory (CONTENT_MCP_DOWNLOAD_DIR, default
\~/Downloads/Content). A path outside that directory is refused.

Input parameters:

- `artifact_id` (string, required)
- `destination`

### `retry_job` (~76 tokens)

Run a finished job's request again, as a new job.

Re-runs the *whole* request: a playlist where one member failed
re-downloads every member. Worth it for a transient failure, wasteful
for a large collection — read the failure in `get_job` first.

Input parameters:

- `job_id` (string, required)

### `delete_upload` (~72 tokens)

Delete bytes uploaded from this machine, before the TTL expires.

\`analyze_source` uploads a local file to the engine; the id it returns
under `upload` is what this takes. Removes only that upload — never an
artifact, never a file in the library.

Input parameters:

- `upload_id` (string, required)

### `get_config` (~36 tokens)

Server-side context for building requests: credential ids for
authenticated sources, whether delivery-by-default is on, and the
existing library folders.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/latentnoise-content/content-mcp#diagnostics

## Score history

- 2026-09-20: 78
- 2026-09-19: 78
- 2026-09-18: 77
- 2026-09-17: 77
- 2026-09-16: 76
- 2026-09-15: 76
- 2026-09-14: 75
- 2026-09-13: 75
- 2026-09-12: 59
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 72
- 2026-09-06: 72
- 2026-09-05: 71
- 2026-09-04: 56
- 2026-09-03: 71
- 2026-09-02: 70
- 2026-09-01: 70
- 2026-08-31: 69
- 2026-08-30: 69
- 2026-08-29: 53
- 2026-08-28: 53
- 2026-08-27: 67
- 2026-08-26: 67
- 2026-08-25: 66
- 2026-08-24: 66
- 2026-08-23: 65
- 2026-08-22: 65

## Common questions

### What is the Content MCP server?

Content is an MCP server listed in the public MCP registry as io.github.LatentNoise/content. Turn URLs, files and text into media, transcripts, summaries, translations and PDF. This page covers its PyPI package (content-mcp).

### Is the Content MCP server safe to use?

Content scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Content MCP server expose?

Content exposes 11 tools: analyze_source, list_capabilities, generate, get_job, cancel_job, and 6 more. Their descriptions and schemas cost roughly 802 tokens of context every time the server is loaded.

### Is the Content MCP server still maintained?

Content is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/content-mcp/
- Socket report: https://socket.dev/pypi/package/content-mcp
- Repository: https://github.com/LatentNoise/content
- Website: https://github.com/LatentNoise/content/blob/main/apps/mcp/README.md
- Changelog RSS feed: https://verifymcp.io/servers/latentnoise-content/content-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/latentnoise-content/content-mcp.json
- HTML version of this page: https://verifymcp.io/servers/latentnoise-content/content-mcp