Ext Ops Panel
Open dashboard
Comparison

lintlab Sitemap Validator vs io.github.xplormityai/searchdock-cli

lintlab Sitemap Validator is an MCP server published by lintlab. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.xplormityai/searchdock-cli is an MCP server published by xplormityai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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

Where each is published
Marketplacelintlab Sitemap Validatorio.github.xplormityai/searchdock-cli
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.3
Downloads/month (npm): 708
Downloads/week (npm): 655
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

lintlab Sitemap Validator vs io.github.xplormityai/searchdock-cli
Factlintlab Sitemap Validatorio.github.xplormityai/searchdock-cli
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.apify.com)On your machine (searchdock-cli)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/xplormityai/searchdock-cli
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-24no 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

lintlab Sitemap Validator

In its own words, on Official MCP Registry:

Find, validate and extract XML sitemaps (gzip, indexes) with lastmod. Pay per result on Apify.

io.github.xplormityai/searchdock-cli

In its own words, on Official MCP Registry:

Read-only Google Search Console analytics, URL inspection and sitemaps via SearchDock CLI.

How to run each

lintlab Sitemap Validator

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: Authorization header

io.github.xplormityai/searchdock-cli As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio searchdock-cli -- npx -y searchdock-cli mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only lintlab Sitemap Validator 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: lintlab Sitemap Validator · What it can do: io.github.xplormityai/searchdock-cli · 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.

Where the data comes from: how the catalog is built