SEO Content Machine vs Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon
SEO Content Machine is an MCP server published by seocontentmachine.com. Marketplaces we read that list it: 1 (Official MCP Registry). Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon is an MCP server published by shawmena-dotcom. 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
| Marketplace |  SEO Content Machine |  Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Downloads/month (npm): 474 Downloads/week (npm): 24 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 No figure published 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 | SEO Content Machine | Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (seo-content-machine-mcp) | Remote server (mcp.apify.com) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/gitterebi/seo-content-machine-plugin | github.com/shawmena-dotcom/product-factory |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
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
SEO Content Machine
Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.
Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon
Keyword ideas from Google/YouTube/Bing/Amazon autocomplete, with intent and trend verdict.
How to run each
SEO Content Machine As a local MCP server: npm package
claude mcp add --env "SCM_API_KEY=<YOUR_SCM_API_KEY>" --transport stdio scm -- npx -y seo-content-machine-mcpRequires: SCM_API_KEY (secret)
Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon has a remote endpoint we check. How we check endpoints
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 Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon publish no settings it asks for, so we do not compare settings.
What it can do: SEO Content Machine · What it can do: Keyfern: Keyword Ideas & Autocomplete — Google, YouTube, Amazon · Compare two other plugins
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.