Linkinator MCP Server

MCP server for link checking using linkinator. Exposed over MCP by the linkinator mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server that provides link checking capabilities using linkinator. This allows AI assistants like Claude to scan webpages and local files for broken links.

• Comprehensive Link Checking — Scan websites and local files for broken links
• Recursive Crawling — Follow links within the same domain
• Multiple Content Types — Check links in HTML, CSS, and Markdown files
• Fragment Validation — Verify anchor links and URL fragments
• Flexible Configuration — Extensive options for timeouts, retries, SSL, and more
• Detailed Reporting — Get status codes, broken links grouped by error type, and parent page information

Adding it to your client

The server ships on npm as install-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

• Windows — The Windows tool exposed by this server
• Required — The Required tool exposed by this server

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the linkinator mcp mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Linkinator MCP's toolset — Windows, Required — is a fair guide to whether it matches your workflow. It is maintained by justinbeckwith; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.