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.EdonZo/talkthru

NPM · TALKTHRU-MCP · SCANNED SEP 20

Talk while using your app — your coding agent gets each sentence aligned to the frame. Fully local.

Available components

0 this week 83 Trust /100
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
  • 33 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 431 tokens (~107/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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_session" 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 4 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
Install

How do I install the io.github.EdonZo/talkthru MCP server?

io.github.EdonZo/talkthru runs locally as an npm package, launched with npx -y talkthru-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 · talkthru-mcp

# add to Claude Code
claude mcp add edonzo-talkthru -- npx -y talkthru-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "edonzo-talkthru": {
      "command": "npx",
      "args": [
        "-y",
        "talkthru-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "edonzo-talkthru": {
      "command": "npx",
      "args": [
        "-y",
        "talkthru-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add edonzo-talkthru -- npx -y talkthru-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "edonzo-talkthru": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "talkthru-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add edonzo-talkthru --command npx --arg -y --arg talkthru-mcp
# ~/.hermes/config.yaml
mcp_servers:
  edonzo-talkthru:
    command: "npx"
    args: ["-y", "talkthru-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "edonzo-talkthru": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "talkthru-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add edonzo-talkthru -t stdio -c npx -a -y talkthru-mcp
// mcp.json
{
  "mcpServers": {
    "edonzo-talkthru": {
      "command": "npx",
      "args": [
        "-y",
        "talkthru-mcp"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 15 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 14 Sept 26 +1
    • Stability: 0.97 → pass security
  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 8 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 7 Sept 26 +1
    • Stability: 0.97 → 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 20 Sept 2026 · Analysed npm/talkthru-mcp@0.3.1

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 98 packages
Packages resolved 98
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~431 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_session ~122

Permanently delete one session — its frames, transcript and bundle — from disk. This cannot be undone and there is no confirmation step, so only call it when the user asked for that session to be deleted. The original recording archived under ~/.talkthru/archive is left alone. To free disk while keeping the frames and narration, the user wants `talkthru compact` instead, not this.

NameTypeReqDescription
session_idstringyesSession id to delete, e.g. 20260803-001500-a1b2c3. Not a file path.

No output schema declared.

No examples provided.

get_latest_session ~89

Return the most recent finished screen recording: the narration aligned to keyframes, the on-screen UI elements captured with each frame, and the frame images. This is the one to call when the user says "look at what I just recorded" or refers to feedback they gave out loud.

NameTypeReqDescription
include_imagesbooleanAttach keyframe images (default true). Set false for the text timeline only.

No output schema declared.

No examples provided.

get_session ~138

Return a specific session by id: narration aligned to keyframes, UI context, and frame images. Use this when the user names an older recording; for "the one I just made", get_latest_session saves a lookup. Ids come from list_sessions. Images are capped, so a long session returns its frames evenly sampled rather than all of them.

NameTypeReqDescription
include_imagesbooleanAttach keyframe images (default true).
max_imagesintegerCap the number of images (default 12).
session_idstringyesSession id, e.g. 20260803-001500-a1b2c3.

No output schema declared.

No examples provided.

list_sessions ~82

List recent screen recordings, newest first, with duration, frame count and a one-line summary of what the person said. Text only and cheap — use it to find the id of the session the user means, then call get_session. Sessions still processing are listed with their state rather than hidden.

NameTypeReqDescription
limitintegerHow many to return (default 10).

No output schema declared.

No examples provided.

Common questions

What is the io.github.EdonZo/talkthru MCP server?

io.github.EdonZo/talkthru is an MCP server listed in the public MCP registry as io.github.EdonZo/talkthru. Talk while using your app, your coding agent gets each sentence aligned to the frame. Fully local. This page covers its npm package (talkthru-mcp).

Is the io.github.EdonZo/talkthru MCP server safe to use?

io.github.EdonZo/talkthru scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.EdonZo/talkthru MCP server expose?

io.github.EdonZo/talkthru exposes 4 tools: get_latest_session, list_sessions, get_session, delete_session. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.

Is the io.github.EdonZo/talkthru MCP server still maintained?

io.github.EdonZo/talkthru 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.

What licence is the io.github.EdonZo/talkthru MCP server under?

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