
Mcp Link Doctor
io.github.webmoleaiPublished by GitHub account webmoleaiv0.1.1Updated Oct 24, 2026
Find broken links, missing meta tags, and redirect chains on any website.
Overview
A local MCP server that audits a web page for broken links, missing meta tags and redirect chains, returning a health score and fix suggestions.
- What you can do
- Check all links on a page for 4xx/5xx errors, up to 20 links per run, and list the broken ones with their status codes and link text. Detect missing meta tags such as title, description, og:title, og:description, og:image, canonical and viewport, and report which tags are present. Trace redirect chains and flag excessive hops. Return a structured report with a 0–100 health score and actionable suggestions for fixing the issues found.
- When to use it
- Useful when checking a page or site before publishing, reviewing SEO and social-sharing metadata, or diagnosing redirect problems and dead links without opening a browser manually.
- Requirements
- Runs as a local stdio process, started with npx mcp-link-doctor or node against the built output, so Node.js is needed. Network access to the target site is required. The MCPCAT_PROJECT_ID environment variable is optional; without it the server runs normally and analytics are disabled.
Installation
In SourceWeft
- Open Mcp Link Doctor 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
mcp-link-doctor
An MCP server that analyzes websites for broken links, missing meta tags, and redirect chains. Returns a structured report with a health score and fix suggestions.
What it does
- Checks all links on a page for 4xx/5xx errors (up to 20 links)
- Detects missing meta tags: title, description, og:title, og:description, og:image, canonical, viewport
- Traces redirect chains and flags excessive hops
- Returns a score (0–100) and actionable suggestions
Install
Configure in Claude Code
Add to your .claude/settings.json (or ~/.claude/settings.json):
Or if running locally from the built output:
MCPCAT_PROJECT_ID is optional. Get your project ID from mcpcat.io. The server runs fine without it — analytics are simply disabled.
Tool
check-links
Input: { "url": "https://example.com" }
Output:
Source: README.md at commit 26ed78a
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% 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
Declare a license in the repository or the registry entry.