Skip to main content
Glama

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

Related MCP server: mcp-link-doctor

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

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

Available Tools

1 tool

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools.

    Naming Consistency5/5

    A single tool name follows a clear naming pattern by default.

    Tool Count3/5

    A single tool for a focused domain is borderline but acceptable; it might feel too limited for broader use cases.

    Completeness3/5

    The tool covers the basic functionality described, but lacks granular options or additional related checks like SEO analysis beyond meta tags.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers