Ext Ops Panel
Open dashboard
Comparison

LiveCheck AI vs io.github.Dave-London/lint

LiveCheck AI is an MCP server published by qualityclouds.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Dave-London/lint is an MCP server published by Dave-London. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceLiveCheck AIio.github.Dave-London/lint
Official MCP Registry Listed
Version: 1.0.2
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.8.0
Downloads/month (npm): 374
Downloads/week (npm): 103
Forks (GitHub): 14
Stars (GitHub): 139
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

LiveCheck AI vs io.github.Dave-London/lint
FactLiveCheck AIio.github.Dave-London/lint
Marketplaces that list it11
Stars (GitHub) (differs)3 (worse)139 (better)
Forks (GitHub) (differs)1 (worse)14 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.qualityclouds.com/mcp)On your machine (@paretools/lint)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/qualityclouds/qualitycloudsgithub.com/dave-london/pare
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno 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

LiveCheck AI

In its own words, on Official MCP Registry:

Secure MCP runtime server for scanning and autofixing code issues

io.github.Dave-London/lint

In its own words, on Official MCP Registry:

Structured linting output (ESLint, format-check) as typed JSON diagnostics.

How to run each

LiveCheck AI As a remote MCP server

Claude Code
claude mcp add --transport http mcp-server-qualityclouds https://mcp.qualityclouds.com/mcp

io.github.Dave-London/lint As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio lint -- npx -y @paretools/lint

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

Only LiveCheck AI 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: LiveCheck AI · What it can do: io.github.Dave-London/lint · 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