MCP servers › io.github.TMHSDigital › screencast-mcp
MCP server · registry snapshot 2026-11-01 · last checked 2026-11-01
io.github.TMHSDigital/screencast-mcp
by TMHSDigital · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
Let AI agents record the Windows screen, watch it as frames, and edit it with ffmpeg — the publisher's description
Summary
io.github.TMHSDigital/screencast-mcp is a local MCP server listed in the official MCP registry at version 0.48.0, under the namespace of the GitHub account TMHSDigital. Its linked repository, github.com/TMHSDigital/screencast-mcp, belongs to the same GitHub account.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #535 of 18,234 packages by monthly downloads
- Not ranked by stars: 1 star (ranked from 10)
- #110 of 938 packages meeting all 9 record checks, by downloads
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- npm · listed version current
- License
- CC-BY-NC-ND-4.0
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
Worth knowing before you connect it
- Its package is signed and carries a build record naming its source.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.48.0, published 2026-11-01 (registry, as of the 2026-11-01 snapshot)
- First listed version
- 2026-10-25 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 21 versions listed, 2026-10-25 to 2026-11-01; 21 in the 90 days before the 2026-11-01 snapshot.(versions still listed in the registry only)
Most recent 12 versions
0.48.0· 2026-11-010.47.0· 2026-10-280.46.0· 2026-10-280.45.0· 2026-10-280.44.2· 2026-10-280.39.0· 2026-10-270.38.0· 2026-10-260.37.0· 2026-10-260.36.0· 2026-10-250.35.0· 2026-10-250.34.0· 2026-10-250.33.2· 2026-10-25
- Registry data
- snapshot 2026-11-01
- Package and repository
- checked 2026-11-01
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.47.0 (published 2026-10-28) → 0.48.0 (published 2026-11-01), between the registry lists of 2026-10-31 and 2026-11-01.
The publisher’s GitHub release note for v0.48.0, published 2026-11-01.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
### Security - Network and device paths are refused in every path argument: a UNC (`\\host\share`), `//host/share`, WebDAV (`\\host@SSL@443\...`), `\\?\UNC\` or `\\.\` path is rejected before anything opens it, because opening one sends the user's NTLM credentials to that host. The check runs once per tool call, before the handler, including paths nested in `pipeline` steps. - Input paths are confined like outputs: once the client sends workspace roots or `SCREENCAST_ALLOWED_DIRS` is set, files to read must sit inside `SCREENCAST_HOME`, the roots, or those folders (a whisper model and a font file are exempt). - A client whose `roots/list` request fails now gets `SCREENCAST_HOME` and `SCREENCAST_ALLOWED_DIRS` only, instead of no confinement. - With no confinement configured, replacing an existing file outside `SCREENCAST_HOME` is refused even with `overwrite: true`; list its folder in `SCREENCAST_ALLOWED_DIRS` to allow it. - `index_recording` masks secret-shaped screen text before writing the index, and `search_recording` matches the masked text, so hit counts cannot confirm a secret. Retention also removes old `*.index.json` sidecars under `SCREENCAST_HOME` (#266). ### Added - `screencast-mcp setup` (#267): one command for first-run setup. It runs the `doctor` checks as a checklist, offers `winget install Gyan.FFmpeg` when FFmpeg 8 is missing, and merges the server into Claude Desktop, Cursor, and VS Code configs (each backed up first) and Claude Code (`claude mcp add`). `--dry-run` prints the changes, `--yes` skips prompts, `--test` records a 3 s GIF. - The GitHub Action (#268): `comment: true` keeps one sticky PR comment per job with the exit code, how the recording ended, OCR'd error lines, and a link to the evidence artifact. The CLI gains `--ocr-errors`. - The Action gains `max-duration`, `end-reason`, `artifact-name`, and `artifact-url`; the CLI gains `--command-env NAME` (#257). ### Fixed - `redact_region` and `pipeline` `style: "blur"` failed on FFmpeg 8.1.3 and newer for small or thin regions (a 4x4 box, a 16 px text line): boxblur now requires a radius strictly under half the region's side, and the radius is chosen that way. - `pipeline` recipes: `redact`, `crop`, and `cursor` overrides now run first (after any trim), in source pixels and time. Before, a redact added to `social_reel` landed after the cut and the 9:16 reframe and missed the secret, and on the other recipes a redact or cursor override failed to plan (#251). - Overlapping `pause_recording`, `resume_recording`, and `stop_recording` calls on one session now run one at a time: a second resume no longer starts an untracked ffmpeg, a stop during a pause no longer force-kills the segment it is finalizing, and a segment ffprobe cannot read is kept with an estimated length instead of dropped (#252). - `encoder: "auto"` skips hardware encoders the frame is too large for (NVENC 4096 px, QSV/AMF 4096x2304), and a hardware encoder that fails at start is retried once with x264, with an `encoderNote` (#253). - `narrate` and OCR batches pass their data through a temp file instead of the command line, so long scripts no longer fail with ENAMETOOLONG (#254). - `index_recording` rebuilds an index made without OCR once OCR is available; sidecars are named after the full file name (`demo.mp4.index.json`, reading the old name only when it belongs to the same recording); `search_recording` refuses an index of another recording and queries with no letters or digits (#255). - `pipeline` and `narrate` no longer overwrite an existing `.srt` without `overwrite: true`, and the pipeline's sidecar is re-timed through speed and cut steps after the captions (#256). - The CLI and Action: `evidence.json` records `status` and `endReason` and the run warns when the recording ended before the command; `--max-duration` must be a whole number in range; commands with quotes and `&` survive cmd.exe; the default artifact name is unique per job and matrix leg; and the Action runs the npm
Source: the official MCP Registry list on 2026-10-31 and on 2026-11-01; release notes from the GitHub Releases API, checked 2026-11-01.
What it is
How do I add it to my client?
Config from the registry entry
From the npm package @tmhs/screencast-mcp
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"screencast-mcp": {
"command": "npx",
"args": [
"-y",
"@tmhs/screencast-mcp@0.48.0"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"screencast-mcp": {
"command": "npx",
"args": [
"-y",
"@tmhs/screencast-mcp@0.48.0"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"screencast-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@tmhs/screencast-mcp@0.48.0"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"screencast-mcp","type":"stdio","command":"npx","args":["-y","@tmhs/screencast-mcp@0.48.0"]}'Claude Code
claude mcp add --transport stdio screencast-mcp -- npx -y @tmhs/screencast-mcp@0.48.0
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"screencast-mcp": {
"command": "npx",
"args": [
"-y",
"@tmhs/screencast-mcp@0.48.0"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"screencast-mcp": {
"command": "npx",
"args": [
"-y",
"@tmhs/screencast-mcp@0.48.0"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.screencast-mcp] command = "npx" args = ["-y", "@tmhs/screencast-mcp@0.48.0"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"screencast-mcp": {
"command": "npx",
"args": [
"-y",
"@tmhs/screencast-mcp@0.48.0"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @tmhs/screencast-mcp@0.48.0
- Optional settings the entry also lists (left out above): SCREENCAST_HOME, SCREENCAST_ALLOWED_DIRS, FFMPEG_PATH, FFPROBE_PATH, SCREENCAST_WHISPER_MODEL, SCREENCAST_MAX_RECORDING_SEC, SCREENCAST_JOB_TIMEOUT_MS, SCREENCAST_RETENTION_DAYS, SCREENCAST_PS_TIMEOUT_MS, SCREENCAST_CONFIRM_CAPTURE, SCREENCAST_TOOLSETS.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.48.0
- Latest stable
- 0.48.0
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-01. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-01 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-bc9JSdVRqggEKFh1q…
- Signature
- signed and attested
- License
- CC-BY-NC-ND-4.0
Source: the package registry · 2026-11-01.
Usage
- Downloads
- 4,373 in the last month
Source: api.npmjs.org · 2026-11-01.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.48.0 on npm | Exists and can be installed | matches | npm · 2026-11-01 |
| Repository github.com/TMHSDigital/screencast-mcp | Opens publicly | matches | api.github.com · 2026-11-01 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.TMHSDigital · 2 servers
- GitHub owner
- a personal account (TMHSDigital)
- Build record
- signed and attested
- Repository
- github.com/TMHSDigital/screencast-mcp
- Stars
- 1
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-01; security policy read from GitHub · 2026-11-01.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating9 of 9 record checks met
- #535 of 18,234 packages by monthly downloads
- Not ranked by stars: 1 star (ranked from 10)
- #110 of 938 packages meeting all 9 record checks, by downloads
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierCC-BY-NC-ND-4.0
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-01 (security policy 2026-11-01). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.TMHSDigital/screencast-mcp
Answered from the data aboveWho publishes io.github.TMHSDigital/screencast-mcp?
The registry ties the namespace io.github.TMHSDigital to the GitHub account TMHSDigital; only its owner can publish under it. Its linked repository, github.com/TMHSDigital/screencast-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.TMHSDigital/screencast-mcp safe to install?
We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.TMHSDigital/screencast-mcp been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's.
Does io.github.TMHSDigital/screencast-mcp publish a security policy?
Yes: its repository has a public security policy (github.com/tmhsdigital/screencast-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
Yes. The registry lists 0.48.0, the latest stable release on npm.
Where is the source code of io.github.TMHSDigital/screencast-mcp?
In github.com/TMHSDigital/screencast-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish. This is our limit, not the server's. — our limit
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.TMHSDigital/screencast-mcp: MCP server record.” Data checked 2026-11-01. https://protocolprobe.com/mcp/servers/io.github.TMHSDigital/screencast-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.TMHSDigital/screencast-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology