I Built an MCP Server That Finds Broken Links. Here's How AI Agents Use It
I published an MCP server that lets Claude, Cursor, and any MCP-compatible AI agent scan websites for broken links, estimate revenue impact, and suggest fixes. Here's why I built it and how it work...

Source: DEV Community
I published an MCP server that lets Claude, Cursor, and any MCP-compatible AI agent scan websites for broken links, estimate revenue impact, and suggest fixes. Here's why I built it and how it works. Every day, my outreach engine scans affiliate blogs and finds the same thing: sites with 100+ pages almost always have 20-30 broken affiliate links that nobody knows about. Each one is a leak in the revenue bucket. The auditing part was automated. But acting on the results still required me to look at the report, figure out what to fix, and make the changes. That's exactly what AI agents are good at. The Model Context Protocol lets AI agents call tools through a standard interface. Instead of giving an agent a screenshot or a CSV and saying "figure this out," you give it structured tools that return structured data. So I wrapped LinkRescue's scanning engine as an MCP server. Now any agent can: Scan a site → get back every broken link with status codes, page locations, and revenue estimates