scan_page
Scan links in a webpage or local file path using linkinator. Checks for broken links, validates anchors, and can crawl recursively. Supports progress notifications for long-running scans.
LABSCO SUMMARY
A local path is as valid a target as a URL, so links get checked before the site exists in public.
serverRoot, port and directoryListing let a built output directory be served for the duration of the scan, which moves link checking from a post-deploy alarm to something that runs against the build. For a large site the parameters that decide the outcome are the ones governing runtime: concurrency, timeout, recurse and linksToSkip, plus a retry policy with its own error list, count and jitter, so a host that is slow does not come back looking broken.
What it is
A single-tool wrapper around linkinator: link checking on a webpage or a local file path, with recursive crawling and progress notifications for long runs.
What you get
- scan_page, which checks a webpage or a local file path for broken links using linkinator.
- Anchor validation through checkFragments, stylesheet checking through checkCss, and markdown handling.
- Crawl control: recurse, concurrency, linksToSkip, timeout, userAgent and cleanUrls, plus serverRoot, port and directoryListing for serving a local directory during the scan.
- A tunable retry policy — retry, retryErrors, retryErrorsCount and retryErrorsJitter — and allowInsecureCerts for hosts whose certificates would otherwise stop the scan.
- Progress notifications while a long scan runs.
Requirements
Nothing to supply — no account, no key. A URL or a local file path to scan, and for a local directory the serverRoot and port linkinator should serve it from.
Setup effort
One command — npx linkinator-mcp
USE CASES
01
Catching broken links before the site is published
A local build directory is served for the duration of the scan, so the same recursive check that would run against a live site runs against the output. Anchors are validated as well as URLs, and the retry settings keep a slow host from being reported as dead.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"linkinator-mcp": {
"command": "npx",
"args": [
"linkinator-mcp"
]
}
}
}npx
TERMINAL
npx linkinator-mcp
