deckify vs NewsBlog Composer
deckify is a plugin bundle for AI coding tools published by Xichang (Seacen) Zhao. Marketplaces we read that list it: 1 (Community GitHub marketplaces). NewsBlog Composer is an MCP server published by Mohammed-Jameal-J. 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
| Marketplace | ||
|---|---|---|
| Community marketplace seacen/deckify | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 49 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.0 Downloads/month (PyPI): 1 173 Downloads/week (PyPI): 57 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.8.0 Downloads/month (PyPI): 1 173 Downloads/week (PyPI): 57 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | deckify | NewsBlog Composer |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 49 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (newsblog-composer-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 3 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | PolyForm-Noncommercial-1.0.0 | MIT |
| Repository (differs) | github.com/seacen/deckify | github.com/mohammed-jameal-j/newsblog-composer-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-05 | 2026-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
deckify
Stop making slides. Let AI build them in HTML — the medium it was born to write in. Give deckify any brand URL; in minutes you get a brand-faithful Design System markdown plus a verified 9-slide HTML demo deck. Trigger: "use deckify on https://...", "build a deck like <brand>", "extract the design system from <site>".
NewsBlog Composer
Verifies news stories, mines SEO keywords, builds schema and reviews your draft. You write it.
How to run each
deckify As a Claude Code plugin
/plugin marketplace add seacen/deckify
/plugin install deckify@deckify
NewsBlog Composer As a local MCP server: PyPI package
claude mcp add --env "CLOUDFLARE_API_TOKEN=<YOUR_CLOUDFLARE_API_TOKEN>" --env "GPTZERO_API_KEY=<YOUR_GPTZERO_API_KEY>" --env "TAVILY_API_KEY=<YOUR_TAVILY_API_KEY>" --transport stdio newsblog-composer -- uvx newsblog-composer-mcp
Requires: CLOUDFLARE_API_TOKEN (secret), GPTZERO_API_KEY (secret), TAVILY_API_KEY (secret)
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
The marketplaces of deckify publish no settings it asks for, so we do not compare settings.
What it can do: deckify · What it can do: NewsBlog Composer · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.