LinkPulse

dev.workers.mike-tusa.linkpulsePublished by linkpulse.mike-tusa.workers.devOfficial publisherv0.3.0Updated Oct 24, 2026

Check one web page for broken links, redirect chains hop by hop and mixed content. Free, no key.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Lets an assistant check one public web page for broken links, redirect chains and mixed content.

What you can do
LinkPulse exposes a single tool, check_links, that fetches one public web page and inspects up to 200 of its links and assets. It reports broken links (4xx/5xx responses, nonexistent hosts, connection errors, timeouts), redirect chains hop by hop including long chains, loops and HTTPS-to-HTTP downgrades, and mixed content. Links that may simply block bots, such as 401, 403 or 429 responses, are flagged as uncertain rather than confirmed broken.
When to use it
Useful when you want a quick link audit of a single page, for example before publishing or after moving content, and want redirect and mixed-content problems surfaced alongside dead links.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. No authentication, API keys, environment variables or headers are declared. The server needs network access to fetch the target page and its links.
Before you install
The server fetches the page you name and its linked resources from the remote service, so the URLs you submit are visible to that third party. Results are advisory: bot-blocking responses are only flagged as possibly broken, so verify before acting on them.

Installation

In SourceWeft

  1. Open LinkPulse in the dashboard and add it to a workspace.
  2. 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/dev.workers.mike-tusa.linkpulse%2Flinkpulse/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.

{
  "mcpServers": {
    "linkpulse": {
      "type": "http",
      "url": "https://linkpulse.mike-tusa.workers.dev/mcp"
    }
  }
}

Tools

1

Version history

1
  1. v0.3.0LatestOct 15, 2026

Score

83% 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 listedRequired15 pts
  • 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.