npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

bug-finder-nextjs-mcp-server

v1.0.3

Published

An MCP server that checks for 404 links in Next.js applications

Readme

Bug Finder Next.js MCP Server

A specialized MCP (Machine Comprehension Protocol) server that checks for 404 links in Next.js applications. This tool helps you identify broken links in your Next.js project, improving user experience and SEO.

Features

  • 🔍 Scans Next.js projects for internal and external links
  • 🚨 Identifies 404 "Not Found" errors
  • 📊 Generates comprehensive reports of broken links
  • 🤖 Designed to work with AI agents using the "find bug" command
  • 🚀 Easy to install and use

Installation

You can install the tool globally using npm:

npm install -g bug-finder-nextjs-mcp-server

Or run it directly with npx:

npx bug-finder-nextjs-mcp-server find-bug

Usage

Basic Usage

To check for broken links in your Next.js project:

bug-finder find-bug

This will scan your current directory for a Next.js project and check all internal links for 404 errors.

Command Line Options

Options:
  -d, --dir <directory>     Directory of the Next.js project (default: current directory)
  -t, --timeout <ms>        Timeout for each request in milliseconds (default: 5000)
  -c, --concurrency <number> Number of concurrent requests (default: 5)
  -o, --output <file>       Output file for the report
  --include-external        Include external links in the check
  --verbose                 Show verbose output
  -h, --help                Display help information

Examples

Check a specific Next.js project:

bug-finder find-bug --dir /path/to/nextjs-project

Include external links in the check:

bug-finder find-bug --include-external

Save the report to a file:

bug-finder find-bug --output report.json

Using with AI Agents

This tool is designed to work with AI agents. When an AI agent is asked to find bugs in a Next.js project, it can use the following command:

find bug

The tool will automatically detect the Next.js project and check for broken links.

Setting Up as an MCP Server

You can configure this tool as an MCP (Machine Comprehension Protocol) server for AI agents by adding the following configuration to your MCP config file:

{
  "mcpServers": {
    "BugFinderNextJS": {
      "command": "npx",
      "args": [
        "-y",
        "bug-finder-nextjs-mcp-server",
        "bug-finder",
        "find",
        "bug"
      ]
    }
  }
}

Save this as mcp-config.json in your project directory. AI agents that support MCP will be able to use this tool to find broken links in your Next.js project.

How It Works

  1. The tool first verifies that the target directory contains a Next.js project
  2. It starts a development server to render the pages
  3. It crawls all pages in the project to find links
  4. It checks each link to see if it returns a 404 error
  5. It generates a report of all broken links

Integration with Next.js Projects

The tool works with both the Pages Router and App Router in Next.js. It can detect links in:

  • Regular anchor tags (<a href="...">)
  • Next.js Link components
  • Button onClick handlers that navigate to URLs
  • JavaScript navigation functions

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT