check_links
Check all links on a webpage for broken URLs (404s), redirects (301/302), and timeouts. Returns status, response time, and location for each link.
LABSCO SUMMARY
Broken links found without opening a crawler.
A link checker is normally a separate tool you have to remember to run. Here it is a question asked mid-conversation, and the answer comes back with the redirect target and the response time already attached.
What it is
An MCP server that checks links for you. It fetches the target, extracts every link on it, and reports which ones are broken, which redirect, and which never answer.
What you get
- Every link on a single page checked for 404s, redirects and timeouts
- A recursive crawl of internal pages, checking the links found along the way
- Every URL in a sitemap.xml checked in one pass
- Status, status text, redirect target, response time and location for each link
- HEAD requests first, falling back to GET when HEAD is refused
Requirements
Nothing to sign up for: npx -y deadlink-checker-mcp is the whole install. Crawl depth on deep_scan runs 1 to 3, and the free tier is capped at 1.
Setup effort
One command — npx -y deadlink-checker-mcp
USE CASES
01
Checking a page before you publish it
Fetch every link on the page and see which ones 404 and which quietly redirect.
02
Auditing a site you just inherited
Crawl internal pages from a starting URL and check the links found on each one.
03
Verifying a sitemap actually resolves
Parse sitemap.xml and check every URL listed in it.
04
Finding the slow pages, not just the dead ones
Response time comes back with every result, so timeouts show up in the same pass.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_sitemap
Fetch a sitemap.xml file and check all listed URLs for broken links, redirects, and timeouts. Supports sitemap index files.
deep_scan
Recursively crawl a website's internal pages and check all found links for broken URLs. Follows internal links up to the specified depth.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"deadlink-checker-mcp": {
"command": "npx",
"args": [
"-y",
"deadlink-checker-mcp"
]
}
}
}npx
TERMINAL
npx -y deadlink-checker-mcp
