Back to Directory/Developer Tools

io.github.carsonroell-debug/linkrescue-mcp

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

Developer ToolsPythonv0.1.1

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. Revenue loss estimated.

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, the server falls back to realistic simulated data so local testing and demos keep working.

Quick Start

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

Then ask your AI agent:

"Scan example.com for broken affiliate links"

Free vs Pro

ToolFreePro ($19/mo)Agency ($29/mo)
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
Revenue loss estimates-YesYes
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.

Upgrade to Pro on MCPize — $19/mo or $190/yr. Agency $29/mo or $290/yr.

Install

MCPize (Recommended)

One-click install with managed hosting: Install on MCPize

PyPI

pip install linkrescue-mcp
linkrescue-mcp

From source

git clone https://github.com/carsonroell-debug/linkrescue-mcp.git
cd linkrescue-mcp
pip install -r requirements.txt
python main.py

MCP endpoint:

  • http://localhost:8000/mcp

Configuration

VariableDescriptionDefault
LINKRESCUE_API_BASE_URLBase URL for LinkRescue APIhttp://localhost:3000/api/v1
LINKRESCUE_API_KEYAPI key for authenticated requestsempty

Example:

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:

linkrescue-mcp

Run directly from source:

python main.py

Run via FastMCP CLI:

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

Connect an MCP Client

Claude Desktop

Add this to claude_desktop_config.json:

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

Claude Code

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

Try It

fastmcp list-tools main.py
fastmcp 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. Pro and Agency tiers include estimated monthly revenue loss for broken affiliate links.

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.

# Railway
railway up

# Fly.io
fly launch
fly deploy

Set LINKRESCUE_API_BASE_URL and LINKRESCUE_API_KEY in your host environment.

Architecture

Agent (Claude, Cursor, etc.)
  -> MCP
LinkRescue MCP Server (this repo)
  -> HTTP API
LinkRescue 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

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
uvx linkrescue-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-carsonroell-debug-linkrescue-mcp": {
      "command": "uvx",
      "args": [
        "linkrescue-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

linkrescue-mcppypi

Compatible MCP Clients

io.github.carsonroell-debug/linkrescue-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More