SEO Content Machine vs io.github.DataLeadsPRO/keyword-research
SEO Content Machine is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
SEO Content Machine is a plugin bundle for AI coding tools published by SEO Content Machine. No marketplace we read lists it any more. io.github.DataLeadsPRO/keyword-research is an MCP server published by DataLeadsPRO. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.DataLeadsPRO/keyword-research | |
|---|---|---|
| Community marketplace gitterebi/seo-content-machine-plugin | Removed on 2026-10-15 Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 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 Machineno longer listed · | io.github.DataLeadsPRO/keyword-research |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (data.dataleads.pro/mcp/keyword-research) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/gitterebi/seo-content-machine-plugin | github.com/dataleadspro/keyword-research |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of SEO Content Machine
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.
-
AI marketing: SEO articles, trend scouting, competitor analysis, social media, lead magnets
-
End-to-end SEO content pipeline connecting keyword research through to rank tracking. Validate and score keyword opportunities with DataForSEO, generate SERP-feature-targeted…
-
mcp net.topicforge/mcp
Generate programmatic SEO articles, topic clusters, FAQ schema, and batch jobs via TopicForge.
-
Create and manage SEO content plans, articles, projects, and publishing integrations in RankWorker.
-
Programmatic SEO as callable tools: research, generate, audit and publish landing pages.
What each says it does
SEO Content Machine
Drive the SEO Content Machine desktop app from Claude Code: scraping, site crawls, Google Maps listings, archive.org downloads and SEO Workspace pages.
io.github.DataLeadsPRO/keyword-research
Keyword ideas and question discovery for any seed term - volumes, difficulty, and SERP intent.
How to run each
SEO Content Machine
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.DataLeadsPRO/keyword-research As a remote MCP server
claude mcp add --transport http keyword-research https://data.dataleads.pro/mcp/keyword-researchCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.DataLeadsPRO/keyword-research 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 io.github.DataLeadsPRO/keyword-research publish no settings it asks for, so we do not compare settings.
What it can do: SEO Content Machine · What it can do: io.github.DataLeadsPRO/keyword-research · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.