com.abbyseo/mcp-server vs io.github.SeoScoreAPI/seoscoreapi-mcp
com.abbyseo/mcp-server is an MCP server published by abbyseo.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.SeoScoreAPI/seoscoreapi-mcp is an MCP server published by SeoScoreAPI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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.abbyseo/mcp-server |  io.github.SeoScoreAPI/seoscoreapi-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 No figure published Not marked · First seen |
Listed Version: 1.4.1 Downloads/month (npm): 651 Downloads/week (npm): 434 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 | com.abbyseo/mcp-server | io.github.SeoScoreAPI/seoscoreapi-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (www.abbyseo.com/mcp) | On your machine (seoscoreapi-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/seoscoreapi/seoscoreapi-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
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.abbyseo/mcp-server
Scan any URL for on-page, technical & content SEO; 0-100 score with copy-paste fixes.
io.github.SeoScoreAPI/seoscoreapi-mcp
SEO audits, AI readability, accessibility, backlinks and score monitoring from SEO Score API.
How to run each
com.abbyseo/mcp-server As a remote MCP server
claude mcp add --transport http com-abbyseo-mcp-server https://www.abbyseo.com/mcpio.github.SeoScoreAPI/seoscoreapi-mcp As a local MCP server: npm package
claude mcp add --env "SEO_SCORE_API_KEY=<YOUR_SEO_SCORE_API_KEY>" --transport stdio seoscoreapi-mcp -- npx -y seoscoreapi-mcpRequires: SEO_SCORE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.abbyseo/mcp-server 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 com.abbyseo/mcp-server publish no settings it asks for, so we do not compare settings.
What it can do: com.abbyseo/mcp-server · What it can do: io.github.SeoScoreAPI/seoscoreapi-mcp · 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.