Ext Ops Panel
Open dashboard
Comparison

memoriant-screen-recorder vs io.github.mcpware/pagecast

memoriant-screen-recorder is a plugin bundle for AI coding tools published by NathanMaine. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.mcpware/pagecast is an MCP server published by mcpware. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplacememoriant-screen-recorderio.github.mcpware/pagecast
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (npm): 408
Downloads/week (npm): 153
Forks (GitHub): 5
Stars (GitHub): 52
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

memoriant-screen-recorder vs io.github.mcpware/pagecast
Factmemoriant-screen-recorderio.github.mcpware/pagecast
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)52 (better)
Forks (GitHub) (differs)0 (worse)5 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@mcpware/pagecast)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nathanmaine/memoriant-screen-recorder-skillgithub.com/mcpware/pagecast
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

memoriant-screen-recorder

In its own words, on Claude Code: claude-plugins-community:

Screen recording for Claude Code. Record demos, tutorials, and bug reproductions directly from your coding session. Claude guides you through capture mode selection (full screen, region, window, or terminal-only), manages the recording session, and converts to optimized GIFs for READMEs and documentation. Works on macOS (screencapture) and Linux (ffmpeg). Includes demo automation for recording plugin showcases.

io.github.mcpware/pagecast

In its own words, on Official MCP Registry:

Record any browser page as GIF or video via MCP

How to run each

memoriant-screen-recorder As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install memoriant-screen-recorder@claude-community

io.github.mcpware/pagecast As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio pagecast -- npx -y @mcpware/pagecast

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

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: memoriant-screen-recorder · What it can do: io.github.mcpware/pagecast · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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