com.superagnt/seo-data vs DispatchSEO
com.superagnt/seo-data is an MCP server published by superagnt.com. Marketplaces we read that list it: 1 (Official MCP Registry). DispatchSEO is an MCP server published by NeoZi12. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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 |  com.superagnt/seo-data |   DispatchSEO |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 1 Stars (GitHub): 6 Not marked · First seen |
Listed Version: 1.1.0 Forks (GitHub): 16 Stars (GitHub): 92 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 | com.superagnt/seo-data | DispatchSEO |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 6 (worse) | 92 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 16 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.superagnt.com/mcp/seo) | Remote server (dispatchseo.com/api/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/superagnt/plugins | github.com/neozi12/dispatchseo |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | Not responding since 2026-10-26 |
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
com.superagnt/seo-data
SEO data for AI agents: Google SERP, keyword research, backlinks, site audits, AI answer visibility.
DispatchSEO
Open-source SEO manager for coding agents: keyword research, content PRs, rank + Search Console.
How to run each
com.superagnt/seo-data As a remote MCP server
claude mcp add --transport http seo-data https://mcp.superagnt.com/mcp/seoDispatchSEO As a remote MCP server
claude mcp add --transport http dispatchseo https://dispatchseo.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of com.superagnt/seo-data responded at the last daily 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: com.superagnt/seo-data · What it can do: DispatchSEO · 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.