LinkPulse MCP Server

by workers-mike-tusa-linkpulse Your server? Claim it

answering

LinkPulse is answering right now. Last checked 9 min ago. It exposes 1 tools.

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

Uptime history 19 days of history

19 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

93 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 October 2026. No other catalogue keeps this.

16 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check LinkPulse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add linkpulse --transport http https://linkpulse.mike-tusa.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://linkpulse.mike-tusa.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.linkpulse]
url = "https://linkpulse.mike-tusa.workers.dev/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

links

check_links

Fetch ONE public web page and check up to 200 of its links and assets: broken links (4xx/5xx, hosts that don't exist, connection errors, timeouts), redirect chains hop by hop (long chains, loops, https-to-http downgrades), mixed content and links that may just block bots (401/403/429, flagged maybe_bot_blocked). Not a crawler: other pages are not visited. Private/loopback/metadata targets are refused, including names that resolve to them. Takes up to about 45 seconds. Returns counts plus up to 25 problem links. Read-only. Same engine and limits as GET /api/check.

Endpoints

URL	Transport	State	Latency	Checked
https://linkpulse.mike-tusa.workers.dev/mcp	streamable-http	answering	53 ms	9 min ago

Alternatives to LinkPulse

same job, measured the same way

MCP Check Links

by webmoleai

Find broken links, missing meta tags, and redirect chains on any website.

48 installs/wk local only

MCP Link Doctor

by webmoleai

Find broken links, missing meta tags, and redirect chains on any website.

40 installs/wk local only

Broken Links Checker — Crawl Pages, Assets & Redirect Chains

by kriton-dev

Find broken links on a website: crawls its pages and reports 404s, errors and redirect chains

answering

Broken Link Checker

by pavel-tashev

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

answering

OKC SEO Site Audit

by okcseo

Free check of one site for orphan pages, broken internal links and sitemap problems.

1 tools answering

lintlab SEO Site QA

by lintlab

Crawl a site for broken links, redirects and missing SEO tags. Pay per page on Apify.

answering

Dexio

by dexio

One wiki for all your agents: pages read and written over MCP, a link graph, and broken-link checks.

answering

Bsc Token Preflight

by brainonbnb

Honeypot and rug-pull check for any BNB Chain token before a trade, measured on chain, free

2 tools answering

LinkPulse — questions

Answers built from our own checks of this server.

What can LinkPulse do?

It exposes 1 tools, read directly from the server on our last check. Among them: check_links. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is LinkPulse working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 93 ms. The bar chart above shows every period we have measured.

How do I connect LinkPulse?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does LinkPulse need an API key?

No. LinkPulse completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is LinkPulse?

It answers our handshake in 93 ms on average, which is faster than 92% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.