Linkrescue Mcp

io.github.carsonroell-debugPublished by GitHub account carsonroell-debugv0.1.1Updated Oct 24, 2026

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

Overview

AI-generated overview

LinkRescue MCP lets an AI assistant scan sites for broken and untracked affiliate links, set up recurring monitoring, and get prioritized fix suggestions.

What you can do
Scan a URL or sitemap for broken links and report details and summary statistics, including affiliate links that lost their tracking parameters and earn nothing when clicked (exposure count, not a revenue estimate). Set up recurring link monitoring for a website at a chosen frequency. Generate prioritized remediation suggestions from a scan report or a raw broken-link list. Check server and backend API connectivity.
When to use it
Useful for affiliate site owners and webmasters who want an assistant to audit link health, catch silent tracking failures, and turn scan results into a prioritized fix list, or to schedule ongoing monitoring of a site.
Requirements
Runs as a local Python process (pip install linkrescue-mcp) or via a hosted remote endpoint. Needs network access to the LinkRescue backend; LINKRESCUE_API_BASE_URL sets the endpoint and LINKRESCUE_API_KEY authenticates requests. An API key is available only on Pro and Agency tiers. LINKRESCUE_DEMO_MODE=1 returns labelled sample data for local testing.
Before you install
Sends the scanned site URL and results to the LinkRescue backend, a third party. LINKRESCUE_API_KEY is a secret; keep it out of shared configs. Paid tiers gate the full crawler, fix suggestions, monitoring, and sitemap crawl, so usage may incur cost. Monitoring creates persistent schedules on the service. Do not enable LINKRESCUE_DEMO_MODE against a real site, since it returns simulated data.

Installation

In SourceWeft

  1. Open Linkrescue Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

LinkRescue MCP Server

[PyPI] [License: MIT] [MCPize]

Find broken affiliate links fast, prioritize by impact, and generate fix suggestions your AI agent can act on.

One call. 38+ affiliate networks checked. Silent tracking failures caught.

One-click install: Install on MCPize | pip install linkrescue-mcp

LinkRescue MCP exposes broken-link scanning, monitoring, and remediation workflows through the Model Context Protocol (MCP), so tools like Claude and Cursor can run link-health operations directly.

What You Get

  • check_broken_links: scan a URL (or sitemap) and return a structured broken-link report
  • monitor_links: set up recurring monitoring for a website
  • get_fix_suggestions: generate prioritized remediation recommendations
  • health_check: verify MCP server and backend API connectivity

If the LinkRescue backend API is unreachable, tools raise an error naming the endpoint they could not reach. They never return invented findings. For local testing, set LINKRESCUE_DEMO_MODE=1 to get sample data — every simulated payload carries "simulated": true and an explicit warning.

Hosted endpoint (no install)

LinkRescue runs a remote MCP server at https://www.linkrescue.io/api/mcp (streamable HTTP). Get a free API key at linkrescue.io/signup, then point any remote-capable MCP client at it:

json
{  "mcpServers": {    "linkrescue": {      "url": "https://www.linkrescue.io/api/mcp",      "headers": { "Authorization": "Bearer lr_your_api_key" }    }  }}

The hosted server exposes check_links, start_site_scan, get_scan and get_fix_suggestions. It never returns simulated data. The stdio package below is for local and offline use.

Quick Start

json
{  "mcpServers": {    "linkrescue": {      "command": "linkrescue-mcp"    }  }}

Then ask your AI agent:

"Scan example.com for broken affiliate links"

Free vs Pro

ToolFreeProAgency
health_checkYesYesYes
check_broken_links (up to 50 pages)YesYesYes
check_broken_links (up to 2,000 pages)-YesYes
check_broken_links (unlimited + sitemap crawl)--Yes
get_fix_suggestions-YesYes
monitor_links (daily)-YesYes
monitor_links (hourly + webhooks)--Yes
Multi-site monitoring-5 sites25 sites

Free tier gives you single-page broken-link checks. Pro unlocks the full crawler + fix suggestions + recurring monitoring. Agency adds hourly checks, webhooks, and unlimited site count.

Current pricing lives at linkrescue.io/pricing — that page is the single source of truth. Install on MCPize.

Install

MCPize (Recommended)

One-click install with managed hosting: Install on MCPize

PyPI

bash
pip install linkrescue-mcplinkrescue-mcp

From source

bash
git clone https://github.com/carsonroell-debug/linkrescue-mcp.gitcd linkrescue-mcppip install -r requirements.txtpython main.py

MCP endpoint:

  • http://localhost:8000/mcp

Configuration

VariableDescriptionDefault
LINKRESCUE_API_BASE_URLBase URL for LinkRescue APIhttps://www.linkrescue.io/api/v1
LINKRESCUE_API_KEYAPI key for authenticated requestsempty
LINKRESCUE_DEMO_MODEReturn labelled sample data instead of erroring when the API is unreachable. Off by default — never enable against a real site.empty (off)

Example:

bash
export LINKRESCUE_API_BASE_URL="https://www.linkrescue.io/api/v1"export LINKRESCUE_API_KEY="your-api-key"linkrescue-mcp

Get an API key at linkrescue.io/settings/api (Pro and Agency tiers only).

Running Options

Run via the installed entry point:

bash
linkrescue-mcp

Run directly from source:

bash
python main.py

Run via FastMCP CLI:

bash
fastmcp run main.py --transport streamable-http --port 8000

Connect an MCP Client

Claude Desktop

Add this to claude_desktop_config.json:

json
{  "mcpServers": {    "linkrescue": {      "command": "linkrescue-mcp"    }  }}

Claude Code

bash
claude mcp add linkrescue --transport http http://localhost:8000/mcp

Try It

bash
fastmcp list-tools main.pyfastmcp call-tool main.py health_check '{}'fastmcp call-tool main.py check_broken_links '{"url":"https://example.com"}'

Tool Inputs and Outputs

check_broken_links

Inputs:

  • url (required): site URL to scan
  • sitemap_url (optional, Agency tier): crawl from sitemap
  • max_depth (optional, default 3): crawl depth

Returns scan metadata, broken-link details, and summary statistics. Affiliate links that resolve but have lost their tracking parameters are reported as exposure — a count of links that earn nothing when clicked. LinkRescue does not estimate lost revenue; multiply by your own RPM.

monitor_links

Inputs:

  • url (required)
  • frequency_hours (optional, default 24; Agency tier supports 1)

Returns monitoring ID, schedule details, and status. Free tier returns a simulated monitor (no persistence).

get_fix_suggestions

Input:

  • full report from check_broken_links, or
  • raw broken_links array, or
  • JSON string of either format

Returns prioritized actions and suggested remediation steps. Pro and Agency tiers only.

health_check

No input. Returns server status and backend API reachability.

Deployment

Smithery

This repo includes smithery.yaml and smithery.json.

  1. Push repository to GitHub
  2. Create/add server in Smithery
  3. Point Smithery to this repository

Docker / Hosting Platforms

A Dockerfile is included for Railway, Fly.io, and other container hosts.

bash
# Railwayrailway up
# Fly.iofly launchfly deploy

Set LINKRESCUE_API_BASE_URL and LINKRESCUE_API_KEY in your host environment.

Architecture

text
Agent (Claude, Cursor, etc.)  -> MCPLinkRescue MCP Server (this repo)  -> HTTP APILinkRescue Backend API (linkrescue.io)

This server is a translation layer between MCP tool calls and LinkRescue API operations.

License

MIT — Built by Freedom Engineers

Related

Additional README Variants

  • Developer-focused version: README.dev.md
  • Marketplace-focused version: README.marketplace.md

Source: README.md at commit 213d6cd

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts