Mcp Check Links

io.github.webmoleaiPublished by GitHub account webmoleaiv0.2.0Updated Oct 24, 2026

Find broken links, missing meta tags, and redirect chains on any website.

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

An MCP server that checks a web page for broken links, missing meta tags, and redirect chains, returning a health score and fix suggestions.

What you can do
Exposes a single check-links tool that takes a URL and analyzes the page. It tests up to 20 links for 4xx/5xx errors, detects missing meta tags such as title, description, og:title, og:description, og:image, canonical, and viewport, and traces redirect chains while flagging excessive hops. Results come back as a structured report with a 0-100 score and actionable suggestions.
When to use it
Useful when auditing a site's SEO and link health, reviewing a page before publishing, or checking redirect behavior after a migration or domain change. Best for quick single-page checks rather than full-site crawls.
Requirements
Runs locally over stdio, typically via npx mcp-check-links or a local Node.js install. Network access is needed to fetch the target page and its links. The optional MCPCAT_PROJECT_ID environment variable enables analytics; the server works without it.
Before you install
The server fetches the URL you give it and the links found on that page, so it makes outbound requests to third-party sites. Setting MCPCAT_PROJECT_ID enables usage tracking, session replay, and error monitoring through MCPcat; leave it unset to keep analytics disabled.

Installation

In SourceWeft

  1. Open Mcp Check Links in the dashboard and add it to a workspace.
  2. 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-check-links

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

bash
npx mcp-check-links

Configure in Claude Code

Add to your .claude/settings.json (or ~/.claude/settings.json):

json
{  "mcpServers": {    "check-links": {      "command": "npx",      "args": ["mcp-check-links"],      "env": {        "MCPCAT_PROJECT_ID": "proj_your_id_here"      }    }  }}

Or if running locally from the built output:

json
{  "mcpServers": {    "check-links": {      "command": "node",      "args": ["/path/to/mcp-check-links/dist/index.js"],      "env": {        "MCPCAT_PROJECT_ID": "proj_your_id_here"      }    }  }}

MCPCAT_PROJECT_ID is optional. Get your project ID from mcpcat.io. The server runs fine without it — analytics are simply disabled.

Analytics

This server supports MCPcat analytics. Set the MCPCAT_PROJECT_ID environment variable to your project ID (e.g. proj_abc123xyz) to enable usage tracking, session replay, and error monitoring. Without it, the server runs normally with no analytics.

See the MCPcat setup guide for details on creating a project and getting your ID.

Tool

check-links

Input: { "url": "https://example.com" }

Output:

json
{  "url": "https://example.com",  "brokenLinks": [{"href": "...", "status": 404, "text": "..."}],  "missingMetaTags": ["og:image", "canonical"],  "presentMetaTags": {"title": "...", "description": "..."},  "redirectChain": ["https://example.com -> https://www.example.com"],  "score": 85,  "suggestions": ["Add og:image meta tag", "Fix broken link (404): /old-page"]}

Source: README.md at commit d997176

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 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.

Other Check integrations