mcpField
M
mcp-check-links

mcp-check-links

Local
github.com/webmoleaiDeveloper Tools1Updated 29w ago
Repository

About mcp-check-links

mcp-check-links is an MCP server for website maintainers that checks links and page metadata. It reports a health score, fix suggestions, and redirect chains.

Key features

  1. 01Checks up to 20 page links for errors
  2. 02Detects missing common meta tags
  3. 03Traces and flags long redirect chains
  4. 04Provides a health score and suggestions

Use cases

  1. 01Finding broken links on a page
  2. 02Checking page metadata before launch
  3. 03Investigating website redirect issues

MCP support

It exposes the check-links tool to MCP clients. Given a URL, the tool returns broken links, meta tag findings, redirect chains, a score, and suggestions.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "webmoleai-mcp-check-links": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-check-links"
      ]
    }
  }
}
Run commandnpx -y mcp-check-links

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmmcp-check-links0.2.0

Tools

1

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
urlstringYesThe URL of the website to analyze

Details

From the project 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

npx mcp-check-links

Configure in Claude Code

Add to your .claude/settings.json (or ~/.claude/settings.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:

{
  "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:

{
  "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"]
}

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.