io.github.carsonroell-debug/linkrescue-mcp
PYPI · LINKRESCUE-MCP
Broken link detection with affiliate tracking, revenue loss estimation, and fixes
Available components
Last scanned (22 hours ago)
Scores higher than 89% of PyPI servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 211 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 471 tokens (~94/item across 5 items; 4 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Provenance: fail → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 29 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.97 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/linkrescue-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 24 packages
| Packages resolved | 24 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_broken_links Check Broken Links ~138
Scans a single URL or entire site/sitemap for broken links. Returns a structured report with every broken link found, its HTTP status code, the page it was discovered on, link type (affiliate/external/internal), SEO impact rating, and estimated revenue loss. Agents can pass the output directly to get_fix_suggestions for remediation steps.
| Name | Type | Req | Description |
|---|---|---|---|
| max_depth | integer | – | How many levels deep to crawl from the start URL. Default 3. |
| sitemap_url | – | – | Optional sitemap URL to crawl instead of discovering pages by depth. |
| url | string | yes | The website URL to scan (e.g. "https://example.com"). |
Structured output declared, but exposes no named fields.
No examples provided.
get_fix_suggestions Get Fix Suggestions ~95
Given a broken links report, returns prioritized remediation suggestions. Each suggestion includes the broken URL, a recommended action (update link, follow redirect, remove, etc.), a human-readable explanation, and a code snippet where applicable. Accepts either the full JSON report from check_broken_links or just the broken_links array.
| Name | Type | Req | Description |
|---|---|---|---|
| broken_links_report | – | yes | The scan report (JSON string or dict) from check_broken_links. |
Structured output declared, but exposes no named fields.
No examples provided.
health_check Health Check ~46
Confirms the LinkRescue MCP server is alive and can reach the backend API. Use this to verify connectivity before running scans. Returns server status, API reachability, and current configuration.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
monitor_links Monitor Links ~99
Sets up ongoing broken-link monitoring for a website. The monitor runs on a schedule (default: every 24 hours) and will detect new broken links, links that were fixed, and changes in site health score. Returns a monitoring_id you can reference later to check status or cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| frequency_hours | integer | – | How often to re-scan, in hours. Default 24. |
| url | string | yes | The website URL to monitor. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.carsonroell-debug/linkrescue-mcp server?
io.github.carsonroell-debug/linkrescue-mcp runs locally as a PyPI package, launched with uvx linkrescue-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · linkrescue-mcp
claude mcp add carsonroell-debug-linkrescue-mcp -- uvx linkrescue-mcp
What is the io.github.carsonroell-debug/linkrescue-mcp server?
io.github.carsonroell-debug/linkrescue-mcp is listed in the public MCP registry as io.github.carsonroell-debug/linkrescue-mcp. Broken link detection with affiliate tracking, revenue loss estimation, and fixes. This page covers its PyPI package (linkrescue-mcp).
Is the io.github.carsonroell-debug/linkrescue-mcp server safe to use?
io.github.carsonroell-debug/linkrescue-mcp scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.carsonroell-debug/linkrescue-mcp server expose?
io.github.carsonroell-debug/linkrescue-mcp exposes 4 tools: check_broken_links, monitor_links, get_fix_suggestions, health_check. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.
Is the io.github.carsonroell-debug/linkrescue-mcp server still maintained?
io.github.carsonroell-debug/linkrescue-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.carsonroell-debug/linkrescue-mcp server under?
io.github.carsonroell-debug/linkrescue-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.