Ext Ops Panel
Open dashboard
Comparison

io.github.carsonroell-debug/linkrescue-mcp vs io.github.hellovelop/limelink-mcp-server

io.github.carsonroell-debug/linkrescue-mcp is an MCP server published by carsonroell-debug. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.hellovelop/limelink-mcp-server is an MCP server published by hellovelop. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
Marketplaceio.github.carsonroell-debug/linkrescue-mcpio.github.hellovelop/limelink-mcp-server
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (PyPI): 72
Downloads/week (PyPI): 21
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.0.5
Downloads/month (npm): 172
Downloads/week (npm): 21
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

io.github.carsonroell-debug/linkrescue-mcp vs io.github.hellovelop/limelink-mcp-server
Factio.github.carsonroell-debug/linkrescue-mcpio.github.hellovelop/limelink-mcp-server
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (linkrescue-mcp)On your machine (limelink-mcp-server)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/carsonroell-debug/linkrescue-mcpgithub.com/hellovelop/limelink-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

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.carsonroell-debug/linkrescue-mcp

In its own words, on Official MCP Registry:

Broken link detection with affiliate tracking, revenue loss estimation, and fixes

io.github.hellovelop/limelink-mcp-server

In its own words, on Official MCP Registry:

MCP server for Limelink dynamic links with deep linking, social previews, and UTM tracking

How to run each

io.github.carsonroell-debug/linkrescue-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LINKRESCUE_API_KEY=<YOUR_LINKRESCUE_API_KEY>" --transport stdio linkrescue-mcp -- uvx linkrescue-mcp

Requires: LINKRESCUE_API_KEY (secret)

io.github.hellovelop/limelink-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "LIMELINK_API_KEY=<YOUR_LIMELINK_API_KEY>" --transport stdio limelink-mcp-server -- npx -y limelink-mcp-server

Requires: LIMELINK_API_KEY (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.carsonroell-debug/linkrescue-mcp asks for

  • LINKRESCUE_API_BASE_URL
  • LINKRESCUE_API_KEY (secret)

Only io.github.hellovelop/limelink-mcp-server asks for

  • LIMELINK_API_KEY (secret)
  • LIMELINK_PROJECT_ID

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.carsonroell-debug/linkrescue-mcp · What it can do: io.github.hellovelop/limelink-mcp-server · 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