
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
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.
Installation
In SourceWeft
- Open Linkrescue Mcp in the dashboard and add it to a workspace.
- 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 reportmonitor_links: set up recurring monitoring for a websiteget_fix_suggestions: generate prioritized remediation recommendationshealth_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:
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
Then ask your AI agent:
"Scan example.com for broken affiliate links"
Free vs Pro
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
From source
MCP endpoint:
http://localhost:8000/mcp
Configuration
Example:
Get an API key at linkrescue.io/settings/api (Pro and Agency tiers only).
Running Options
Run via the installed entry point:
Run directly from source:
Run via FastMCP CLI:
Connect an MCP Client
Claude Desktop
Add this to claude_desktop_config.json:
Claude Code
Try It
Tool Inputs and Outputs
check_broken_links
Inputs:
url(required): site URL to scansitemap_url(optional, Agency tier): crawl from sitemapmax_depth(optional, default3): 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, default24; Agency tier supports1)
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_linksarray, 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.
- Push repository to GitHub
- Create/add server in Smithery
- Point Smithery to this repository
Docker / Hosting Platforms
A Dockerfile is included for Railway, Fly.io, and other container hosts.
Set LINKRESCUE_API_BASE_URL and LINKRESCUE_API_KEY in your host environment.
Architecture
This server is a translation layer between MCP tool calls and LinkRescue API operations.
License
MIT — Built by Freedom Engineers
Related
- SelfHeal MCP — Self-healing proxy for MCP servers
- SiteHealth MCP — Full website health audit
- LeadEnrich MCP — Waterfall lead enrichment
Additional README Variants
- Developer-focused version:
README.dev.md - Marketplace-focused version:
README.marketplace.md
Source: README.md at commit 213d6cd
Tools
0Version history
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