Broken Link Checker

io.github.pavel-tashevPublished by GitHub account pavel-tashevv1.1.0Updated Oct 24, 2026

Crawl a site for broken links, 404s, dead images, redirect chains and slow pages, with sources

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that crawls a site and reports broken links, 404s, dead images, redirect chains and slow pages, with sources.

What you can do
Crawl a site to find broken links and 404 responses, with the pages that reference them as sources. Detect dead images and follow redirect chains. Flag slow pages. Report findings with their source pages so issues can be traced back.
When to use it
Useful when auditing a website's link health, checking a site after a migration or content change, or investigating redirect chains and slow pages before launch.
Requirements
Remote endpoint at mcp.apify.com over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared.
Before you install
Requires an OAuth sign-in, so the assistant acts under your account. Crawling a site sends requests to that site and may be slow or rate-limited on large sites; make sure you are authorized to crawl the target.

Installation

In SourceWeft

  1. Open Broken Link Checker in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.pavel-tashev%2Fbroken-link-checker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "broken-link-checker": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=pavel.tashev/broken-link-checker"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.1.0LatestSep 21, 2026
  2. v1.0.0Sep 20, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.