SEO-ajaypipes vs ChimpanSEO
SEO-ajaypipes is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
SEO-ajaypipes is a plugin bundle for AI coding tools published by captaindevv. No marketplace we read lists it any more. ChimpanSEO is an MCP server published by chimpanseo.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  ChimpanSEO | |
|---|---|---|
| Community marketplace captaindevv/seo-ajaypipes | Removed on 2026-10-15 Version: not stated Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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-ajaypipesno longer listed · | ChimpanSEO |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 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) | Installs as a plugin bundle | Remote server (chimpanseo.app/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 36 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/captaindevv/seo-ajaypipes | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 43 h ago returned HTTP 405 |
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-ajaypipes
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI-powered blog creation and optimization skill with 20 commands, 4 specialized agents, and 5-category 100-point scoring. Write, rewrite, analyze, and optimize blog posts for…
-
AI agents that research, write and publish SEO articles on your website, from your AI assistant.
-
Run your company blog for SEO and AI search from your AI assistant.
-
Research keywords, plan, write, update and publish SEO blog posts on your site from any agent.
-
Write blog articles with AI and publish them to WordPress, Shopify and 30+ platforms.
-
Draft SEO blog articles from topic to ready-to-review post.
What each says it does
SEO-ajaypipes
AI-powered blog creation and optimization engine for Claude Code, customized for Ajay Pipes (ajaypipes.com) — 30 sub-skills, 5 agents, 5-category 100-point scoring, GEO/AEO optimization.
ChimpanSEO
Generate GEO/AEO-optimized articles and publish them to WordPress from your AI agent.
How to run each
SEO-ajaypipes
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ChimpanSEO As a remote MCP server
claude mcp add --transport http chimpanseo https://chimpanseo.app/api/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ChimpanSEO 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
Neither one's marketplaces publish the settings it asks for.
What it can do: SEO-ajaypipes · What it can do: ChimpanSEO · 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.