Ext Ops Panel
Open dashboard
Comparison

txscribe vs Talkthrough

txscribe is an MCP server published by txscribe.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Talkthrough is an MCP server published by korovin-aa97. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacetxscribeTalkthrough
Official MCP Registry Listed
Version: 0.2.1
Downloads/month (npm): 867
Downloads/week (npm): 121
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.4.4
Downloads/month (PyPI): 687
Downloads/week (PyPI): 59
Forks (GitHub): 4
Stars (GitHub): 33
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.4.4
Downloads/month (PyPI): 687
Downloads/week (PyPI): 59
Forks (GitHub): 4
Stars (GitHub): 33
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

txscribe vs Talkthrough
FacttxscribeTalkthrough
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)33 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last release (differs)2026-10-28 (better)2026-10-23 (worse)
Where it runs (differs)Remote server (txscribe.ai/mcp)On your machine (talkthrough-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 0
Licence (differs)Not statedMIT
Repository (differs)github.com/txscribe-ai/txscribe-mcpgithub.com/korovin-aa97/talkthrough-mcp
Changes in the last 7 days00
First seen (differs)2026-10-252026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 405no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

txscribe

In its own words, on Official MCP Registry:

Transcribe a link, then read the transcript and summary from your txscribe account.

Talkthrough

In its own words, on Official MCP Registry:

Local MCP server: recordings or public video URLs into transcript, frames, OCR, wall-clock evidence.

How to run each

txscribe As a remote MCP server

Claude Code
claude mcp add --transport http txscribe https://txscribe.ai/mcp

Requires: TXSCRIBE_API_KEY (secret)

Talkthrough As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio talkthrough-mcp -- uvx talkthrough-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only txscribe has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only txscribe asks for

  • TXSCRIBE_API_KEY (secret)

Only Talkthrough asks for

  • TALKTHROUGH_HOME
  • TALKTHROUGH_MAX_DOWNLOAD_BYTES
  • TALKTHROUGH_OCR
  • TALKTHROUGH_OCR_LANG
  • TALKTHROUGH_WHISPER_MODEL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: txscribe · What it can do: Talkthrough · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built