io.github.tavily-ai/tavily-mcp vs SEOclar — SEO MCP Server
io.github.tavily-ai/tavily-mcp is an MCP server published by tavily-ai. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, npm registry (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.tavily-ai/tavily-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.15 Downloads/month (npm): 79 584 Downloads/week (npm): 24 167 Forks (GitHub): 308 Stars (GitHub): 2 481 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:e8bbe2860c85 Forks (GitHub): 308 Pulls (Docker Hub): 57 818 Stars (Docker Hub): 8 Stars (GitHub): 2 481 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Listed Version: 0.2.22 Downloads/month (npm): 79 584 Downloads/week (npm): 24 167 Forks (GitHub): 308 Stars (GitHub): 2 481 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.tavily-ai/tavily-mcp | SEOclar — SEO MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 2 481 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 57 818 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 308 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (tavily-mcp) | Remote server (seoclar.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/tavily-ai/tavily-mcp | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-28 |
| Endpoint at the last check (differs) | no remote endpoint we check | 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.tavily-ai/tavily-mcp
MCP server for advanced web search using Tavily
SEOclar — SEO MCP Server
SEO MCP server for keyword research, live SERPs, backlinks, site audits and AI visibility.
How to run each
io.github.tavily-ai/tavily-mcp As a local MCP server: npm package
claude mcp add --env "TAVILY_API_KEY=<YOUR_TAVILY_API_KEY>" --transport stdio tavily-mcp -- npx -y tavily-mcpRequires: TAVILY_API_KEY (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.
Only SEOclar — SEO MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of SEOclar — SEO MCP Server publish no list of tools, so we do not compare tools.
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.tavily-ai/tavily-mcp · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.