io.github.AceDataCloud/mcp-serp vs SEOclar — SEO MCP Server
io.github.AceDataCloud/mcp-serp is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). SEOclar — SEO MCP Server is an MCP server published by verbatik. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  io.github.AceDataCloud/mcp-serp | |
|---|---|---|
| Official MCP Registry | Listed Version: 2026.11.1.0 Downloads/month (PyPI): 3 792 Downloads/week (PyPI): 326 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 2026.11.1.0 Downloads/month (PyPI): 3 792 Downloads/week (PyPI): 326 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
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 | io.github.AceDataCloud/mcp-serp | SEOclar — SEO MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-01 | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (seoclar.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/acedatacloud/serpmcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-28 |
| Endpoint at the last check (differs) | Status out of date: last check 32 h ago returned HTTP 401 | Responded 4 h ago |
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
io.github.AceDataCloud/mcp-serp
MCP server for Google search results via SERP API
SEOclar — SEO MCP Server
SEO MCP server for keyword research, live SERPs, backlinks, site audits and AI visibility.
How to run each
io.github.AceDataCloud/mcp-serp As a remote MCP server
claude mcp add --transport http mcp-serp https://serp.mcp.acedata.cloud/mcpRequires: ACEDATACLOUD_API_TOKEN (secret)
SEOclar — SEO MCP Server As a remote MCP server
claude mcp add --transport http seoclar https://seoclar.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints 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
The marketplaces of SEOclar — SEO MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: io.github.AceDataCloud/mcp-serp · What it can do: SEOclar — SEO MCP Server · Compare two other plugins
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.