Talkthrough MCP

Don't write a bug report — record it. Local MCP: screen recording → transcript, frames, OCR, wall-clock evidence for cod

MCP Servers Python Grade A Listed MIT
80.9/100
Rank #90 of 1320
Compare Talkthrough MCP

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-03 · 1d ago
Recent change
Scorecard +11

Is Talkthrough MCP safe? Talkthrough MCP scores 80.9/100 (Grade A), ranked #90 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7/10; 58% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-04
Scorecard Added
OSSF Scorecard: 7.0/10
2026-09-04
Grade Changed
Trust grade B → A
2026-09-04
Rank Moved
Rank rose 192 spots (#282 → #90)
Maintainer Checklist
Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.
51.3
Activity sub-score · out of 100
#33

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 14:33 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
24
Forks
1
Last Push
2026-09-03
yesterday
Commits (4 wk)
20
Downloads (7d)
234
pypi
HN mentions (30d)
Open Issues
4
Rank Change
▲192
was #282

Analysis

HVTrust Dimensions vs MCP Servers

80.9 / 100 · 100.0% confidence

Talkthrough MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
19.1 / 25
9.6 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
14.4 / 17
2.6 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
17.2 / 20
5.0 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.5 / 20
in line with avg 6.2

Activity Inputs

51.3 / 100
StarsRepository reach
8.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
16.5 / 25
CommunityFork signal
1.4 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
7.0 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
58%
of last 100 commits verified
Dangerous-Workflow 10
Dependency-Update-Tool 10
Token-Permissions 10
Code-Review 0
Maintained 0
Security-Policy 10
Binary-Artifacts 10
Pinned-Dependencies 10
CII-Best-Practices 0
Vulnerabilities 10
Packaging 10
Fuzzing 0
License 10
SAST 10
Branch-Protection 8
Signed-Releases 4
Contributors 0
CI-Tests 10

Is Talkthrough MCP safe?

Public supply-chain signals for Talkthrough MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Talkthrough MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Talkthrough MCP publish package provenance?
Yes. Talkthrough MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Talkthrough MCP have an OpenSSF Scorecard?
Talkthrough MCP has an OpenSSF Scorecard score of 7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Talkthrough MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Talkthrough MCP use?
Talkthrough MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Talkthrough MCP's commits signed?
57% of the last 100 commits to Talkthrough MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Talkthrough MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Talkthrough MCP?

For maintainers

HVTrust scores Talkthrough MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 14HVTrust 2Grade 2Listed 1Scorecard 1
2026-09-04
Scorecard Added
OSSF Scorecard: 7.0/10
2026-09-04
Grade Changed
Trust grade B → A
2026-09-04
Rank Moved
Rank rose 192 spots (#282 → #90)
2026-09-04
HVTrust Changed
HVTrust up 14.6pts (66.3 → 80.9)
2026-09-02
Grade Changed
Trust grade D → B
2026-09-02
Rank Moved
Rank rose 571 spots (#844 → #273)
2026-09-02
HVTrust Changed
HVTrust up 22.6pts (43.6 → 66.2)
2026-09-01
Rank Moved
Rank dropped 32 spots (#812 → #844)
2026-08-31
Rank Moved
Rank dropped 33 spots (#779 → #812)
2026-08-30
Rank Moved
Rank dropped 36 spots (#743 → #779)
2026-08-29
Rank Moved
Rank dropped 40 spots (#703 → #743)
2026-08-28
Rank Moved
Rank dropped 20 spots (#683 → #703)
2026-08-27
Rank Moved
Rank dropped 16 spots (#667 → #683)
2026-08-26
Rank Moved
Rank dropped 97 spots (#570 → #667)
2026-08-25
Rank Moved
Rank rose 11 spots (#581 → #570)
2026-08-24
Rank Moved
Rank dropped 11 spots (#570 → #581)
2026-08-16
Rank Moved
Rank dropped 22 spots (#551 → #573)
2026-08-13
Rank Moved
Rank dropped 14 spots (#542 → #556)
2026-08-10
Rank Moved
Rank dropped 26 spots (#523 → #549)
2026-08-08
Newly Listed
First tracked at rank #513

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 80.9 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/talkthrough-mcp.svg)](https://hvtracker.net/agents/talkthrough-mcp)
HTML:
<a href="https://hvtracker.net/agents/talkthrough-mcp"><img src="https://hvtracker.net/badge/talkthrough-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON